Roles & permissions
Control who can do what across your Hyperping account and projects. Five roles give you fine-grained control, with every resource scoped inside a project, and team members only seeing the projects they belong to.
- You're onboarding new team members and need to explain what they can and can't do.
- You need to decide how to structure projects for different teams or clients.
- You're preparing for a security or compliance review.
At a glance
The four roles
One Owner per account. All other team members are assigned one of three roles: Admin, Member, or Billing.
- View and manage every project, including those created by teammates
- Invite and remove teammates from any project
- Transfer ownership to another teammate
- Manage billing, subscription, and payment details
- Configure SSO policies and authentication settings
- Access audit logs and delete on-call schedules
- Invite and remove teammates
- Create, edit, and delete monitors
- Manage status pages and publish incidents
- Create, update, and delete on-call schedules
- Configure escalation policies and integrations
- View all reporting data and outage history
- Create, edit, and delete monitors
- Create and update on-call schedules
- Acknowledge, resolve, and escalate outages
- Update outage severity, descriptions, and summaries
- Bulk-edit monitors
- View all reporting data and outage history
- Access billing, subscription, and payment settings
- View monitors, reports, outage history, and schedules
Permission matrix
Quick reference for every capability. ✓ means allowed, — means blocked.
| Action | Owner | Admin | Member | Billing |
|---|---|---|---|---|
| View monitors, reports, and outages | ✓ | ✓ | ✓ | ✓ |
| View on-call schedules | ✓ | ✓ | ✓ | ✓ |
| View teammates list | ✓ | ✓ | ✓ | ✓ |
| Create, edit, and delete monitors | ✓ | ✓ | ✓ | — |
| Bulk-edit monitors | ✓ | ✓ | ✓ | — |
| Create and update on-call schedules | ✓ | ✓ | ✓ | — |
| Delete on-call schedules | ✓ | ✓ | — | — |
| Create outages | ✓ | ✓ | ✓ | — |
| Acknowledge and resolve outages | ✓ | ✓ | ✓ | — |
| Escalate outages | ✓ | ✓ | ✓ | — |
| Update outage severity and details | ✓ | ✓ | ✓ | — |
| Write postmortems and AI summaries | ✓ | ✓ | ✓ | — |
| Delete outages | ✓ | ✓ | ✓ | — |
| Invite and remove teammates | ✓ | ✓ | — | — |
| Transfer account ownership | ✓ | — | — | — |
| Manage billing and subscription | ✓ | — | — | ✓ |
| Configure SSO and authentication | ✓ | — | — | — |
Project isolation
Projects act as boundaries. A teammate invited to Project A cannot see monitors, status pages, or integrations in Project B. Only the Owner sees every project.
Common ways to split work across projects:
- Clients. Each client gets their own project.
- Internal teams. Engineering, infrastructure, support.
- Environments. Production vs staging.
If you use SAML SSO, you can also restrict SSO users to specific projects through the SSO access scope setting. See login methods for the full flow.
Pick a role
Common mappings from job title to recommended role:
Account security
Add a second verification step to login. Once enabled, you need your password plus a code from your authenticator app.
Enable it in your account settings. Available to all users on every plan.
Every change is recorded: who did what, when, and in which project.
Useful for tracking config changes, reviewing teammate activity after an incident, and providing evidence for compliance audits.
Encrypted at rest with LUKS, in transit with SSL/HTTPS.
All data stored in the EU (DigitalOcean Frankfurt). GDPR-compliant with self-serve data deletion.
