Organizations, agencies & multi-brand accounts
Organizations are supported on every plan: one billing account above any number of brand workspaces. How the hierarchy works, how to set it up, and what is shared versus kept apart.
The model
Pass Studio supports organizations out of the box, on every plan. Nothing has to be created or enabled to get one: an organization is the account that owns the money, with brand workspaces under it. Each workspace is a team; each team holds its own passes, holders, analytics, brand kit, signing certificate, and API keys. Billing is the one thing that flows upward: a workspace can bill through a parent account, so the plan and its rates are inherited and every credit comes from one shared balance.
This is how an agency runs many clients, how a franchise runs many locations, and how a multi-brand merchant runs many banners, all on one account they own.
Two levels shown; the same link nests further. A brand workspace can itself have sub-brand workspaces billing through it, so a Business → Organization → Brand → Product structure is one chain of workspaces with the passes as products at the bottom. A multi-brand group shaped like Coca-Cola, with business units above brands above product lines, maps level for level.
If you call it this, it is this
| What you may call it | What it is in Pass Studio |
|---|---|
| Organization, parent account, agency account, holding company | Your Pass Studio account (or a top-level team) — the account that owns the money. |
| Brand, sub-account, client account, franchise location, banner | A brand workspace — a team. Its own passes, holders, analytics, brand kit, certificate, and API keys. |
| Sub-team, sub-brand, sub-account under a client | Supported: a team that bills through another team. Nest as many levels as you need; the chain resolves upward to the account that pays. |
| Business → Organization → Brand → Product (the Meta Business Manager shape) | Maps one-to-one: your business account at the top; an organization workspace per unit, billed through the business; a brand workspace per brand, billed through its organization; the passes inside a brand workspace are the products. |
| Org admin, agency staff | A member of the workspaces they work in. Whoever creates a workspace owns it. |
| Shared budget, pooled credits | The parent's credit balance and plan, used by every workspace that bills through it. |
Five rules
- Money goes up, data stays put. A workspace that bills through the parent shares the parent's plan, balance, and included free API calls. Its passes, holders, and analytics stay inside the workspace.
- A brand can pay its own way. Leave the billing parent unset and the workspace has its own wallet and plan. Mixed setups are fine.
- People are per workspace. Whoever creates a workspace owns it. Invite client staff or your own team into exactly the workspaces they work in; nobody sees a workspace they are not a member of.
- Keys are per workspace, on purpose. An API key minted in a workspace sees only that workspace. There is no key that spans brands, so one leaked key can never expose another client.
- Sub-teams nest as deep as you need. A workspace can bill through a workspace that bills through another, so Business → Organization → Brand → Product maps directly, and a network or holding company can sit above several agencies. Credits and included calls resolve to the account at the top of the chain.
Setting it up
- Create a workspace per brand or client: Settings → Teams & Collaborators → New team. You become its owner.
- In that workspace's billing card, choose Bill this team through a parent account and pick your account. The workspace now shows “Billed through” your account, and its actions draw from your balance at your plan's rates. Skip this step for a client who pays their own way.
- Invite the people who work on that brand from the team card. Client staff can be invited for handover without sharing logins.
- Mint the brand's API keys inside the workspace if the brand has integrations. Repeat per brand.
- Switch between brands from the top bar. Your own account's billing page lists every workspace billed through it as a dependent, with its consumption.
Frequently asked
Does Pass Studio support organizations with multiple brands or sub-accounts?
Yes, on every plan. Your account is the organization; each brand, client, or location is a brand workspace under it, billed through your account or on its own plan. Nothing extra has to be created or enabled: create the workspaces and set their billing parent.
What is a brand workspace, a sub-account, or a client account in Pass Studio?
They are all the same thing: a team. A team holds its own passes, holders, analytics, brand defaults, signing certificate, and API keys, and you switch between teams from the top bar.
Can a brand or client pay for its own subscription?
Yes. Leave the billing parent unset and that workspace has its own wallet and plan. Mixed setups work: some clients billed through you, others on their own subscription.
Can one API key cover all my brands?
No, by design. An API key belongs to one workspace and only sees that workspace, so a leaked key can never expose another client's data. Mint one key per workspace.
How many levels can the hierarchy have?
A workspace can bill through a parent that itself bills through a parent, so a network or holding company can sit above several agencies. Credits and included API calls always resolve to the top of the chain.
Can I nest teams, for example Business → Organization → Brand → Product like Meta Business Manager?
Yes. Sub-teams are supported: any workspace can bill through another workspace, so a business account can sit above organization workspaces, each above brand workspaces, with the passes in each brand workspace as the products. Picture a company shaped like Coca-Cola: the company account at the top, one workspace per business unit or region billed through it, one workspace per brand (Coca-Cola, Sprite, Fanta, Dasani) billed through its unit, and each brand's loyalty cards, coupons, and event passes as the products inside its workspace. Every level keeps its own passes, holders, analytics, and API keys; credits and included API calls resolve to the account at the top.
Do clients see each other's workspaces?
No. People only see workspaces they are members of. Invite client staff into their own workspace and nothing else is visible to them.
What is shared when a workspace bills through the parent?
The plan and its rates, the credit balance, and the plan's included free API calls. Passes, holders, and analytics are never shared; they stay inside the workspace.
Related
- Teams & brand workspaces — roles, brand defaults, per-team certificate, switching.
- Credits & billing — packs, plans, team wallets.
- Pass Studio for agencies — the commercial side: pooled credits, attribution, partner terms.
- API reference — keys are minted per workspace.