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

# Roles & Access

> Organizations isolate tenant data; role-based access control (owner, admin, member, viewer) governs who can do what.

## Organizations (tenants)

Everything in Orca lives inside an **organization** — your tenant. Agents, profiles, secrets, keys, runs, and usage all belong to one organization, and **data is isolated per tenant**: one organization can never see or reach another's data.

The tenant is always derived from your credential — an **[API key](/concepts/api-keys)** carries its tenant, and a dashboard session carries yours. (Orca strips any `X-Tenant-ID` header, so the tenant can't be spoofed by a request.)

## Roles (RBAC)

Every member of an organization has one of four roles:

| Role       | Can do                                                                                                                                                      |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **owner**  | Everything an admin can, plus full organization ownership.                                                                                                  |
| **admin**  | Manage **[Secrets](/concepts/secrets)**, **publish** agents, **delete** agents, and manage the org: rename, change logo, delete, and invite/remove members. |
| **member** | Build and run agents. **Read-only** affordances on admin-only surfaces (e.g. can see that Secrets exist, but not manage them).                              |
| **viewer** | Read-only access.                                                                                                                                           |

### Admin-only surfaces

These actions require `admin` (or `owner`):

* Managing **Secrets** (create, rotate, delete).
* **Publishing** an agent.
* **Deleting** an agent.
* **Organization management** — rename, logo, delete, and inviting or removing members.

Members see read-only versions of these surfaces rather than the controls.

## API keys inherit their creator's role

An **[API key](/concepts/api-keys)** takes on the role of whoever created it. A key issued by an admin can reach admin-only surfaces; a key issued by a member is limited to member-level actions. Choose the issuing account deliberately to scope a key.

## Managing the organization

Organization lifecycle and membership are managed in the dashboard under **Organization** and **Members** — where you rename the org, set its logo, and invite or remove people. See **[Workspace](/dashboard/workspace)**.

## Related

<CardGroup cols={3}>
  <Card title="Workspace & members" icon="users" href="/dashboard/workspace">
    Manage the org and its members.
  </Card>

  <Card title="API Keys" icon="key" href="/concepts/api-keys">
    Keys inherit their creator's role.
  </Card>

  <Card title="Secrets" icon="lock" href="/concepts/secrets">
    An admin-only surface.
  </Card>
</CardGroup>