Team Permissions

Note

Admins are not subject to team permissions and can access all data assets. Team permissions only apply to users with the Manager and Member roles. For platform-level permissions, see the User Roles documentation.

Tag rules span two axes

Managing tag definitions (create, update, delete) is controlled by the Manager user role; any user with the Manager or Admin role can manage tag definitions regardless of team membership. Applying an existing tag to an asset, in contrast, is a team-permission action gated by the rows above. Users with the Manager user role do not bypass the team-permission gate for tag application: they must still hold the required team permission (Editor for datastores, containers, and fields; Drafter for draft quality checks; Author for active quality checks and anomalies) on the asset's datastore. Only Admin users bypass both axes.

Computed Asset ownership

Computed Assets (Computed Tables, Computed Files, Computed Joins, and Computed Fields) follow a hybrid ownership model. Authors can create, edit, and delete computed assets they personally own. Editors can manage any computed asset on the datastore regardless of owner, and only Editors can reassign ownership to another user. For a cross-datastore Computed Join, the user also needs at least Viewer permission on the right-side datastore to use its containers as join inputs.