---
title: "Organizations, workspaces and billing"
description: "Run several businesses or customers from one account: workspaces, organization roles, the three ways to pay, and what an agent can set up."
url: https://www.unitpost.com/guides/organizations
section: Guides
updated: 2026-11-17
---
# Organizations, workspaces and billing

## Organizations, workspaces and billing

> Run several businesses or customers from one account: workspaces, organization roles, the three ways to pay, and what an agent can set up.

Every workspace belongs to an organization. A workspace is where you send from: its own domains, contacts, suppressions, templates, keys, team and plan. The organization groups your workspaces and holds what they share: people with organization roles, a card, a shared plan, and API keys that create workspaces. Your first workspace makes the organization; it shows in the workspace switcher (with a gear by its name) once it has a second workspace, a card or a second person.

### One workspace per business

Give each business or customer its own workspace. Contacts, suppressions, domains and keys stay apart, so one business's list never mixes with another's, and each can have its own team.

### Organization roles

| Role | Billing: card, invoices, plans, shared plan | Create and close workspaces, organization keys | Invite people | Open any workspace |
| --- | --- | --- | --- | --- |
| Owner | Yes | Yes | Yes | Yes |
| Admin | No | Yes | Yes | Yes |
| Billing | Yes | No | No | No |
| Member | No | No | No | No |

- Owners, Admins and Billing members sign in with two-factor before any of these rights apply. Turn it on in Settings → Profile (/dashboard/settings/profile).
- Opening a workspace through the organization gives a limited Admin seat: no billing, API keys, team management or deleting the workspace.
- Whoever pays manages billing. A workspace that pays for itself is managed by its own Owner; one the organization pays for, by the organization's Owners and Billing members.

### Three ways to pay

|  | The workspace pays | The organization's card | The shared plan |
| --- | --- | --- | --- |
| Plan and allowance | Its own | Its own | One Starter or Growth plan, its allowance shared by the workspaces on it |
| Card | Its own | The organization's | The organization's |
| Pay-as-you-go | On its own invoice | On its plan's invoice | On the shared plan's invoice |
| Invoices | In the workspace, Settings → Billing | Organization → Billing, named by workspace | Organization → Billing, labelled Shared plan |
| Billing managed by | The workspace's Owner | The organization's Owners and Billing members | The organization's Owners and Billing members |
| How to get it | The default | Add the organization's card on Organization → Billing | On request: Organization → Billing → Shared plan → Request access |

