Skip to main content

​
Overview

Every member of an organization has a role that determines what they can see and change. Roles range from full control (owner) to read-only (viewer), so you can safely add teammates, contractors and clients to the same organization.

​
Roles at a Glance

Exact capabilities can evolve as the product does; this table reflects the intended model. Owner is always the highest level of access.

​
Role Descriptions

The person who created the organization. Full control over connections, members, billing and the organization itself. There is always exactly one owner responsibility on an organization.
Trusted operators. Manage connections and members and configure monitoring, but don’t control billing or delete the organization.
Day-to-day team members. Work with connections and analytics; can create connections in the organization (this is the minimum role required to do so via the API).
Collaborators outside your core team — a partner or contractor — with scoped access to the organization’s data.
Read-only. Ideal for clients and stakeholders who should see status, uptime and reports but change nothing.

​
How This Maps to API Keys

Organization roles govern people in the app. API keys have their own permission model (roles like read-only and full-access, and resource: action permissions). A member creating an API key can only grant it access they themselves have. See Authentication.

Managing Members

Invite, re-role and remove people

API Authentication

Key roles and permissions