Scope Model

Goal

Understand the hierarchy Oriel uses for navigation, authorization, storage, and querying:

workspace -> project -> environment -> service

Workflow

Use the scope bar at the top of the app to choose the active workspace, project, environment, time range, and optional service. The active scope follows you across Explore, Traces, Logs, Metrics, Dashboards, Service Map, Services, Alerts, and Settings.

Scope	Meaning
Workspace	Hard tenancy and authorization boundary.
Project	A product or system inside the workspace.
Environment	A deployment plane such as prod, staging, dev, or pr-481.
Service	The OpenTelemetry service.name resource attribute.

Changing scope changes the data behind every screen. It does not change the meaning of saved queries or dashboards; those still run inside the selected workspace and project context.

Permissions

The minimum permission for reading telemetry is telemetry:query. Additional screens require their own permissions, for example dashboards:read, alerts:read, or projects:read.

Project-scoped grants can limit a user to specific projects. Workspace-scoped grants apply across the workspace.

Related Pivots

• From a service, pivot to traces, logs, or the service map.
• From a trace, pivot to logs with the same trace_id.
• From a metric exemplar, pivot to the trace when exemplar data is present.
• From an alert, pivot back to the query and scope that produced it.