Platform FAQ

An organisation is your billing and identity boundary — credits, payment history, plan, and the member list live there. A workspace is a space inside the organisation for a project, team, or environment, and it is where API keys are created and where usage is attributed.

Rule of thumb: one organisation per company that gets a bill; one workspace per thing you want to separate.

Almost always a workspace. Workspaces give you separate API keys, separate access control, and per-workspace usage attribution while keeping one credit balance and one bill.

Create a new organisation only when you need a genuinely separate billing entity — a different legal entity, or a client account that is invoiced directly. Nothing is shared between organisations: separate credits, separate payment methods, separate members.

No. A new workspace uses the organisation’s existing credit balance straight away. A new organisation, on the other hand, starts with its own empty balance and needs its own credits.

Up to 100 workspaces per organisation, and you can own up to 100 organisations. Deleted workspaces do not count towards the limit.

Use the switcher at the top of the left sidebar. Your current selection decides which credits, members, workspaces, and API keys you are looking at everywhere in the dashboard — so check it before creating a key or adding credits.

One organisation can be your default, which is where you land when you sign in. You can see this as Default organisation under Settings → Organisation → General.

Not from the dashboard. Because a workspace’s usage and API keys are tied to the organisation that pays for them, moving one is a manual operation — contact us if you need it.

Two at the organisation level — Owner and Member — and three per workspace: Admin, Editor, and Viewer.

Organisation Owners are automatically Admin on every workspace, so you do not need to grant them workspace access explicitly.

Only organisation Owners. For a Member the Invite User button is disabled with the tooltip “Only org owners can invite users”, and the API rejects the request too — it is a real permission, not just a hidden button.

Creating workspaces, renaming the organisation, changing someone’s role, and removing members are also Owner-only and enforced the same way.

Everyone starts as an organisation Member with Editor access to the workspaces you picked during the invite. The invite dialog does not offer a role choice.

To make someone an Owner, invite them first, then use Edit user on their row and change Organisation role to Owner.

They have been invited but have not signed in and accepted yet. Pending rows offer Revoke invitation instead of the usual edit and remove actions.

No. An organisation must always have at least one Owner, so the final Owner cannot be demoted or removed. Promote someone else to Owner first.

Remove them from Settings → Organisation → Members, which revokes their access to the organisation and all its workspaces immediately.

Removing a person does not revoke API keys they created — keys belong to the workspace and keep working. Rotate any key you consider sensitive under API Keys.

No limit on the number of members. A single invite can grant access to up to 50 workspaces at once.

The invite dialog handles one person at a time. For bulk onboarding, contact us and we can load the invites for you.

The organisation. There is one balance per organisation, shared by every workspace, every API key, and every Sarvam product. There are no per-workspace balances or budgets.

Not today. Because there is a single organisation-level balance, per-workspace and per-key budgets do not exist. If you need hard spend separation, use a separate organisation, which has its own balance.

You can still see spend per workspace under Settings → Usage, since usage is attributed to the workspace a call came from.

No.

The organisation is out of credits. Add credits under Settings → Billing and calls resume immediately — no key rotation or redeploy needed. Enable auto-recharge to avoid it happening again.

If your balance looks healthy and you are still seeing 402, see Errors & Troubleshooting.

Most often the payment window was closed before it confirmed, in which case the charge is refunded automatically rather than converted to credits. Check Settings → Billing → Payment History first, then contact support with the payment reference if the money left your account and no refund appears.

Usually a special character or emoji in the billing address, which the payment provider rejects. Fix the billing address and contact support to have the invoice reissued.

Use Request enterprise plan on Settings → Plans & pricing. Enterprise covers higher rate limits, custom concurrency and throughput, volume discounts on credits, and dedicated support with SLAs.

To the workspace. That is why a key keeps working after the person who created it leaves, and why calls made with it are attributed to that workspace.

Up to 50 active keys per organisation. If you need more, contact the team — the cap is not self-serve.

Per account. All keys share the same rate limit pool — creating more keys does not buy more throughput. See Credits & Rate Limits.

One workspace per environment, with its own key in each. Rotating or revoking a staging key then never touches production traffic.

Organisation ID is under Settings → Organisation → General; workspace ID is under Settings → Workspace → General. Both have a copy button. Support will often ask for one of these.

The dropdown at the top of the settings sidebar switches between Organisation (org details, members, workspaces, billing and usage), Workspace (that workspace’s details and members), and Profile (your own account settings).

Yes. Model training is a toggle under Settings → Organisation → General, and only an Owner can change it. For retention windows, zero-data-retention, and custom retention periods, talk to us.

Yes — Session idle timeout under Settings → Organisation → General, Owner-only. It applies to everyone in the organisation.