1. Docs
  2. Billing

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, but the Workspace's billing page asks for the managing capability today.

Managing covers everything on the page: the plan, cards, the billing contact and address, tax IDs, and paying an invoice.Reading covers invoices, the subscription, and usage. It is enforced by the API, but there is no read-only billing screen: someone holding only the read capability is offered no Billing entry at all.Neither is implied by administering people. Someone who runs a region day to day usually holds neither.

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 decide your tax region and currency, 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: Console users, meaning administrators plus pending invitations; monthly active users, meaning the distinct people who signed in to your application this calendar month; monthly active API keys; and single sign-on connections.

They do not all behave the same way. Running out of Console users refuses the next administrator invitation, and a plan with no single sign-on allowance refuses a new connection. Monthly active users is not a wall: passing it warns you and, on a paid plan, is billed, and no end user is ever refused a sign-in because of it.

Next Step

The remaining account-wide surface is small: Account settings covers the details that identify your organization.

Environment
API version
v1.0
On this page Was this page helpful?

Tell us how we can improve this guide.