Billing & Account overview
How workspaces, entitlements, and subscriptions fit together on Integraph — the vocabulary you need before subscribing or managing an org.
Who this section is for
Anyone who needs to subscribe to an Integraph tool, manage who on their team has access to what, or understand why a particular member of their organization can or cannot open a particular tool. If you only use a personal account and never invite collaborators, most of this is still useful — but the sections on org management and transfers can be skipped.
Three concepts to get straight first
The billing system is built on three ideas that are easy to confuse:
1. Workspace: personal vs organization
Every user has a personal workspace the moment they sign up. You can also create team organizations (“orgs”) and invite other users to them. When you’re signed in, the app shows a workspace switcher — everything you do (projects, tool instances, billing) is scoped to the workspace you’re currently in.
Two different settings pages exist and they are not interchangeable:
- Account Settings — always about you, the signed-in user. Reached from the avatar menu’s Account Settings entry.
- Organization Settings — about the currently-selected team org. Reached from the avatar menu’s Organization Settings entry, which only appears when you’re in a team workspace (not when you’re in your personal workspace).
2. Subscription: who is paying
A subscription is a Stripe commitment to pay for access to one or more tools at one or more access tiers. Subscriptions belong to a single Stripe customer — either your personal account or one of your team orgs. Nothing else on Integraph is a subscription: not a project, not a tool instance, not a user.
3. Entitlement: who can actually use a tool
An entitlement is a per-user, per-tool record that says “this user can open this tool at this access tier”. Entitlements are always granted by a subscription, and they are always granted to a user — but the granting subscription might live on your personal account or on an org you belong to.
In practice this means every user’s access to a tool is the union of all their entitlements, regardless of which workspace originated them. If your personal account has an ACS subscription and your employer’s org grants you ACS, you are still “ACS-entitled” once — but if your personal subscription is cancelled, the org grant keeps you running without interruption.
The common flows at a glance
| You want to… | Start here |
|---|---|
| Subscribe to a tool for yourself | Subscriptions and trials |
| Give a colleague access via your org | Managing org entitlements |
| See what access you’re paying for and what you get from other orgs | Cross-context visibility |
| Move a personal subscription onto an org you just created | Transferring to an org |
| Cancel or reactivate a subscription | Cancelling and reactivating |
| View invoices or update your card | Payment methods and invoices |
| Diagnose something that looks wrong | Troubleshooting |
A worked example
Imagine Alice signs up and subscribes to ACS on her personal account during a 14-day trial. Three days later her employer Bob creates a team org “Acme Engineering”, invites Alice, and subscribes Acme to LGS. Alice now holds two entitlements:
- ACS (personal tier) — granted by Alice’s personal subscription.
- LGS (team web tier) — granted by Acme Engineering’s subscription.
When Alice opens her Account Settings → Billing tab she sees both entitlements, but only the ACS row is editable. The LGS row is read-only with a “Manage in Acme Engineering Settings” link, because Bob (the org owner) controls Acme’s subscription. If Alice then cancels her personal ACS subscription, the LGS entitlement keeps her Acme access intact — but ACS disappears from her account at the end of the billing period.
This is what “unified cross-org entitlement visibility” means in practice, and it’s what the next few pages document in detail.