Browse guides

Organisation setup

Manage organisation billing

Complete subscription setup, manage payment details, schedule billing-frequency changes, and understand access after cancellation.

Organisation setup For Owner, Administrator

Manage organisation billing

Billing belongs to an organisation, not to an individual user. Only an organisation owner or administrator can open Organisation, then Billing, and manage that organisation's Stripe subscription.

Complete subscription setup

New paid organisations require an explicit monthly or annual subscription choice and begin with the trial period shown for the current plan. Stripe securely collects the payment method and billing address; Obsidian Metra does not collect card details directly.

Review Product, then Pricing before registration to compare the currently available monthly and annual costs and the capabilities included with each option. The public pricing page and organisation onboarding both show prices from the product currently marked active for new subscriptions. Inactive or superseded products are not offered to new organisations, and the browser does not calculate or submit a charge amount. If current pricing cannot be loaded, retry before creating an organisation; your existing organisations remain available.

An existing organisation remains linked to the product and price selected when its subscription was created. Activating a replacement product changes the choices for new signups only; it does not automatically move or reprice existing customers. The organisation's Billing page continues to show its stored subscription price.

  1. Open the organisation's Billing page.
  2. Review the selected billing frequency, price, trial end, subscription status, and expected renewal or access-end date.
  3. Select Continue subscription setup when checkout is incomplete.
  4. Complete the hosted Stripe Checkout session.
  5. Return to Obsidian Metra and wait while the page confirms the subscription.

Stripe confirmation is asynchronous. If the return page says confirmation is still pending, refresh shortly rather than creating another organisation or checkout session.

An organisation on the FREE_FOREVER founder plan does not require Stripe checkout and cannot schedule a paid billing-frequency change through this workflow.

Manage payment details and invoices

Select Manage payment and invoices to open the organisation's configured Stripe Customer Portal. Use the portal to manage payment methods, invoices, and cancellation. Always confirm the organisation name before changing billing information, especially when your account belongs to several organisations.

The Billing page does not expose Stripe secrets, card data, or a reusable customer-portal URL. Each hosted session is created for the selected and authorised organisation.

Change monthly or annual billing

  1. Under Change billing frequency, select the other available frequency.
  2. Select Schedule for renewal.
  3. Confirm the scheduled subscription and effective date shown on the page.

The change takes effect at the next renewal without mid-period proration. Scheduling a change does not immediately replace the current billing period.

Cancellation and access

Cancellation takes effect at the end of the current billing period. The Billing page shows the next renewal date or access-end date from the stored subscription state. Organisation access is locked after that period ends rather than disabling one user at a time.

When recovery remains available, an owner or administrator can select Restart subscription and complete a new hosted checkout. If Stripe has accepted payment but the page still shows an old status, refresh after webhook processing; do not repeat payment solely because the first refresh is delayed.

Troubleshooting

  • Billing unavailable with an access message means the current membership is not an owner or administrator.
  • A connection error is different from a permission denial. Use Try again after checking the API connection.
  • A pending confirmation after Stripe return normally means webhook processing has not completed yet.
  • If a scheduled change is rejected as a conflict, refresh before submitting another change because the billing record changed in another session.
  • If the portal or checkout cannot open, retry from the Billing page rather than reusing an old hosted URL.

Billing state is synchronised from Stripe events. Contact the service operator when Stripe shows a completed change for the same organisation but Metra remains stale after a reasonable processing delay. Do not send card details, Stripe secrets, or access tokens in a support request.

Roles and permissions