Container Data Catalog Links Permissions
There is no container-level permission for catalog links. Everything a user can do with a container's links is decided by their team permission on the datastore the container belongs to.
The full permission model lives at the datastore level
User roles, how the two permission layers combine, the Admin bypass, and who can start synchronizations are documented in Data Catalog Links Permissions at the datastore level. Everything there applies to containers unchanged.
Team Permissions (Checked on the Datastore)
| Action | Reporter | Viewer | Drafter | Author | Editor |
|---|---|---|---|---|---|
| View the container's catalog links | |||||
| Link, change, or unlink the container | |||||
| Search the catalog's tables when linking |
Without the Editor Team Permission
The container's dialog opens read-only. The Link an asset, Change asset, and Unlink controls are hidden, and so is the hint pointing to the datastore-level synchronization. Manual and automatic links stay visible to anyone who can open the container; only changes are gated.
See Also
-
How It Works
Where container links come from, and how manual and automatic links behave.
-
Synchronization
What a synchronization exchanges for container links, and why it runs at the datastore level.