> For the complete documentation index, see [llms.txt](https://support.incidentlake.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidentlake.com/getting-started/roles.md).

# Roles and permissions

What Administrators, Members, and Viewers can do.

Every person in an organization has one role. The role decides what they can change.

| Role              | Typical use                            | What they can do                                                                                                                 |
| ----------------- | -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Administrator** | Workspace owners and security contacts | Invite and remove people, change organization settings, connect integrations, manage workflow, and do everything a Member can do |
| **Member**        | Responders and commanders              | Create and update incidents, chat, edit knowledge, and work tasks                                                                |
| **Viewer**        | Stakeholders who need visibility       | Read incidents and reports they are allowed to see; they cannot change workspace settings                                        |

{% hint style="info" %}
Some incidents are limited with access tags (shown as **RBAC tags** in organization settings). If you cannot open an incident that you expect to see, you may be missing the required tag. Ask an Administrator.
{% endhint %}

## Who should be an Administrator

Keep the Administrator role small. Admins can invite people, connect Slack or other tools, and change how the organization is set up. Day-to-day response work only needs the Member role.

## Changing a role

An Administrator opens **Settings → Tenant** (organization settings), finds the person on the members list, and changes their role. The change applies the next time that person uses Incident Lake.


---

# 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://support.incidentlake.com/getting-started/roles.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.