Client accounts under your brand
Open in
A client account holds the products an agency builds for one client, on the client's own Stripe, behind a console that carries the agency's brand.
Filled: what the client's people see, always under your brand.
What each client may do
ClientAccount.grant sets what a client's people may do. Each grant holds the ones above it in this table.
| Grant | A client's person may | Typical for |
|---|---|---|
read | See its products, usage, Customers and a statement per period | Every client |
prices | Change the Offer's prices and plans, which deploy as a reviewed change | A client that runs its own pricing |
deploy | Deploy a change your team prepared, after its review | A client with its own developer |
own | Accept the product, which moves it to its own workspace | The end of an engagement |
A client never sees another client, your other products or your workspace's plan. Your team sees every client. Every act a client's person takes in the client console is a Verb on the platform API, open to its agents under their own token.
The console under your brand
Workspace.brand sets one brand for every client console and every email it sends, on Team and Scale.
| Part | Set by | What a client's people see |
|---|---|---|
| Name, logo and colour | name, logo, color | Your mark on every screen, receipt and email; nothing names APIs.Dev |
| The address | domain, one of your Domains | console.yourstudio.com, checked once by one DNS record |
| Sign-in | Your Domain's sign-in, with passkeys and SSO | A sign-in page and its emails from you |
| Sending | from, an address on your Domain | Invitations, statements and alerts from that address |
| Help | support, an address or a URL | Your own help, never the platform's |
When a request is refused
Each refusal is a Problem with its cure, and changes nothing that serves.
| What happens | The answer |
|---|---|
| Your team opens a client account past what the plan includes | 402 client_limit, with an add-on in offers |
| A product of a client goes Live, or charges, before the client connects Stripe | 409 stripe_not_connected; it keeps serving in Test |
| A client's person deploys, or changes prices, above the account's grant | 403 grant_exceeded, naming the grant it needs |
| Anyone deploys or reprices a product whose handoff waits | 409 handoff_open, with the handoff's link |
| The owner never accepts the invitation | The account turns expired after 14 days; ClientAccount.invite sends a new one |
| Your workspace drops below Team | Each console turns read-only and no account opens; every client keeps its Stripe and its Customers |
A client's Customers never meet any of these. Its products keep serving whatever the account's state.
A studio and its first client
A studio brands its console, then opens an account for a client with a read grant for its finance lead.
{
"brand": {
"name": "Northwind Studio",
"logo": "https:HTTP/1.1 201 Created
Content-Type:That is PUT https:, then POST https:.
Numbers, statements and handoff
| What | How many, or how long |
|---|---|
| Client accounts | 10 with Team and 25 with Scale; each past them is an add-on on /pricing |
| People in one client account | 50, one of them its owner |
| An invitation | 14 days, then expired |
| A logo | SVG or PNG, 200 KB at most |
| A handoff | Waits 30 days for the owner, then lapses and the product stays where it was |
Each client gets a statement per period in your name: its products' usage, revenue and the platform's charges.
A handoff ends the build. Kept, the product stays in your workspace and the client keeps its console. Moved, it goes to the client's workspace by transfer, and nothing its Customers see changes.
Your workspace
Your own account with APIs.Dev: plan and take, allowances and spend caps, verification, the Stripe connection, going Live, suspension and client accounts.
A private deploy
The site, the portal and the docs behind an enterprise sign-in, an IP allowlist or both, with the API on its Keys and the prices public while the product sells.