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

# Roles and access

Every team member is assigned a role. Each role comes with a predefined set of permissions that admins can edit. Manage roles and access under [Organisation > Team](https://app.spike.sh/settings/general/team).

## Roles

By default, four roles are available:

| Role      | Description                                                                                            |
| --------- | ------------------------------------------------------------------------------------------------------ |
| Admin     | Full access to manage the account, including the ability to remove members                             |
| Manager   | Can manage all entities on the account and change members' permissions and roles                       |
| Responder | Can work with incidents, integrations, automation, and on-calls, but cannot archive or delete entities |
| Viewer    | Read-only access across Spike. Cannot create, update, or delete anything                               |

<figure><img src="/files/OVkEG07tyhvBEFFhCAFB" alt="Roles and access on Spike"><figcaption></figcaption></figure>

Click a role to see the members assigned to it.

## Access control

Access control defines what each team member can do in Spike.

Click **View & edit permissions** on any member to see and change their permissions.

<figure><img src="/files/LIW5d0GtyTgkLROPm44A" alt="View and edit permissions for team members on Spike"><figcaption></figcaption></figure>

## FAQs

### What if no existing role fits a user?

Create a custom role. On the Team page, click **Create role**, configure the permissions you need, and assign the new role to the user.

<figure><img src="/files/Rdakk3rbx50HKe3WODwl" alt="Create a custom role on Spike"><figcaption></figcaption></figure>

{% hint style="info" %}
Status pages have their own access settings. The same roles apply, except the Responder role is not available there.
{% endhint %}

### How do I remove a user?

Click the remove icon next to the user in the table. Make sure to also replace them in any escalation policies and on-call schedules.


---

# 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:

```
GET https://docs.spike.sh/administration/roles-and-access.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.