Team access
ServersPulse lets you share server access with teammates, moderators, and external helpers. Each person gets a role that controls what they can see and do.
Roles
There are four roles, each with a different set of default permissions:
Owner
Full control over the server. This role is automatically assigned to the user who created the server entry. There can only be one owner per server.
Owners have all permissions and are the only role that can:
- Delete the server
- Rename or edit the server identity
- Access plugin registration codes
- Manage sharing and membership
Operator
Designed for trusted admins who help manage the server day-to-day. Operators can view all data, manage alert rules, and handle incidents.
Alert Manager
Similar to Operator in permissions. Intended for staff who focus specifically on monitoring and responding to alerts. Can manage notification rules and acknowledge incidents.
Viewer
Read-only access. Viewers can see metrics, incidents, reports, and player data but cannot change any configuration or manage alerts.
Permissions matrix
Each role grants a specific set of capabilities. This table shows the defaults:
| Capability | Viewer | Alert Manager | Operator | Owner |
|---|---|---|---|---|
| View overview metrics | Yes | Yes | Yes | Yes |
| View incidents and reports | Yes | Yes | Yes | Yes |
| View players and sessions | Yes | Yes | Yes | Yes |
| Manage notification rules | -- | Yes | Yes | Yes |
| Manage event notifications | -- | Yes | Yes | Yes |
| Acknowledge/resolve incidents | -- | Yes | Yes | Yes |
| Delete server | -- | -- | -- | Yes |
| Rename/edit server identity | -- | -- | -- | Yes |
| Plugin registration access | -- | -- | -- | Yes |
| Manage sharing and membership | -- | -- | -- | Yes |
The last four capabilities (delete, rename, registration, sharing) are owner-only and cannot be granted to other roles, even through per-capability overrides.
Creating invites
To invite someone to your server:
- Open the server's Sharing tab in the dashboard
- Click to create a new invite
- Choose the role to assign (Viewer, Alert Manager, or Operator)
- Optionally set:
- Max uses -- How many times the invite link can be used
- Expiration -- When the invite link expires
- Email restriction -- Limit the invite to a specific email address
- Share the generated invite link with the person
The recipient clicks the link, logs in (or creates an account), and is added to the server with the assigned role.
Managing members
From the Sharing tab, you can:
- View all members -- See who has access, their role, and when they were added
- Change a member's role -- Update someone from Viewer to Operator, or vice versa
- Remove a member -- Revoke their access entirely
- View pending invites -- See all active invite links
- Revoke an invite -- Invalidate an invite link before it expires
Only the server owner can manage membership.
Team size limits
The number of team members (including the owner) is limited by your plan:
| Plan | Max team members |
|---|---|
| Free | 1 (owner only) |
| Starter | 1 (owner only) |
| Pro | 3 |
| Multi | 10 |
Best practices
- Use the least-privilege role -- Give Viewer access by default, and only promote to Operator or Alert Manager when needed
- Set expiration on invites -- Especially for temporary helpers, contractors, or event staff
- Audit regularly -- Review the member list after staffing changes, events, or when projects end
- Use email restrictions -- When you want to ensure only a specific person can use an invite
- One owner -- Keep a single accountable owner per server. Use Operator for trusted admins
Contributors
Thanks to everyone who keeps this docs area accurate.
