User roles
What User, Admin and Superadmin can each do.
Overview
Checkmate has three roles: User, Admin and Superadmin. Pick the lowest role that lets a person do their job. Permissions are enforced on the server, so a role limit holds whether someone uses the web interface or calls the API directly.

The first user to register becomes the Superadmin.
Role comparison
| Permission | User | Admin | Superadmin |
|---|---|---|---|
| View monitors, checks and incidents | ✓ | ✓ | ✓ |
| View certificate and domain expiry | ✓ | ✓ | ✓ |
| View notifications, maintenance and status pages | ✓ | ✓ | ✓ |
| View global settings | ✓ | ✓ | ✓ |
| Edit own account | ✓ | ✓ | ✓ |
| Create, edit and delete monitors | — | ✓ | ✓ |
| Pause monitors | — | ✓ | ✓ |
| Import and export monitors | — | ✓ | ✓ |
| Manage notification channels | — | ✓ | ✓ |
| Resolve incidents | — | ✓ | ✓ |
| Manage maintenance windows | — | ✓ | ✓ |
| Manage status pages | — | ✓ | ✓ |
| Delete check history | — | ✓ | ✓ |
| View team members | — | ✓ | ✓ |
| Invite and remove team members | — | ✓ | ✓ |
| View logs, diagnostics and the queue | — | ✓ | ✓ |
| Configure SMTP and global settings | — | ✓ | ✓ |
| Generate and rotate the heartbeat ping key | — | ✓ | ✓ |
| Create user accounts directly | — | — | ✓ |
| Change a member's role | — | — | ✓ |
| Change another user's password | — | — | ✓ |
| Delete all monitors at once | — | — | ✓ |
User
Users can see monitoring data but cannot change how monitoring works. They see every monitor, the dashboard, uptime history and response times, checks, incidents, certificate and domain expiry and the configuration of notifications, maintenance windows and status pages. They can edit or delete their own account.
A User cannot create, edit, pause or delete a monitor, manage notification channels, resolve incidents, change settings or see other team members.
In the web interface, controls a User cannot use are hidden rather than shown and then rejected, so Checkmate reads as a view-only app.
The User role is the closest thing to a read-only account, with two limits worth knowing before you rely on it. There is no separate read-only API credential, so a User who signs in holds a normal session token. Read access is also all or nothing: a User sees every monitor on the team and cannot be restricted to a subset.
Admin
Admins have every User permission plus day-to-day management: creating, editing, pausing and deleting monitors, importing and exporting them as JSON, managing notification channels and sending test notifications, resolving incidents, managing maintenance windows and status pages, deleting check history, inviting and removing team members, changing global application settings including SMTP, viewing application logs, system diagnostics and the queue and generating or rotating the team heartbeat ping key.
Superadmin
Superadmins have everything an Admin has, plus user account management. Only a Superadmin can create a user account directly without an invite, edit another user's account including their role, change another user's password or delete all monitors at once.
Choosing a role
Use User for anyone who needs to watch monitoring data without changing it, such as a developer on call who reads incidents or a stakeholder who checks uptime.
Use Admin for the people who run monitoring day to day: adding monitors, wiring up alerts and scheduling maintenance.
Keep Superadmin for the one or two people who manage the team itself. An Admin can invite and remove members but cannot change anyone's role, so you need a Superadmin on hand to promote someone.
There is no per-monitor permission. Any role that can see monitors sees all of them, and any role that can edit monitors can edit all of them.