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

# Workspaces & teams

> Organize access, billing, and resources with workspaces and team members.

Everything in Omnia is scoped to a **workspace**: API keys, wallet, usage,
dedicated endpoints, and fine-tuning jobs all belong to one. You manage your
workspace and its members from the dashboard.

<Note>
  Team and billing features are **dashboard-managed**, not a public API. The API is
  for inference and resource management (dedicated endpoints, fine-tuning),
  authenticated with a workspace key. There is no API to create workspaces, invite
  members, or move funds.
</Note>

## Workspaces

Your workspace is created during onboarding, and each account has **one
workspace**; multiple workspaces per account are not currently supported. The
workspace is the unit of:

* **Billing**: one prepaid wallet per workspace. Dedicated GPU-hours and
  fine-tuning trained-token charges all draw from this wallet.
* **Access**: every API key resolves to exactly one workspace, and all usage
  from that key is attributed to it.
* **Resources**: dedicated endpoints and fine-tuning jobs live in the workspace
  and are visible to its members.

## How keys resolve to a workspace

An API key uniquely identifies its workspace. When you make an inference or
management call, Omnia resolves the key to its workspace and applies that
workspace's catalog, wallet, and resources. A key cannot act on another
workspace, and it cannot override the workspace it belongs to.

## Team members and roles

Invite teammates to your workspace from the dashboard. Members have roles that
control what they can do:

| Role       | Can do                                                                   |
| ---------- | ------------------------------------------------------------------------ |
| **Owner**  | Full control: billing, members, keys, deploy, delete.                    |
| **Admin**  | Manage keys, deploy dedicated endpoints, start fine-tuning.              |
| **Member** | Use the platform (inference, playground) with the workspace's resources. |

Certain actions are **admin-gated**: creating, updating, or deleting dedicated
endpoints and launching fine-tuning jobs all require an owner or admin. Managing
billing is owner/admin as well. Regular members can run inference against shared
models and existing dedicated endpoints.

## Inviting members

<Steps>
  <Step title="Open team settings">
    In the dashboard, go to your workspace's team settings.
  </Step>

  <Step title="Send an invitation">
    Enter the teammate's email and choose their role. They receive an invitation
    link.
  </Step>

  <Step title="They accept">
    The invitee accepts and joins your workspace with the role you assigned.
  </Step>
</Steps>

## API keys and members

Each API key is created by a member and belongs to the workspace. Usage from a
key is attributed to the workspace, and admin-gated management operations respect
the member's role. Revoke a key any time from the dashboard.

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/authentication">
    How workspace API keys work.
  </Card>

  <Card title="Billing" icon="wallet" href="/concepts/billing">
    How the per-workspace wallet is charged.
  </Card>
</CardGroup>