Invite and manage your team
Use one account per person
Invite each teammate with their own email address. Shared logins make it difficult to understand who changed a monitor, acknowledged an incident, or updated workspace settings.
Give people only the access they need
Owners and administrators manage the workspace; members operate it; viewers can inspect it.
Choose the least powerful useful role
| Role | Best for | Main access level |
|---|---|---|
| Owner | The person accountable for the workspace and subscription | Full workspace authority |
| Administrator | Trusted people who manage members and configuration | Broad management access |
| Member | Operators who create monitors and respond to incidents | Day-to-day operational access |
| Viewer | Stakeholders who need visibility but should not make changes | Read-only access |
Do not make everybody an administrator for convenience. Start with Member or Viewer and expand access when the responsibility requires it.
Invite a teammate
Open Team
Choose Team and select Invite member.
Enter the work email
Check the spelling and confirm the address belongs to the intended person.
Select a role
Choose the lowest role that supports the teammate’s work.
Send the invitation
The invitation remains pending until accepted and is valid for a limited time.
Configure notifications
After the member joins, review which incident and SSL events they should receive.
Manage pending invitations
The Invitations tab separates pending access from active members. You can resend an invitation when the original message was missed or cancel it when the person should no longer join.
Before resending repeatedly, ask the recipient to check spam filtering and confirm the email address. Cancel invitations sent to the wrong address immediately.
Change a role
Role changes take effect for the member’s workspace access. Tell the person when their responsibility changes, especially when reducing access during a job or team transition.
Avoid leaving temporary administrator access in place after the task that required it is complete.
Remove a member
Removing a member ends their workspace access. It should not delete monitors, incidents, check history, or other shared operational records they created.
Before removal:
- transfer service ownership and response responsibilities;
- review integrations or credentials they managed;
- confirm another owner or administrator remains;
- preserve any necessary operational notes.
Review delivery by event
The Delivery tab groups notification attempts so administrators can see whether important events reached their destinations. Filter by status instead of scanning a long unstructured list.
See Decide who receives notifications for delivery states and recommended routing.
Quarterly access review
At least once each quarter, review active members, pending invitations, administrator access, and notification responsibilities. Also review access after contractors finish, teams reorganize, or an employee leaves.