User Roles and Permissions

Your user role and permissions determine your access to resources and functionality in Tamr Cloud.

The combination of your user role and permissions for shared resources determine your access to resources and functionality in Tamr Cloud. Resources include entity types, publishing destinations, and connections to cloud storage locations.

Your role determines the functionality you can access by default and your ability to create new resources.

Your permissions for resources shared with you determine the actions you can perform on those resources, regardless of your role.

User Roles

Tamr provides three user roles: data citizen, author, and admin. test test

Admins have full access to all Tamr Cloud functionality and resources. They can fully manage all entity types, publishing destinations, and connections.

Authors have access to most Tamr Cloud functionality. Authors can fully manage the resources that they create (entity types, publishing connections, and destinations). For shared resources, an author's permissions depend on the permission level assigned to them for that resource.

Data Citizens have access only to Studio by default, and cannot create new entity types, publishing destinations, or connections. For shared resources, a data citizen's permissions depend on the permission level assigned to them for that resource.

The table below summarizes default menu options for each role:

Menu OptionData CitizenAuthorAdmin
StudioYesYesYes
DesignerNoYesYes
CuratorNoYesYes
PublishNoYesYes
Admin > ConnectionsNoYesYes
Admin > SourcesNoYesYes
Admin > JobsNoYesYes
Admin > UsersNoNoYes
Admin > SchedulerNoNoYes
Admin > API KeysNoNoYes

The following table summarizes which roles can add new resources:

FunctionData CitizenAuthorAdmin
Add Entity TypeNoYesYes
Add ConnectionNoYesYes
Add SourceNoYesYes
Add Publishing DestinationNoYesYes

Permissions for Shared Resources

You can share entity types, publishing destinations, sources, and connections with other users. When you share a resource with another user, you select the user's permissions for that resource. You can give other users permissions at your permission level or lower.

Examples:

  • If you have editor permissions for an entity type, you can give others editor, curator, publisher, or viewer permissions for that entity type.
  • If you have publisher permissions for an entity type, you can give others publisher or viewer permissions for that entity type.

Shared Entity Type Permissions

Share an entity type from Studio.

Tamr Cloud provides five permission levels for shared entity types, described in the table below.

Ownership cannot be changed through permissions.

Resource PermissionsViewerPublisherCuratorEditorOwner
View in StudioYesYesYesYesYes
View in PublishNoYesYesYesYes
PublishNoYesYesYesYes
View in CuratorNoNoYesYesYes
CurateNoNoYesYesYes
View in DesignerNoNoNoYesYes
Edit and Run Mastering FlowNoNoNoYesYes
Save a CopyNoNoNoYesYes
DeleteNoNoNoNoYes
Share OptionsViewerViewer
Publisher
Viewer
Publisher
Curator
Viewer
Publisher
Curator
Editor
Viewer
Publisher
Curator
Editor

Shared Source, Connection, and Publishing Destination Permissions

Share a connection from Admin > Connections. Share a source from Admin > Sources. Share a publishing destination for an entity type from Publish.

Tamr Cloud provides three permission levels for shared connections and publishing destination, described in the table below.

Ownership cannot be changed through permissions.

Resource PermissionViewerEditorOwner
ViewYesYesYes
EditNoYesYes
DeleteNoNoYes
Share OptionsViewerViewer
Editor
Viewer
Editor