# Field Data Catalog Links Permissions

Source: https://userguide.qualytics.io/fields/data-catalog-links/deep-dive/permissions/

There is no field-level permission for catalog links. Everything a user can do with a field's links is decided by their team permission on the **datastore the field belongs to** (through the field's container).

> **Info: 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](https://userguide.qualytics.io/source-datastore/data-catalog-links/deep-dive/permissions/) at the datastore level. Everything there applies to fields unchanged.

## Team Permissions (Checked on the Datastore)

| Action | Reporter | Viewer | Drafter | Author | Editor |
| --- | --- | --- | --- | --- | --- |
| View the field's catalog links | Allowed | Allowed | Allowed | Allowed | Allowed |
| Link, change, or unlink the field | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Search the catalog's columns when linking | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |

## Without the Editor Team Permission

The field'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 field; only changes are gated.

## See Also

- **How It Works**

  Where field links come from, and how manual and automatic links behave.

  [How It Works](https://userguide.qualytics.io/fields/data-catalog-links/deep-dive/how-it-works/)
- **Synchronization**

  What a synchronization exchanges for field links, and why it runs at the datastore level.

  [Synchronization](https://userguide.qualytics.io/fields/data-catalog-links/deep-dive/synchronization/)

*Last updated: September 7, 2026.*
