Tenancy and environment scope
Understand how organization, tenant, application, environment, and app-user scope prevent cross-customer access.
Scope hierarchy
- A dashboard identity belongs to one or more organizations through explicit memberships.
- An organization owns applications. Runtime data is scoped to a verified tenant and application.
- Each application separates environments such as development, staging, and production.
- App users, channels, messages, jobs, events, webhooks, and support actions remain inside that exact scope.
Where scope comes from
Scope comes from verified dashboard membership, application credentials, or app-user token claims. A client-provided tenantId, appId, environment, userId, or resource path is never enough by itself to authorize access.
Client-side rule
A cache key, selected application, route parameter, or visible UI row is not authorization proof. Send the released identifiers, let the server apply verified scope, and reconcile neutral not-found outcomes without exposing why access failed.