A user’s connection role determines whether that user can add and manage connections and whether they can use a connection to add source data or publish data. Connection roles include admin, editor, and viewer.

In summary:

• Connection admins can select this connection when adding source data and configuring publish destinations. If this user is also a tenant editor or admin, they can edit and delete the connection.

• Connection editors can add source data from a connection. They can also select the connection when configuring data publish.

• Connection viewers can view and use the sources added through a connection. They can run publish jobs configured with that connection. They cannot, however, add new source data from that connection or set up a new publish configuration using that connection.

• Users without a connection role can view and use sources added through the connection. They cannot, however, add new source data from that connection. They also cannot set up a new publish configuration using that connection or run publish jobs using that connection

  Note for legacy data products: For legacy data products, connection roles are not applicable when adding source data to a data product, creating publish configurations, or running publish jobs. Those permissions are determined by the legacy data product roles. See Legacy Data Product Permissions.

  The tables below provides more detail on the connection role inherited from the tenant role, and on the permissions allowed by each connection role.

Connection Roles Inherited from Tenant Role

A user’s tenant level role determines their default (inherited) connection roles. Tenant admins can grant users additional roles and remove granted roles.

Connection Role Permissions

The following table defines the actions allowed by each connection role.