Team roles and permissions

Monitoring is often not handled by a single person. The account owner might deal with payments, a developer with application errors, a tester with the quality of a deployment, and accounting with documents.

Roles let you split these responsibilities without giving everyone full access to the account.

Access depends on the role

• Owner has full access to the account, including subscription settings and billing details.
• Admin manages projects and the team, but isn't responsible for payment settings.
• Accountant has access to the areas related to the subscription and billing.
• Developer works with projects, errors, and reports.
• Tester can view data about errors and reports and work with issue statuses.

The exact scope of access depends on the assigned role. There's no need to create a separate account for every person working with monitoring.

Why are separate accounts better than a shared login?

A shared login quickly leads to problems with security and access management. When someone leaves the team, you have to change the password for everyone else.

With separate accounts, you can simply remove or change one person's access, leaving the rest of the team unaffected.

Monitoring for multiple clients

If you work as a software house or an agency, separate projects let you keep order across deployments. Each application can have its own errors, alerts, keys, and configuration.

This matters especially when a single person looks after several production applications.