- The workspace switcher shows each workspace's role and plan, for example "Owner · Starter · Shared" for one on the shared plan, or "Owner · No plan yet".
- A plan for a workspace on the organization's card is charged to that card at once, with no payment page in between, so the dashboard asks you to confirm it first ("Charge <organization>'s card?" with the plan and price).
- The Wallet guide (/guides/wallet#wallet-shared-usage) covers the shared plan in detail: caps per workspace, alerts, privacy and how to leave it.

### Switching who pays

- A free workspace switches at once, either way.
- A workspace on a paid plan switches when its current paid period ends. Its plan, allowance and any running promotion carry over, and it never drops to Free in between. Until then its plan can't change; cancel the switch on its Settings → Billing → Paid by.
- Moving onto the organization's card takes one person who is both the workspace's Owner and an organization Owner or Billing member. Moving back to its own card takes its Owner and a card of its own.
- A workspace with a paid plan of its own joins the shared plan once that plan has ended. One that leaves the shared plan moves to Free if its Owner has no other free workspace, and otherwise needs a plan of its own; what it used that period stays on the shared plan. Its Settings → Billing then says when the shared plan has room for it, with a link to add it back.

### Step by step

Move a workspace onto the organization's card. Add the card on Organization → Billing. Then, in the workspace, Settings → Billing → Paid by → Move to <organization>'s card. A free workspace moves at once; one on a paid plan moves when its period ends (Paid by shows the date, and Cancel switch stops it).

Buy a plan for a workspace on the organization's card. In the workspace, Settings → Billing → Change plan, pick the plan, and confirm the charge to the organization's card. It renews on the card, and its invoices are the organization's, each naming the workspace.

Shared plan. On Organization → Billing: Request access, and once Unitpost approves it, buy it in one checkout (pick the workspaces it covers; a promotion code goes on the payment page). Add workspace puts another on it, or choose the shared plan when you create a workspace. Each row's menu sets a cap or removes the workspace. Upgrade moves to a bigger allowance now (you pay the difference today and the period restarts); End at period end stops it renewing, and Keep plan undoes that. When every place is taken, Ask for more reaches support.

### Limits

- One free workspace per person. Any other workspace you own needs a plan: its own, one on the organization's card, or the shared plan.
- The organization's card pays for up to 3 workspaces until its first paid invoice, then 10. Support raises it.
- The shared plan covers up to 3 workspaces on Starter and 10 on Growth. Support raises it: when it's full, Organization → Billing → Ask for more.
- Creating workspaces by API needs Unitpost to approve the organization first (Organization → API → Request access). The Owner can set which plans keys may choose, the largest plan price and a monthly limit on new workspaces.

### What an agent can set up

An agent connected with an organization key (`ok_live_…`, over the API (/docs/platform/organizations), the CLI or MCP) can do the day-to-day setup. Steps that involve a card, an approval or a new key stay with a person in the dashboard. Over MCP the key also tells the server which organization it is; the CLI (/docs/cli#organization-keys) reads the key from `UNITPOST_ORG_KEY` and the organization from `--org` or `UNITPOST_ORGANIZATION_ID`.

| Step | Who does it |
| --- | --- |
| Sign up and turn on two-factor | A person, in the dashboard |
| Ask for API access and for the shared plan | An Owner (a Billing member can ask for the shared plan), in the dashboard |
| Approve them | Unitpost reviews each organization |
| Add the organization's card; buy, upgrade or end the shared plan (a promotion code goes on the payment page) | An Owner or Billing member, in the dashboard |
| Make an organization key and set the API rules | An Owner, on Organization → API → Create key, confirmed with their authenticator. For shared-plan work tick "Can change plans and use the shared plan" (`organizations:billing`, which only an Owner can give) |
| Create workspaces (`shared_plan: true` puts one straight on the shared plan), rename, close and restore them | The agent: `POST /v1/organizations/{id}/workspaces`, MCP `organization_workspaces_*` |
| Add a workspace to the shared plan, cap what it draws, take it off | The agent, with a key that has `organizations:billing` |
| Mint a key for each workspace | The agent: MCP `organization_workspace_keys_create` |
| Domains, contacts, templates and sending inside a workspace | The agent, with that workspace's key |
| One webhook endpoint for every workspace; usage per workspace | The agent, with the organization key |
| Invite people and change roles | A person, in the dashboard |

> **NOTE:** Ask Unit, the assistant in the dashboard, works inside one workspace. It can explain all of this, but it doesn't create workspaces or change the organization's billing.

### From sign-up to an agent-run setup

- Sign up and name your first workspace after your first business. Turn on two-factor in Settings → Profile.
- Open the workspace switcher → New workspace and create your second business's workspace. It waits for a plan: don't buy one for it. Your organization now shows in the switcher.
- In the organization, ask for the shared plan (Billing → Shared plan → Request access) and, if an agent will create workspaces, for API access (API → Request access).
- Once Unitpost approves, buy the shared plan on Organization → Billing: pick the plan and the workspaces it covers, and enter any promotion code on the payment page.
- On Organization → API → Create key, tick "Can change plans and use the shared plan" (`organizations:billing`), confirm with your authenticator, and copy the key (`ok_live_…`, shown once) to your agent.
- The agent creates the remaining workspaces with `shared_plan: true`, mints a key for each, sets caps if you want them, and sets up each workspace with its own key.

## Related

- [Wallet](https://www.unitpost.com/guides/wallet): The monthly sending allowance on a paid plan. Email and SMS draw it, and sending pauses once overage hits the cap.
- [Migration Assistant](https://www.unitpost.com/guides/migration): Move from Resend, SendGrid, Mailgun, Postmark, Brevo, Loops, Mailchimp, MailerLite, Kit, beehiiv or Klaviyo with one API key.
- [Integrations](https://www.unitpost.com/guides/integrations): Connect forms, sheets, no-code tools, payments, stores, auth providers and CRMs to Unitpost through the API, webhooks or SMTP.
