# Roles and console access

> See what each console role can do, and how API keys are authorized separately from roles.

Canonical guide: <https://engine.neraperla.com/docs/rbac>

Raw Markdown: <https://engine.neraperla.com/docs/raw/rbac.md>

OpenAPI: <https://engine.neraperla.com/v1/openapi.json>

Console users belong to an organization with one role: `owner`, `admin`, `member`, `billing`, or `viewer`.

| Role | What it can do |
|---|---|
| `owner` | Everything an administrator can, plus invite owners, change an owner's role, and remove an owner. An organization always keeps at least one owner. |
| `admin` | Everything `member` and `billing` can, plus: create, rename, and archive projects; create and revoke project and company-level API keys; approve AI-agent and connector access and revoke connections; invite and manage members other than owners; set quotas; manage brand profiles, offers, playbook templates, campaign schedules, and provider connections; and change organization settings. |
| `member` | Run enabled capabilities, start campaign cycles, cancel jobs, share playbooks, and read the project's work. |
| `billing` | Add credits; manage payment details and auto-recharge; create, change, and delete budgets; and manage project allowances (top-ups and reductions), project daily and monthly limits, and company limits. It can't run capabilities or manage projects, keys, or members. |
| `viewer` | Read-only. |

No organization role enables a capability. Capabilities are enabled for your organization by Blackpearl: when `GET /v1/capabilities` lists one with `enabled: false`, request access. See [Capabilities and entitlements](https://engine.neraperla.com/docs/feature-flags).

## API keys are not user sessions

The console authenticates with an HTTP-only session cookie. Public `/v1` integrations don't use that cookie and don't inherit anyone's role: authority comes from the key type, as described in [Authentication](https://engine.neraperla.com/docs/authentication).

- A project key acts only in its own project. It can read its own project, limits, allowance, and charges, but can't manage projects.
- A company-level key acts in every project of the organization, and over the API it can create, rename, and archive projects and change their allowances and limits. See [Managing your clients with projects](https://engine.neraperla.com/docs/projects).

Removing a member does not revoke the API keys they created; connector connections they approved are revoked. Revoke keys you no longer need under **API keys**.

Organization invitations are deliberate and role-specific. Do not share personal credentials or API keys to work around missing membership. Administrators should issue the appropriate membership and create separate keys for deployed services: a project key per service and environment, or a company-level key for an integration that serves several projects.
