> For the complete documentation index, see [llms.txt](https://docs.statuspal.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.statuspal.io/next/workspace/invite-and-manage-members.md).
# Invite and manage members
Invite your team, choose roles and access scopes, and manage who belongs to your organization.
Admins invite teammates, assign roles, and organize members into groups that scope what they can see, all from **Settings** → **Team Members** and **Settings** → **Groups**.
## Invite members
Go to **Settings** → **Team Members** and click **Invite**.
In the **Invite your team** dialog, enter one email address or several separated by commas in the **Email(s)** field, choose a **Role**, and click **Send invite(s)**.
The role you pick applies to every address in that batch, so invite people who need different roles separately. Each invitee gets an email invitation to join your organization.
Until someone accepts, their row in Team Members shows their email with **(pending)** next to it and no linked sign-in method yet. If your plan's seat limit is reached, the dialog shows an error explaining why and links to billing instead of sending the invites; see [Plans, billing, and seats](/next/workspace/plans-billing-and-seats.md).
## Roles and permissions
Every member has exactly one role: **Admin**, **Member**, or **Status viewer**.
| Capability | Status viewer | Member | Admin |
| --------------------------------------------------- | :-----------: | :----: | :---: |
| View member-restricted status pages | ✓ | ✓ | ✓ |
| View incidents and notices | - | ✓ | ✓ |
| Create and edit incidents and notices | - | ✓ | ✓ |
| Manage monitoring checks | - | ✓ | ✓ |
| Update service statuses manually | - | ✓ | ✓ |
| View the members list | - | ✓ | ✓ |
| Delete notices, resolve or delete incidents | - | - | ✓ |
| Create, edit, and delete runbooks | - | - | ✓ |
| Access settings (page-level and organization-level) | - | - | ✓ |
| Invite or remove members, change roles | - | - | ✓ |
| Manage billing | - | - | ✓ |
| Access audit logs | - | - | ✓ |
**Status viewer** is a read-only role: it exists purely to give someone authenticated access to one or more member-restricted status pages, with no access to the admin console beyond that.
An organization always needs at least one admin. If you try to remove the last admin or change their role to something else, the change is blocked with a message asking you to promote another member first.
Seats are tied to your plan and apply only to Admin and Member roles: the Free plan includes 2 seats, and paid plans size seats to what you've purchased in **Billing**. Status viewers don't use a seat at all: the Free plan allows none, and paid plans allow up to 1,000. See [Plans, billing, and seats](/next/workspace/plans-billing-and-seats.md) for details.
## Team groups and access scopes
Groups don't change what a member can do (that's still their role); they change what status pages and modules a member can *see*. A member with no group keeps full access based on their role. A member in one or more groups is limited to the union of those groups' status pages and modules.
Go to **Settings** → **Groups** and click **Create group** (or open an existing group to edit it). A group has:
* **Name**: required, unique within your organization.
* **Status pages**: either **All status pages**, or **Specific pages** with a checklist of the ones the group's members can access.
* **Modules**: **Incident Management** and **Monitoring** checkboxes controlling which of those modules the group's members can use. Status viewers can't use either module regardless of these checkboxes, since the role itself has no access to them.
* **Members**: added or removed from the group's edit page, either by selecting existing members or by inviting someone new directly into the group.
* **SCIM group name**: optional, and only shown once SCIM is connected. Match it to a group name in your identity provider to drive this group's membership automatically over SCIM instead of managing it here. See [Single sign-on & SCIM](/next/workspace/single-sign-on-and-scim.md).
{% hint style="info" %}
A group scoped to **Specific pages** with status viewers in it needs at least one member-restricted status page in that scope, otherwise those viewers would have nothing to view.
{% endhint %}
Deleting a group removes its memberships only; members keep their organization role and any access other groups grant them.
## Change roles and remove members
From **Team Members**, use the pencil icon on a member's row to open the **Role** menu and pick a new role. You'll be asked to confirm the change.
If a role has been claimed by an identity provider group over SCIM, that role can no longer be assigned manually, and any member already on that role shows a **Managed via SCIM** badge with the pencil icon disabled. Manage that member's role from your identity provider instead; see [Single sign-on & SCIM](/next/workspace/single-sign-on-and-scim.md).
To remove someone, click the trash icon on their row and confirm. This deletes their membership and revokes their access to the organization immediately.
## The Sign-in methods column
The **Sign-in methods** column on the Team Members page lists which methods each member currently uses to sign in, for example **Email & password**, **Google**, **GitHub**, or **SSO**, based on what they've set up and what your organization currently allows. A pending invitation shows no sign-in methods yet, since the person hasn't joined. See [Sign-in methods](/next/workspace/sign-in-methods-and-account-linking.md) for how members link accounts and how you control which methods are allowed.
