Billing
The subscription behind the account: what it costs, what it allows, and who is permitted to change it.
Overview
Billing belongs to the account rather than to any Environment: one subscription covers every application and every Environment inside it. It is account-wide authority, which means it comes from an administrator role rather than from administering people anywhere.
Card details are held by our payment provider, not by Canopy. Card numbers never reach our servers, which is also why changing a card happens in their secure form rather than in a Canopy field.
Reading and changing
Canopy distinguishes reading billing from changing it, and the Workspace's billing page follows that split.
The plan and how you pay
The page shows your current plan, its status, and what happens next: the date it renews, the date a cancellation takes effect, or the date a trial ends. Upgrading, switching between monthly and annual, and cancelling are all done here, and cancelling leaves access in place until the period ends before reverting to the free plan. Below it sit the payment methods, with one card charged automatically and others kept as backups, the billing contact and address that appear on every invoice and are used to calculate tax, and your registered tax IDs. An account managed by an account team shows a custom plan instead, and changes are made through them.
What the plan measures
A plan is not only a price, it is a set of allowances, and the page shows how much of each you have used: team members, meaning administrators plus pending invitations; monthly active users, meaning the distinct people who signed in to your application this calendar month; monthly active machine credentials, meaning the API keys and machine clients that authenticated this calendar month; and end-user single sign-on connections (admin SSO does not count).
They do not all behave the same way. Running out of team members refuses the next administrator invitation, and a plan with no single sign-on allowance refuses a new connection. Monthly active machine credentials refuses a new API key or machine client once the month's count has reached the limit; those already in use keep working. Monthly active users is not a wall for the people you already have: passing it warns you and, on a paid plan, is billed, and no existing end user is ever refused a sign-in because of it. Past the plan's sign-up ceiling, no new person can be created by any path: creating or importing one, accepting an invitation as someone new, self-service sign-up, a first single sign-on or directory sync. People who already exist are unaffected.
Next Step
Tell us how we can improve this guide.