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

# Team & roles

> One organization, one balance, one catalog, with roles scoping who can spend, ship, and administer.

Everything belongs to your **organization**: API keys, credits, usage, and billing. Whoever signs up creates it and becomes its first **org admin**; everyone else joins by invitation from the [Organization](https://platform.pearlresearch.ai/organization) page and gets a role that scopes what they can do.

## What each role can do

| Capability | Org admin | Billing admin | Developer | Viewer |
| - | :-: | :-: | :-: | :-: |
| Dashboard, Models, Analytics, Docs | ✓ | ✓ | ✓ | ✓ |
| Playground | ✓ | — | ✓ | — |
| View API keys | ✓ | — | ✓ | ✓ |
| Create / revoke / delete API keys | ✓ | — | ✓ | — |
| Create / revoke / delete management keys | ✓ | — | — | — |
| Billing: top-ups, auto-recharge, payments, invoices | ✓ | ✓ | — | — |
| Invite teammates / revoke invitations | ✓ | ✓ | — | — |
| Change member roles / remove members | ✓ | — | — | — |
| Grant the org-admin role | ✓ | — | — | — |

In practice, the roles map to jobs:

* **Org admin**, full control, including the only role that can manage members and grant org-admin. Keep at least two, so no one person is a single point of failure.
* **Billing admin**, finance without engineering access: credits, auto-recharge, payment history, invoices, and inviting teammates.
* **Developer**, day-to-day API work: keys and the playground, but no spending controls.
* **Viewer**, read-only visibility (usage, models, existing key names) for stakeholders who ship nothing.

## Inviting teammates

Enter an email and pick a role, the invitee gets an email, and the pending invitation (with a copyable invite link) stays listed until it's accepted or revoked. Accepting routes through sign-in and lands the new member *inside your organization*, they never create a duplicate org of their own. Roles can be changed (and members removed) by an org admin at any time; changes take effect on the member's next session refresh.

> [!NOTE]
>
> Stripe receipts and invoices go to your organization's **billing contact**: the earliest-joined billing admin, falling back to the earliest org admin. Changing those roles re-points it automatically.


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