> ## Documentation Index
> Fetch the complete documentation index at: https://docs.osvi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace

> Invite teammates, assign roles, work across sub-accounts, and find your API token

Everything in your Osvi account — agents, campaigns, call logs, numbers — belongs to one shared workspace. The **Workspace** section has four parts: **Members** (who's in it), **Sub-Accounts** (separate workspaces you have access to), **Concurrency** (how many calls each agent can run at once — see [Concurrency](https://docs.osvi.ai/platform/concurrency.md)), and **Settings** (your API token).

## Members

![User Management listing team members with their role, status, join date, and last activity](https://mintcdn.com/osviai/HSPh-lxIhx0ibZfT/images/Workspace/ws-user-management-light.png?fit=max\&auto=format\&n=HSPh-lxIhx0ibZfT\&q=85\&s=78c3de5f32a9d756a57dd62ddbb82420)

**Workspace → Members** lists everyone in the workspace with their role, status, when they joined, and when they were last active — so you can spot accounts nobody is using. Beside the member list are two more tabs: **Access Requests** and **Invitations**.

## Roles

| Role | Can do |
| - | - |
| **Admin** | Everything members can, plus: invite and remove users, change roles, and approve or reject pending users. |
| **Member** | Day-to-day platform work — building agents, running campaigns, reviewing conversations. |

## Inviting teammates

From **Workspace → Members**, click **Invite Members**, enter one or more email addresses, pick the role, and send. Invitees get an email link to join your workspace.

* Pending invitations are listed under **Invitations** with their status; you can **resend** one (after an hour) if it was missed, or **revoke** it.
* Users who request access to your workspace appear under **Access Requests**, where an admin **approves** or **rejects** them.

## Managing members

The members list shows each person's role and status (active, pending, revoked, expired). Admins can change a member's role or remove them from the workspace at any time.

> [!TIP]
>
> Keep at least two admins so account administration never depends on one person being available.

## Sub-accounts

![Sub-Accounts listing separate workspaces with their user and agent counts](https://mintcdn.com/osviai/HSPh-lxIhx0ibZfT/images/Workspace/ws-subaccount-light.png?fit=max\&auto=format\&n=HSPh-lxIhx0ibZfT\&q=85\&s=494726754baa514528a1118a2e7d61e2)

A sub-account is a workspace of its own, with its own agents, numbers and call logs. **Workspace → Sub-Accounts** lists the ones you can reach, with how many users and agents each has, and **Open** takes you into one in a new tab. Useful when you run Osvi for several brands, departments or clients and want their data kept apart.

## API token

Your workspace has one **API token**. It's what authenticates your systems when they talk to Osvi — without it, requests are rejected.

![Workspace Settings showing the account API token, hidden, with reveal and copy buttons](https://mintcdn.com/osviai/HSPh-lxIhx0ibZfT/images/Workspace/ws-settings-light.png?fit=max\&auto=format\&n=HSPh-lxIhx0ibZfT\&q=85\&s=ec1702af2bc13cfa6e6eb1e478fe0a51)

Find it under **Workspace → Settings → Account API Token**. It's masked by default — the eye reveals it, and the copy button puts it on your clipboard.

**Where it's used.** Send it in the `API-Token` header on every request to the Osvi API:

```http theme={null}
API-Token: <your-api-token>
```

That unlocks the things your own systems need to drive:

| What you can do | Where |
| - | - |
| **Place a call** from your product or backend, passing customer context | [Initiate a phone call](https://docs.osvi.ai/api-reference/endpoint/call_v1.md) |
| **Read call results** — details, transcripts, recordings | [Calls](https://docs.osvi.ai/api-reference/endpoint/list_calls.md) |
| **Run campaigns** — add contacts, check status | [Campaigns](https://docs.osvi.ai/api-reference/endpoint/campaign_add_contacts.md) |
| **Manage Do Not Disturb** numbers | [Do Not Disturb](https://docs.osvi.ai/api-reference/endpoint/dnd_list.md) |
| **List the agents** currently able to take calls | [List active agents](https://docs.osvi.ai/api-reference/endpoint/active_agents.md) |
| **Drive chat sessions** — create, send messages, hand to an operator | [Chat](https://docs.osvi.ai/api-reference/endpoint/chat/create_session.md) |

The [API reference](https://docs.osvi.ai/api-reference/introduction.md) has the full contract. Post-call [webhooks](https://docs.osvi.ai/api-reference/endpoint/webhook.md) are the other half of the loop: your systems call Osvi with the token, and Osvi calls your systems back with results.

> [!WARNING]
>
> The token is scoped to your whole workspace and carries the same power as your account. Keep it on your server, never in a browser, a mobile app, or a public repository. Anyone holding it can place calls that you pay for.

> [!NOTE]
>
> Building and configuring agents — prompts, tools, voices, evals — is done in the dashboard or with [Conductor](https://docs.osvi.ai/platform/conductor), not through the API. The token is for running calls and reading results.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.