> For clean Markdown of any page, append `.md` to the page URL.
> For a complete documentation index, see https://docs.sarvam.ai/llms.txt.
> For full documentation content in one file, see https://docs.sarvam.ai/llms-full.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.sarvam.ai/_mcp/server.

# Create an organisation

> Step-by-step guide to creating a new Sarvam organisation from the dashboard, when a separate organisation is the right choice, and what does not carry over from your existing account.

An **organisation** is a billing and identity boundary: its own credit balance, its own payment history, and its own member list. You already have one from signup, so you only need a second organisation in specific cases.

Before you create one, check that you actually want an organisation and not a workspace. Nothing is shared between organisations — credits, payment methods, members, and API keys all stay separate, and you will have to top up each organisation independently. If you just want to separate projects, teams, or environments while keeping one bill, [create a workspace](/api/platform/create-a-workspace) instead.

Create a separate organisation when:

* it is a **different legal entity** that needs its own invoices
* you manage a **client's account** on their behalf and they are billed directly
* you need a **hard separation** of credits and members, not just of API keys

## Steps

#### Open the organisation switcher

Click your organisation name at the top of the left sidebar. The switcher lists every organisation you belong to, with its workspace and member counts.

#### Click Add Workspace or Organisation

It sits at the bottom of the switcher.

#### Choose Add organisation

You will be asked to choose between a workspace and an organisation. Pick **Add organisation** — described as a separate billing entity with its own plan, invoices, and members.

#### Name it and create

Enter an **Organisation name**, optionally upload a logo (PNG, JPG, or WebP up to 2 MB), then click **Create organisation**. You can change both later in **Settings → Organisation → General**.

You become the **Owner** of the new organisation automatically, and a default workspace is created inside it.

## After creating it

The new organisation starts empty. To make it usable:

#### Add credits

Go to **Settings → Billing** and add credits. The new organisation has its own balance — credits from your other organisations do not carry over. See [Billing & payments](/api/platform/billing).

#### Create an API key

API keys belong to a workspace, not to the organisation. Open the new organisation's workspace and create a key under **API Keys**.

#### Invite your team

Members are per organisation, so people from your other organisations are not carried over. See [Invite your team](/api/platform/invite-your-team).

You can own up to **100 organisations** per account.

## Switching between organisations

Use the same switcher at the top of the sidebar. Your selected organisation determines which credits, members, workspaces, and API keys you are looking at everywhere in the dashboard, so check it before you create a key or add credits.

One organisation can be marked as your **default**, shown as `Default organisation: Yes` in **Settings → Organisation → General**. That is the one you land in when you sign in.