Several workspaces
One agency, one bill, one client per workspace
A workspace is one company's customer data and one database. If you run customer state for eleven clients, that is eleven workspaces, and none of them can see another. What is shared is the bill and the person signing in.
Why separate at all
Isolation you can describe to a client
Each workspace is its own database, not a tenant column in a shared one. A query cannot accidentally cross a boundary, because there is no shared table to cross it in, and a client asking how their data is kept apart from the next client's gets an answer about architecture rather than about discipline.
It also means each client's data can be exported and handed over whole, or destroyed on request, without touching anybody else's.
- Switch without signing out
- One sign-in reaches every workspace you are a member of. The switcher is in the application, and your role can differ in each.
- One subscription
- Your plan covers the first workspace and each one after it is $10 a month, on one payment method and one invoice. Eleven clients on Solo is $129 a month. Adding a client is not adding a card.
- Handover
- Transfer ownership of a workspace to the client when the engagement ends. Their data goes with them and your access stops.
For a platform
Create a workspace without opening a browser
If you are embedding Indraft rather than running an agency, onboarding a tenant cannot contain a step where a human logs in. It does not have to: a credential holding the provisioning grant creates a workspace over the API, and a credential holding the export grant takes the nightly backup, neither of them able to read a CRM record they were not asked about.
Both grants are owner-only, and a credential is never more powerful than the person who created it. Demote them and the provisioning stops on the next call.
| Endpoint | Scope | What it does |
|---|---|---|
| GET /v1/export | data:export | Export every record, custom object type, and the change ledger, as one JSON file |
| GET /v1/workspaces | workspaces:provision | List the workspaces this credential can reach |
| POST /v1/workspaces | workspaces:provision | Create a workspace and return a credential scoped to it |
What to expect
What running eleven of these is actually like
Each workspace carries its own pipeline, its own custom fields, and its own agent connections, because two clients rarely sell the same way. There is no template that clones one workspace's configuration into the next, so the agent sets each one up, which takes a session.
Records and changes are one allowance spent across all of them, so a quiet client leaves room for a busy one and you size a plan against the whole book rather than against your largest account. What the extra workspaces cost is the per-workspace price above, not another copy of the plan.
People work the other way, because a person belongs to a workspace rather than to the account: each workspace gets the plan's full allowance of them, and anyone past it is priced per person in that workspace. Nobody is refused an invitation on a paid plan, and the whole bill still stops at the price of the cheapest plan that covers you.
What is not built yet
There is no cross-workspace reporting: no single view of every client's pipeline in one place. Each workspace is answered on its own, and rolling eleven of them into one number is something you would do outside Indraft today.