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

# Members and roles

> Invite teammates, assign roles, and keep each person on a need-to-know basis.

## Roles

| Role          | Playground | API keys                     | Billing   | Admin settings |
| ------------- | ---------- | ---------------------------- | --------- | -------------- |
| **Owner**     | full       | full                         | full      | full           |
| **Admin**     | full       | full                         | view only | full           |
| **Developer** | full       | create & manage **own** keys | —         | —              |
| **Billing**   | full       | —                            | full      | —              |
| **Viewer**    | read-only  | —                            | —         | —              |

Only **one owner** per workspace (workspace creator). Transfer ownership via Settings → Members → `⋯` menu.

## Inviting

Settings → **Members** → **Invite** → enter email + pick role. The invitee gets an email with a secure link (24-hour expiry) to accept.

Accepted invitations become active immediately.

## Billing role

The Billing role combines **financial access with basic product use**:

* Can view and change the plan, purchase topups, update payment methods
* Can manage budget alerts and view usage
* Can use Playground (own chats only)
* **Cannot** manage API keys or Files
* **Cannot** see other members' chat content

Useful for finance / ops teammates who need to manage credits and also evaluate the product.

## Developer role

Developers manage **their own** API keys. They can't see or revoke keys owned by Admins or other Developers. Quotas set at the plan and member levels still apply.

## Changing roles

Owner and Admins can change roles via the member row `⋯` menu. Role changes take effect immediately (their current session refreshes).

## Removing a member

Settings → Members → `⋯` → **Remove**. Removed members:

* Lose access to the workspace immediately
* Their API keys are revoked
* Their chats remain (owned by the removed user for attribution) — Admins can fork or delete