> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sreagent.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage people and roles

> Invite teammates, set roles, review what each role can do, and group people into teams.

export const Plan = ({tier}) => <Badge color="blue">{tier} plan</Badge>;

Org admins manage who belongs to the organization and what each person can do from the **Users** page. Enterprise organizations can also run [parent and child organizations](/guides/administer/parent-and-child-organizations).

<Plan tier="Free" />

User seats count against your plan: Free includes 3 users, Pro 25, Business 100, and Enterprise is unlimited.

## Roles

A role is held per organization, so the same person can be an admin in one organization and a viewer in another.

| Role | What it is for |
| - | - |
| **Viewer** | Read-only. Sees everything the organization monitors and changes none of it. |
| **Member** | The person holding the pager. Acknowledges and resolves alerts, starts investigations, runs runbooks and works SLOs. Does not change how the organization is wired up. |
| **Org admin** | Everything a member can do, plus settings, integrations, API keys, billing and users. |
| **Support** | Everything a member can do, plus the public status page. It is not a role you can assign from the app. |

To see exactly what a role allows, open **Users** under **Administration** and click **Roles and permissions**. Click a role card to see what it can and cannot do, or click **Compare all roles** for a side-by-side table. The page reads the live permission rules, so it matches what the app enforces. Slack commands and buttons use their own table, and a few actions have a different minimum role there.

## Invite a teammate

<Steps>
  <Step title="Open Users">
    Click **Users** in the **Administration** section of the sidebar. Only org admins see it.
  </Step>

  <Step title="Add the person">
    Click **Add User**, enter their **Email** and **Name**, and click **Create User**. They get an
    email with a link to set a password. An address that already has an account is added to your
    organization instead.
  </Step>

  <Step title="Set their role">
    New people join as members. Click **Edit** on their row, choose **Viewer**, **Member** or **Org
    admin**, and click **Save**. You cannot change your own role.
  </Step>
</Steps>

If the invitation email cannot be sent, ask the person to use **Forgot password** with that address. At your plan's user limit, the page shows the count and asks you to upgrade.

## Keep the directory tidy

The **Directory** tab lists everyone. Filter by **Role** or **Status** (**Active** or **Disabled**), or search by email or name. The filters are in the address, so you can share a filtered view. Each row has these buttons:

* **Edit** changes name, role and Slack member ID. The Slack ID usually fills in the first time someone uses a Slack command.
* **Reset password** sets a new password and signs the person out everywhere. It is not offered for people who sign in with SSO.
* **Disable** stops the person signing in, and **Enable** reverses it.
* **Delete** removes the account permanently, and their audit entries lose their attribution. Disable instead if they may return.

An organization always keeps at least one admin. Removing the last one is refused until you promote somebody else. People asking to join appear under **Requests to join**. See [Sign in and join your team](/guides/administer/sign-in-and-joining-your-team).

## Group people into teams

The **Teams** page (Business plan), in the **Infrastructure** section, groups people so a workload or finding can point at them. A team attributes work. It never grants access, which comes only from roles.

Type a name under **New team** and click **Create**. Click a team to add or remove members, and use **Rename** or **Delete** on its row. Deleting a team leaves what it owned unowned and deletes none of it. Org admins manage teams, and everyone can read them.

## Related

* [Set up single sign-on](/guides/administer/single-sign-on): map identity provider groups to roles.
* [Choose a plan and manage billing](/guides/administer/plans-and-billing): user limits on each plan.
* [Work incidents from Slack](/guides/respond/slack): roles that Slack commands need.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.