Role-based access, scoped API keys, service accounts and an audit log

Four roles (owner, admin, developer, viewer), API keys with explicit scopes, expiry and IP restrictions, service accounts for automation that outlive any one person, and an audit log of who changed what — so a monitoring platform with production credentials in it is governed like one.

Roles decide what a person can do in the dashboard; scopes decide what a key can do through the API, and a key can never carry more access than its owner's role. Service accounts own keys for CI pipelines and agents so a departing engineer doesn't take the automation with them. Keys can expire, be restricted to IP ranges and environments, and carry their own read/write/delete rate limits.

Everything that changes — a role, a destination, a key, a monitor — is written to the organization audit log with the actor and the time; Enterprise adds export and retention guarantees. Sessions are visible and revocable per user, MFA is available to everyone, and SSO (Google/OAuth on Pro, SAML on Enterprise) keeps sign-in where your identity provider is.

• Roles — owner, admin, developer, viewer.
• Scoped keys with expiry, IP and environment restrictions and rate limits.
• Service accounts for automation that isn't a person.
• Audit log, sessions, MFA, SSO for the security review.