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

# Roles & permissions

> What Owner, Admin, and Member can each do.

ServiceBooked has three roles. Permissions are simpler than enterprise CRMs — by design.

## Permissions matrix

| Action                                               | Owner | Admin | Member |
| ---------------------------------------------------- | ----- | ----- | ------ |
| **View dashboard**                                   | ✓     | ✓     | ✓      |
| **Read all conversations / contacts / appointments** | ✓     | ✓     | ✓      |
| **Reply to conversations / take over from AI**       | ✓     | ✓     | ✓      |
| **Create / edit contacts**                           | ✓     | ✓     | ✓      |
| **Create / edit deals**                              | ✓     | ✓     | ✓      |
| **Create / edit tasks (own + assigned)**             | ✓     | ✓     | ✓      |
| **Send review requests**                             | ✓     | ✓     | ✓      |
| **Run reactivation campaigns**                       | ✓     | ✓     | —      |
| **Configure forms**                                  | ✓     | ✓     | —      |
| **Configure widget**                                 | ✓     | ✓     | —      |
| **Configure pipeline / stages / tags**               | ✓     | ✓     | —      |
| **Configure integrations (calendar, Slack)**         | ✓     | ✓     | —      |
| **Configure auto-text / voice AI Receptionist**      | ✓     | ✓     | —      |
| **Edit knowledge base**                              | ✓     | ✓     | —      |
| **Invite / remove members**                          | ✓     | ✓     | —      |
| **Change member roles (admin ↔ member)**             | ✓     | ✓     | —      |
| **View billing**                                     | ✓     | ✓     | —      |
| **Change plans / cancel subscription**               | ✓     | —     | —      |
| **Edit business profile**                            | ✓     | ✓     | —      |
| **Configure branding / white-label**                 | ✓     | ✓     | —      |
| **Delete the organization**                          | ✓     | —     | —      |
| **Transfer ownership**                               | ✓     | —     | —      |

## When to pick which role

### Owner

There's exactly one. It's you, by default. You should only transfer it when you're literally handing the business over.

### Admin

Use for: business partners, an office manager, a senior employee, or anyone you trust to configure the system. Most teammates in small operations end up as Admin because there's overhead to constantly bumping a Member up.

### Member

Use for: techs in the field, VAs, junior employees, anyone you specifically don't want changing settings. They can still pick up conversations, create contacts, and work the pipeline — they just can't reconfigure how the system works.

## Edge cases

### "I want my VA to manage Slack notifications but not change the calendar."

Make them Admin and trust them. Or talk to support about more granular permissions — we may build per-feature ACLs in the future, but they don't exist today.

### "I want a sales team that only sees their own deals."

Not currently supported. All team members see all org data. If this is a hard requirement for your business, talk to support — we can sometimes provision separate organizations that share a phone number, depending on the case.

### "I want to give a one-time consultant temporary access."

Invite them, do the work, remove them. Their account doesn't get deleted (they may belong to other orgs), but they lose access to YOUR org immediately.

## Next

You're done with Team. Next:

<Card title="Billing" icon="credit-card" href="/billing/plans-and-limits">
  Plans, limits, upgrades, invoices.
</Card>