Observability Permissions
Observability sits on top of two permission layers: the workspace-level user role that gates the endpoints, and the datastore-level team permission that gates the underlying containers and checks.
For the full reference of user roles and how they compare, see User Roles. For the canonical matrix of every team-permission-gated action across the platform, see Team Permissions Overview.
Admin bypass
Users with the Admin role bypass every team-permission check on every datastore.
Reading the Observability tab
| Team permission | View listing | View charts and heatmap | See favorites |
|---|---|---|---|
| Reporter | |||
| Viewer | |||
| Drafter | |||
| Author | |||
| Editor |
Read access is available to every team permission because the listing endpoint requires a valid workspace user and the team permission gates only the underlying datastore, container, and check reads.
Managing observability checks
| Team permission | Edit thresholds (Min / Max) | Edit Maximum Age | Toggle Volume / Freshness Tracking | Edit check description, tags, metadata |
|---|---|---|---|---|
| Reporter | ||||
| Viewer | ||||
| Drafter | ||||
| Author | ||||
| Editor |
- Threshold edits and Maximum Age edits modify the underlying quality check and require the Author team permission (Editor is always allowed as well).
- Toggling Volume Tracking or Freshness Tracking is available to anyone with any team permission on the datastore. It is intentionally more permissive than check edits so team members can turn on tracking for containers they observe, even when they cannot author or modify checks.
The UI does not hide controls you cannot use
The Edit Threshold and Edit Maximum Age controls are visible to every user who can read the Observability tab. Users at Reporter, Viewer, or Drafter see the pencil buttons but the platform rejects the change on save with a permission error, so match your team permission against the matrix above before attempting a check edit. The Observability Settings modal is a separate case: any team member on the datastore can open it and toggle Volume or Freshness Tracking without hitting a permission error.
Marking favorites
Marking a card or check as a favorite is a per-user preference. Any authenticated user with at least read access to the Observability tab can mark and unmark favorites; the marks are private to the user.