> For the complete documentation index, see [llms.txt](https://docs.itoc360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itoc360.com/users-and-access-management/roles-and-permissions.md).

# Roles & Permissions

Every user in your ITOC360 organization has a role, and that role decides what they can see and do from acknowledging an incident to changing the subscription. ITOC360 ships with three built-in roles that cover most teams, and if none of them is quite right, you can build your own role by picking exactly the permissions it should include.

You'll find roles under **Management → Users**, on the **Roles** tab.

Creating and managing custom roles is available on the **Advanced** and **Premium** plans. The three built-in roles are available on every plan.

### Built-in roles

**Admin** has every permission. Admins are the only ones who can delete things (sources, teams, schedules, escalation policies, channels, domains, maintenance windows, roles), invite new users, change the plan or payment method, and assign a role to a user. Keep this role for the small group of people who genuinely need to run the organization.

**Manager** is the day-to-day operator. Managers can create and edit almost everything, acknowledge incidents, and silence alerts — but they cannot delete anything, cannot invite new users, cannot touch billing beyond viewing it, and cannot assign roles to other users. This is the right fit for team leads and senior on-call engineers.

**Viewer** is read-only. Viewers can see alerts, incidents, sources, schedules, teams, escalation policies, channels, domains, maintenance windows, roles, and the billing overview — but they can't change any of it, and they can't acknowledge incidents or silence alerts. Useful for stakeholders who want visibility without the risk of a stray click.

Built-in roles can't be edited or deleted. If you need something between Manager and Viewer, create a custom role instead, or duplicate a built-in role and adjust it.

### Permissions reference

The tables below show what each built-in role can do. When you create a custom role, these same permissions are the ones you toggle on and off.

#### Alerts

| Permission     | Admin | Manager | Viewer |
| -------------- | ----- | ------- | ------ |
| View alerts    | ✅     | ✅       | ✅      |
| Silence alerts | ✅     | ✅       | —      |

#### Incidents

| Permission            | Admin | Manager | Viewer |
| --------------------- | ----- | ------- | ------ |
| View incidents        | ✅     | ✅       | ✅      |
| Acknowledge incidents | ✅     | ✅       | —      |

#### Sources

| Permission                              | Admin | Manager | Viewer |
| --------------------------------------- | ----- | ------- | ------ |
| View monitoring sources                 | ✅     | ✅       | ✅      |
| Create new sources                      | ✅     | ✅       | —      |
| Edit source settings and configurations | ✅     | ✅       | —      |
| Remove sources                          | ✅     | —       | —      |

#### Escalations

| Permission                                         | Admin | Manager | Viewer |
| -------------------------------------------------- | ----- | ------- | ------ |
| View escalation policies                           | ✅     | ✅       | ✅      |
| Create new escalation policies                     | ✅     | ✅       | —      |
| Edit escalation policy settings and configurations | ✅     | ✅       | —      |
| Remove escalation policies                         | ✅     | —       | —      |

#### Schedules

| Permission                                | Admin | Manager | Viewer |
| ----------------------------------------- | ----- | ------- | ------ |
| View schedules                            | ✅     | ✅       | ✅      |
| Create new schedules                      | ✅     | ✅       | —      |
| Edit schedule settings and configurations | ✅     | ✅       | —      |
| Remove schedules                          | ✅     | —       | —      |

#### Teams

| Permission                            | Admin | Manager | Viewer |
| ------------------------------------- | ----- | ------- | ------ |
| View teams                            | ✅     | ✅       | ✅      |
| Create new teams                      | ✅     | ✅       | —      |
| Edit team settings and configurations | ✅     | ✅       | —      |
| Remove teams                          | ✅     | —       | —      |

#### Channels

| Permission                               | Admin | Manager | Viewer |
| ---------------------------------------- | ----- | ------- | ------ |
| View notification channels               | ✅     | ✅       | ✅      |
| Create new notification channels         | ✅     | ✅       | —      |
| Edit channel settings and configurations | ✅     | ✅       | —      |
| Remove notification channels             | ✅     | —       | —      |

#### Maintenances

| Permission                                          | Admin | Manager | Viewer |
| --------------------------------------------------- | ----- | ------- | ------ |
| View maintenance windows                            | ✅     | ✅       | ✅      |
| Create new maintenance windows                      | ✅     | ✅       | —      |
| Edit maintenance window settings and configurations | ✅     | ✅       | —      |
| Remove maintenance windows                          | ✅     | —       | —      |

#### Domains

| Permission                              | Admin | Manager | Viewer |
| --------------------------------------- | ----- | ------- | ------ |
| View domains                            | ✅     | ✅       | ✅      |
| Create new domains                      | ✅     | ✅       | —      |
| Edit domain settings and configurations | ✅     | ✅       | —      |
| Remove domains                          | ✅     | —       | —      |

#### Roles

| Permission                                                                       | Admin | Manager | Viewer |
| -------------------------------------------------------------------------------- | ----- | ------- | ------ |
| View roles, their assigned permissions, and the assignable permissions catalogue | ✅     | ✅       | ✅      |
| Create new roles within the tenant                                               | ✅     | ✅       | —      |
| Edit roles and their permission assignments                                      | ✅     | ✅       | —      |
| Remove roles from the tenant                                                     | ✅     | —       | —      |

#### Users and invitations

| Permission                            | Admin | Manager | Viewer |
| ------------------------------------- | ----- | ------- | ------ |
| Invite users to tenants               | ✅     | —       | —      |
| Assign a role to a user in own tenant | ✅     | —       | —      |

#### Billing

| Permission                                                             | Admin | Manager | Viewer |
| ---------------------------------------------------------------------- | ----- | ------- | ------ |
| View the subscription, plan usage, and invoices                        | ✅     | ✅       | ✅      |
| Change the plan, seats, or payment method, and cancel the subscription | ✅     | —       | —      |

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2Fgit-blob-78a139080ffdb907f2d7ae3e07b531e055794868%2F43_Ekran%20Resmi%202026-09-01%2015.05.39.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2Fgit-blob-1f919607f8fb8158d5f4bacea01dbdf26bd385ae%2F44_Ekran%20Resmi%202026-09-01%2015.06.13.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2Fgit-blob-a1db519f7d2e14b90dc0fff2ac14e48e7c423336%2F45_Ekran%20Resmi%202026-09-01%2015.06.44.png?alt=media" alt=""><figcaption></figcaption></figure>

Notice the split in the **Roles** table: a Manager can create and edit roles, but cannot assign a role to a user or delete a role. Those two actions stay with **Admins**.

### Creating a custom role

1. Go to **Management → Users** and open the **Roles** tab.
2. Click **Create role**.
3. Give the role a **Name** that describes the job, not the person — `Network On-Call`, `Read-only Auditor`, `Billing Owner`. You can add a **Description** too.
4. Click **Create role**. The role's page opens. A new role starts with no permissions.
5. Tick the permissions the role should have. The grid lists each area as a row, grouped into Platform, Management and Settings, with **View**, **Create**, **Edit** and **Delete** columns. Actions such as silencing alerts or acknowledging incidents are under **Other**.
6. Click **Save changes**.

To start from an existing role instead, open it and click **Duplicate**. The copy starts with the same permissions, and you can change them on the next page.

The new role appears on the **Roles** tab and can be picked everywhere a role is chosen, including invitations.

A few things worth keeping in mind while you pick permissions:

* **Grant the view permission for anything you grant edit on.** A role that can edit schedules but can't view them will hit dead ends in the UI.
* **Delete is always the sharpest edge.** Removing a source, schedule, or escalation policy is not recoverable, so hand out the remove permissions deliberately.
* **Think about who can hand out power.** A role with *Create new roles*, *Edit roles*, and *Assign a role to a user* can effectively promote anyone, including itself.

### Assigning a role to a user

1. Go to **Management → Users**.
2. Click the **⋯** menu on the user's row and choose **Change role**.
3. Pick the new role and click **Change role**.

Only a role with **Assign a role to a user in own tenant** can do this — by default, Admin. You can't change your own role or the organization owner's role.

Permissions are carried in the user's session. The new role takes effect when their session refreshes, which happens automatically within an hour. If they need it right away, they can sign out and sign back in.

### Choosing a role when you invite someone

Every invitation includes a role, so new users land with the right permissions from their very first sign-in instead of being fixed up afterwards. Built-in and custom roles both appear in the role list.

You can invite people in two places:

* **Invite** in the top bar — enter the email address, pick a role, and click **Send invitation**.
* **Settings → Team** — click **Invite members** in the **Invitations** section. Enter each person's email address and role, use **Add another** to invite more people at once, and send the invitations.

Inviting requires the **Invite users to tenants** permission, which only Admin has by default.

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2Fgit-blob-7bddc851905aa5d9897d72543de78a213b906364%2F46_Ekran%20Resmi%202026-09-01%2015.21.28.png?alt=media" alt=""><figcaption></figcaption></figure>

### Editing and deleting a role

Open a custom role from the **Roles** tab. Use the **⋯** menu and choose **Edit** to change its name or description. To change its permissions, update the grid and click **Save changes**. Changes apply to everyone holding the role; like a role change, they reach each user when their session refreshes, within an hour.

To delete a role, choose **Delete** from the **⋯** menu. This needs the **Remove roles from the tenant** permission. A role that is still assigned to members can't be deleted, so move those members to another role first. Built-in roles can't be edited or deleted.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.itoc360.com/users-and-access-management/roles-and-permissions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
