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

# User roles and permissions

## Available roles

A user in ilert can have one of the following roles:

* [Stakeholder](#stakeholder)
* [Guest](#guest)
* [Responder](#responder)
* [User](#user)
* [Admin](#admin)
* [Account Owner](#account-owner)

### Stakeholder

Stakeholders will only be able to see the incidents to which they have been added as a subscriber and won't be able to see any other data, such as alerts, alert sources, escalation policies, etc. Additionally, they can see the status pages and services to which they have been granted access. In order to grant a stakeholder user access to resources, the stakeholder needs to be added to a team that contains said resources. This role is only available as part of our [Scale plan](https://www.ilert.com/pricing).

### Guest

Guest users have access to the application. However, they cannot see any resources or users unless they are added as members of a team, which gives them (depending on their team role) permission to see or even edit the resources of the specific team.

### Responder

Responders can use the web UI and mobile app to manage alerts, just like Users. However, they have no permission to create or modify any objects, such as alert sources, schedules, or escalation policies. Besides taking actions on alerts, Responders can add themselves as overrides to schedules.

### User

Users can create or modify entities like alert sources or on-call schedules; however, they cannot create or modify (or invite) other users (of any role) or change account settings. Users are also not able to create or modify Teams. Although users may edit public resources globally, they may not change the ownership of a resource (team context).

### Team Admin

**Users** may not create or modify teams. But an Admin may grant a User, as a member of a team, the right to modify a certain team. A Team Admin is, therefore actually not a role in itself; it is an additional permission that may be granted to a **User** on a team basis\*\*.\*\*

### Admin

An Admin is a **User** with elevated priviliges. He may not access or modify the account settings. However, he can create and modify **Users** as well as **Teams**, he may also change the role of **Users,** and can create and edit connectors\*\*.\*\* An **Admin** has the right to add and remove team ownerships to/from resources.

### Account Owner

An account owner has the same privileges as an **Admin**, with the addition of being able to access and modify the account settings as well as subscription and billing settings. Only the account owner himself is able to transfer the Account Owner role to another **User**. There can only be a single account owner per account.

## Role permissions

The table below gives an overview of the role permissions.

| **Operation**                                          | **Stakeholder** | **Guest** | **Responder** | **User** | **Admin** | **Account Owner** |
| ------------------------------------------------------ | :-------------: | :-------: | :-----------: | :------: | :-------: | :---------------: |
| Modify profile settings                                |        ✅        |     ✅     |       ✅       |     ✅    |     ✅     |         ✅         |
| Subscribe to incidents, services and status pages      |        ✅        |     ❌     |       ✅       |     ✅    |     ✅     |         ✅         |
| Manage alerts                                          |        ❌        |     ❌     |       ✅       |     ✅    |     ✅     |         ✅         |
| View objects, e.g. schedules and escalation policies\* |        ❌        |     ❌     |       ✅       |     ✅    |     ✅     |         ✅         |
| View reports\*\*                                       |        ❌        |     ✅     |       ✅       |     ✅    |     ✅     |         ✅         |
| Add him/herself as override to a schedule              |        ❌        |     ❌     |       ✅       |     ✅    |     ✅     |         ✅         |
| Add (anyone) as overrides to schedules                 |        ❌        |     ❌     |       ❌       |     ✅    |     ✅     |         ✅         |
| Modify objects, e.g. schedules and escalation policies |        ❌        |     ❌     |       ❌       |     ✅    |     ✅     |         ✅         |
| Manage teams                                           |        ❌        |     ❌     |       ❌       |     ❌    |     ✅     |         ✅         |
| Manage users                                           |        ❌        |     ❌     |       ❌       |     ❌    |     ✅     |         ✅         |
| Add or remove team ownerships to/from resources        |        ❌        |     ❌     |       ❌       |     ❌    |     ✅     |         ✅         |
| <p>Manage account</p><p>settings and subscription</p>  |        ❌        |     ❌     |       ❌       |     ❌    |     ❌     |         ✅         |

\*Stakeholders have view access to shared (team membership) or subscribed incidents, services and status pages\
\*\**The actual data that is shown in reports will depend on the permissions of the current user.*\
\&#xNAN;*If the user has no access to a schedule, for example, he will not see the on-call-duty data of this schedule when browsing reports. (*[*Read more here*](/~/changes/vPSzQFfkdJCVWGT5AL1m/user-administration/teams.md#report-visibility)*)*

## Change a user's role

{% hint style="warning" %}
This requires admin or account owner privileges
{% endhint %}

To change a user's role

1. Click on the cog-icon in the navigation bar and select **Users & teams**
2. Click the **Edit** link for the user you would like to change.
3. In the **Basic information** section, select the user's role from the dropdown menu:

![](/files/-MKAvxfh2szxeuCsCzuK)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ilert.com/~/changes/vPSzQFfkdJCVWGT5AL1m/user-administration/user-roles-and-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.