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.

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)
Insights
View insights	✅	✅	✅	❌
Publish
Add publish destination	✅	✅	❌	❌
Edit publish destination	✅	✅	❌	❌
Delete publish destination	✅	✅	❌	❌
Publish to destination	✅	✅	❌	❌
Curation
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	✅	✅	❌	❌
Manage Data Product
Edit metadata	✅	❌	❌	❌
Delete data product	✅	❌	❌	❌
Copy data product	✅	❌	❌	❌
View data product role assignments	✅	✅	✅	❌
Manage data product role assignments	✅	❌	❌	❌

Note: If your tenant has not been configured for Tamr RealTime and you have configured sensitive fields in a data product, viewers cannot access the 360 pages for that data product.