Team and roles
Each service has its own team. A person has one role per service.
Roles
| Capability | SUPPORT | OPERATIONS | ADMIN |
|---|---|---|---|
| View everything on the service | Yes | Yes | Yes |
| Post, edit and delete status updates | Yes | Yes | Yes |
| Open and close incidents | Yes | Yes | Yes |
| Delete incidents | No | Yes | Yes |
| Manage components, endpoints and monitors | No | Yes | Yes |
| Invite members, change roles, remove members | No | No | Yes |
| Manage Application Programming Interface (API) keys | No | No | Yes |
| Change settings: visibility, indexing, custom domain, name | No | No | Yes |
| Delete the service | No | No | Yes |
A service always keeps at least one ADMIN. The last ADMIN cannot be demoted or removed.
Invitations
- An ADMIN enters an email address and a role. The role defaults to SUPPORT.
- The person must already have an account. If the address has none, nothing is sent and the page shows the same message either way.
- The invitee sees the invitation on My Services and chooses Accept or Reject.
Limits
| Plan | Members per service |
|---|---|
| FREE | 5 |
| PRO | 25 |
Accepting an invitation also counts against the invitee's own service limit, 2 by default.