Note: This topic does not apply to legacy data products. See Legacy Data Product Permissions.

A user’s permissions in a specific data product depend on their project role and granted data product roles.

Data product roles include admin, developer, curator, and viewer.

In summary:

Data product admins have full access to that data product.
Data product developers can update the data product configuration, refresh the data product, and view data product data. They can also create and update publish configurations for the data product. They cannot curate the data.
Data product curators can curate and view the data in the data product.
Data product viewers:
- Data products with System of Record configured: Data product viewers can view the 360 pages for these data products. They can access these pages from the Browse menu option or by selecting the data product on the Data Products page.
- Data products without System of Record configured: Data product viewers cannot view the 360 pages for these data products. Their permissions for these data products are the same as for users without a data product role.
Users without a data product role have no access to the data product.

The tables below provides more detail on the data product role determined by a user's project role, and on the permissions allowed by each data product role.

Data Product Roles Inherited from Project Role

Within a project, a user’s default (inherited) data product roles are determined by their assigned project role. Tenant, project, and data product admins can grant users additional data product roles and remove granted roles.

Project Role	Inherited Data Product Roles
	Admin	Developer	Curator	Viewer
Admin	✅	✅	✅	✅
Editor	❌	✅	✅	✅
Viewer	❌	❌	❌	✅
No Role	❌	❌	❌	❌

Data Product Role Permissions

The following table defines the actions allowed by each data product role.

Action	Admin	Developer	Curator	Viewer
360 Pages
View 360 pages	✅	✅	✅	✅ (see note)
Edit record attributes from 360 pages	✅	❌	✅	❌
View relationships on 360 pages	✅	✅	✅	✅ (see note)
Create relationships from 360 pages	✅	❌	✅	❌
Edit relationships from 360 pages	✅	❌	✅	❌
Delete relationships from 360 pages	✅	❌	✅	❌
Insights
View insights	✅	✅	✅	❌
Publish Note: Connection role determines which connection a user can select when adding a publish destination. Users can only publish data to connections to which they have viewer access or higher.
Add publish destination	✅	✅	❌	❌
Edit publish destination	✅	✅	❌	❌
Delete publish destination	✅	✅	❌	❌
Publish to destination	✅	✅	❌	❌
Curator Hub
Curate source record clusters	✅	❌	✅	❌
Run queue cleanup to remove items associated with deleted golden records	✅	✅	❌	❌
Access and manage queue items	Based on queue role. See Queue Roles.
Curation (Batch)
View golden record and source record pages	✅	✅	✅	❌
Override attributes	✅	❌	✅	❌
Override clusters	✅	❌	✅	❌
Verify source records	✅	❌	✅	❌
Create views	✅	✅	✅	❌
Edit views	✅	✅	✅	❌
Delete views	✅	❌	✅	❌
Set personal default view	✅	✅	✅	❌
Set global default view	✅	❌	✅	❌
Tasks for Data Product
View tasks	✅	❌	✅	❌
Create tasks	✅	❌	✅	❌
Edit tasks	✅	❌	✅	❌
Delete tasks	✅	❌	✅	❌
Configure Data Product
Configure data product settings	✅	✅	❌	❌
Enable Tamr RealTime	✅	❌	❌	❌
Refresh data product	✅	✅	❌	❌
Copy data product	✅	❌	❌	❌
View data product role assignments	✅	✅	✅	❌
Manage data product role assignments	✅	❌	❌	❌
Manage Data Product
Edit metadata	✅	❌	❌	❌
Delete data product	✅	❌	❌	❌
Copy data product	✅	❌	❌	❌
View data product role assignments	✅	✅	✅	❌
Manage data product role assignments	✅	❌	❌	❌

Note: If the data product does not have a System of Record, viewers cannot access the 360 pages for that data product.