Roles and permissions

Control who can do what across your Hyperping account and projects.

Hyperping uses two roles, Owner and Teammate, combined with project-level isolation to keep access tightly scoped. Every resource in Hyperping lives inside a project, and teammates only see the projects they belong to. The Owner has full visibility across all projects and is the only role that can manage billing, invite or remove teammates, and transfer ownership.

This page is useful when:

• 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

Roles

There is one Owner per account and any number of Teammates.

Owner

The Owner has unrestricted access to the entire account. This includes:

• Viewing and managing all projects, including those created by teammates
• Inviting and removing teammates from any project
• Transferring ownership to another teammate
• Managing billing, subscription, and payment details
• Configuring SSO policies and authentication settings
• Accessing audit logs

The Owner is the only role that can perform administrative actions like changing the plan, setting up SAML SSO, or removing teammates. If the Owner transfers ownership, they become a regular Teammate.

Teammate

A Teammate has full access to the resources inside their assigned project, but nothing outside it. Within a project, a Teammate can:

• Create, edit, and delete monitors
• Manage status pages and publish incidents
• Configure escalation policies and on-call schedules
• Set up notification channels and integrations
• View response time data, outage history, and logs

A Teammate cannot access billing, see other projects, or remove other teammates.

Permission comparison

Project isolation

Projects act as boundaries. A Teammate invited to Project A cannot see monitors, status pages, or integrations in Project B. This makes projects a good way to separate:

• Different clients (each client gets their own project)
• Internal teams (engineering, infrastructure, support)
• Environments (production vs. staging)

The Owner is the exception. Owners see all projects and can move between them freely.

If you use SAML SSO, you can also restrict SSO users to specific projects through the SSO access scope setting in login methods. This is useful when contractors or external partners authenticate via your identity provider but should only access certain projects.

Account security

Two-factor authentication (2FA)

Add a second verification step to your login. Once enabled, you'll need both your password and a code from your authenticator app to sign in.

To enable 2FA, go to your account settings and follow the setup steps.

2FA is available to all users regardless of role or plan.

Audit logs

Audit logs record every change made within your Hyperping account: who did what, when, and in which project. Use them to:

• Track configuration changes to monitors and status pages
• Review teammate activity after an incident
• Provide evidence for compliance audits

Data protection

Hyperping encrypts data at rest with LUKS and in transit with SSL/HTTPS. All data is stored in the EU (DigitalOcean Frankfurt). Hyperping is GDPR-compliant and supports data deletion requests directly from the dashboard.

Troubleshooting

A teammate says they can't see a project.
Teammates only see projects they were invited to. Check the Teammates page while inside the correct project to verify they were invited there.

A teammate needs to manage billing.
Only the Owner can access billing. If someone else needs to handle it, the current Owner can transfer ownership.

An SSO user can't log in.
Check the provisioning policy in your SSO settings. If it's set to "Invite-only," the user needs to be invited before SSO login will work. See login methods for details.