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

# Team Permissions

Choose who can change each part of a team - overrides, rotation, reminders, settings, integrations - for every team at once or one team at a time.

By default anyone in your workspace can cover a shift, and only a team's managers can change its rotation. **Team Permissions** lets you decide that per action, instead of all-or-nothing.

## Where

* **For every team at once:** Dashboard → **Organisation → Admins → Team permissions**
* **For one team:** Dashboard → **My Teams** → open the team → **Permissions** (at the bottom)

A team's own choice overrides the org-wide one. Only organisation admins can change either.

## The five things you can control

|                       | Covers                                                                |
| --------------------- | --------------------------------------------------------------------- |
| **Overrides & cover** | Take over a shift, swap with someone, remove an override              |
| **Rotation**          | Who is in the rotation, the order, when it hands over                 |
| **Reminders**         | The shift reminder sent before a handover                             |
| **Team settings**     | Name, Slack channel, manager, timezone                                |
| **Integrations**      | Which PagerDuty schedule, Jira board and alert sources feed this team |

For each, pick who may do it:

* **Anyone** in the workspace
* **Team managers + admins** — the team's access list ([Setup Team Access](/getting-started/setup-team-access.md)), plus org admins
* **Org admins only**

Leave a row on **Default** and nothing changes.

## What "Default" means

|                                       | Team **without** a managers list | Team **with** a managers list |
| ------------------------------------- | -------------------------------- | ----------------------------- |
| Overrides & cover, Reminders          | Anyone                           | **Anyone**                    |
| Rotation, Team settings, Integrations | Anyone                           | Managers + admins             |

Overrides and reminders stay open on every team unless you close them — covering a sick colleague at 2am should not need a permission you do not have.

## Where it applies

The same rule runs everywhere: the **Override** button in Slack, the dashboard, `@Pagerly` assist, and the [MCP server](/getting-started/connect-an-ai-agent-mcp.md). Someone who is refused is told which team and who to ask.

{% hint style="info" %}
Creating and deleting teams, the on-call directory, escalation policies, integrations and billing are always organisation-admin only. They are not configurable, on purpose.
{% endhint %}