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

# Roles and permissions

> What owner, admin, member and viewer can do in aciona.me.

aciona.me has four roles per organization. A person's role applies inside that organization — the same person can be an admin in one and a viewer in another.

## The four roles

<Columns cols={2}>
  <Card title="Owner" icon="crown">
    Full control. The only role that manages the subscription and creates child organizations.
  </Card>

  <Card title="Admin" icon="settings">
    Configures the operational environment: teams, services, schedules, alert sources, integrations and members.
  </Card>

  <Card title="Member" icon="user">
    Takes part in on-call and acts on incidents. Does not change organization configuration.
  </Card>

  <Card title="Viewer" icon="eye">
    Read-only. Ideal for management, product and support to follow along with no risk of changing anything.
  </Card>
</Columns>

## Permission matrix

| Action                                          | Owner | Admin | Member | Viewer |
| ----------------------------------------------- | :---: | :---: | :----: | :----: |
| View the organization                           |   ✅   |   ✅   |    ✅   |    ✅   |
| Edit the organization                           |   ✅   |   ✅   |    —   |    —   |
| Create a child organization                     |   ✅   |   —   |    —   |    —   |
| Manage subscription and billing                 |   ✅   |   —   |    —   |    —   |
| Manage members and invites                      |   ✅   |   ✅   |    —   |    —   |
| Manage teams                                    |   ✅   |   ✅   |    —   |    —   |
| Manage services                                 |   ✅   |   ✅   |    —   |    —   |
| Manage on-call schedules                        |   ✅   |   ✅   |    —   |    —   |
| Create an on-call override                      |   ✅   |   ✅   |    ✅   |    —   |
| Manage alert sources                            |   ✅   |   ✅   |    —   |    —   |
| Manage integrations (Slack, Teams)              |   ✅   |   ✅   |    —   |    —   |
| View incidents                                  |   ✅   |   ✅   |    ✅   |    ✅   |
| Act on incidents (ack, take, resolve, escalate) |   ✅   |   ✅   |    ✅   |    —   |

## Special rule: assigning an incident to someone else

Assigning an incident to a **third party** carries an extra restriction:

* **Owner and admin** can assign to any active member of the organization.
* **Member** can only assign to someone else if **both** — the assigner and the assignee — are members of the **incident's team**.
* If the incident has no team, a member can only **take it for themselves**. Owners and admins remain unrestricted.

Assigning outside this rule returns an error explaining that the assignee must be a member of the incident's team.

<Tip>
  When torn between **admin** and **member**: give admin to whoever needs to configure schedules and integrations; give member to whoever only needs to answer the page.
</Tip>