Skip to main content
A role is a named set of permissions. A member receives a role for the whole workspace under Users. An access grant gives a user or a team a role for the whole organization or for selected resources, optionally until a date. Open Identity & Access → Roles or Access grants.

Roles

Roles lists the built-in and the custom roles of the workspace, with the number of permissions of each and where it is used: members, tokens, invitations, and bindings. Built-in roles are read only. See Built-in roles. To create a custom role:
  1. Select New role.
  2. Enter a Key of lowercase letters, digits, and underscores. It cannot change later.
  3. Enter a Name and a Description.
  4. Optionally choose a Permission template as a starting point, then add or remove permissions. Each permission shows what it allows.
  5. Select Create role.
Select a custom role to change it. Delete removes a custom role only while nothing uses it: no membership, token, invitation, or binding. Reading roles requires iam.roles.read, and changing them requires iam.roles.manage.

Access grants

An access grant is a role binding: a role for a principal, in an organization, over a scope of resources. Use one when access should follow a person, a team, or a resource, instead of widening a broad role.
  1. Open Access grants and select New access grant.
  2. Principal: choose a User or a Team, and select it.
  3. Organization: the current workspace, shown for reference.
  4. Resource scope: Entire organization, or a resource type (Dashboard or Stream) with one resource or All resources of this type.
  5. Role and permissions: the role that the grant gives.
  6. Constraints: optionally an Environment that requests must match exactly, such as prod, and an Expires at time.
  7. Select Create grant.
Delete ends a grant at once. Reading grants requires iam.policies.read, and creating or deleting them requires iam.policies.manage.

Share resources across organizations

A cross-organization share gives another organization access to selected resources of this one. It is explicit and not transitive: it applies only to the chosen organization and resources, and is never inherited or passed on.
  1. In Access grants, select Share across organizations.
  2. Choose the Target organization.
  3. Choose the resource type and the resource: a Dashboard, or a Stream.
  4. Choose the permissions: dashboards.read and dashboards.edit for a dashboard, streams.read and streams.query for a stream.
  5. Optionally set Expires at, then select Create share.
The share starts as Pending acceptance. An administrator of the target organization selects Accept in its own Access grants, and the share becomes Active. Either side can Revoke it. Creating, accepting, and revoking shares requires iam.policies.manage.

Permission reference

Every permission of the catalog, what it allows, and the built-in roles that hold it. Custom roles combine any organization permissions.

Platform

Organization and access

Data

Dashboards and reports

Alerts and reliability

Pipelines and functions

Mole Agent

Roles and grants API

Last modified on October 26, 2026