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

# Roles and permissions (Admin, Member, Manager, Staff)

> Roles decide what each person can see and do in Cura.

Roles decide what each person can see and do in Cura. Getting them right means owners stay in control, while staff get exactly the access they need — no more, no less.

Cura uses two levels of roles. One sits at the **account** level (your whole organization), the other at the **workspace** level (a single location). Everyone has one account role; people also get a role in each workspace they're added to.

***

## Account roles: Admin and Member

When you invite someone to your account, they become one of two things.

* **Admin (`org:admin`)** — full control of the account. Admins can create and delete workspaces, invite people, set everyone's roles, manage teams, and reach **every** workspace. This is the role for owners and trusted managers.
* **Member (`org:member`)** — a regular team member. Members only get access to the specific workspaces an admin grants them, with the workspace role the admin chooses.

<Note>
  Admins automatically act as a **manager** in every workspace on the account — even ones they were never explicitly added to. That's by design, so owners never get locked out of a location.
</Note>

## Workspace roles: Manager and Staff

Within each workspace, every person has one of two roles. The same person can be a manager in one workspace and staff in another.

* **Manager** — the lead role for a location. Managers run the day-to-day of the workspace and its team.
* **Staff** — the front-line role. Staff work the Inbox: reading and replying to customers, taking over from the AI, and handling bookings.

## How the two levels fit together

Think of it as access in two parts:

* Your **account role** decides whether you can run the *organization* (Admin) or just *take part* in it (Member).
* Your **workspace role** decides what you can do *inside a particular location* (Manager or Staff).

A practical example: an owner is an **Admin** (and so a manager everywhere). A branch manager is a **Member** of the account but a **Manager** in their branch's workspace. A receptionist is a **Member** with the **Staff** role in the one workspace they work in.

## Quick reference

| Role        | Level     | Who it's for          | Key abilities                                                                                            |
| ----------- | --------- | --------------------- | -------------------------------------------------------------------------------------------------------- |
| **Admin**   | Account   | Owners, trusted leads | Everything: create/delete workspaces, invite people, set roles, manage teams; manager in every workspace |
| **Member**  | Account   | Everyone else         | Access only to granted workspaces, with the role given there                                             |
| **Manager** | Workspace | Branch leads          | Lead the workspace and its team day to day                                                               |
| **Staff**   | Workspace | Front-desk staff      | Work the Inbox: reply, take over from the AI, handle bookings                                            |

<Tip>
  Hand out **Admin** sparingly — it's the keys to the whole business. For most of your team, **Member** plus a workspace role gives them everything they need.
</Tip>

***

### Related articles

* [Inviting team members](/team/inviting-team-members)
* [Workspaces explained](/team/workspaces-explained)
* [Teams and team leads](/team/teams-and-team-leads)
* [Setting an escalation contact](/team/escalation-contacts)