Permissions

Pipeline permissions determine the access that users have to a . The owner of the and users with the Admin role have full access to a . As a owner or a user with the Admin role, you can also assign permissions to individual users and to groups.

To perform -related tasks, you must have the appropriate permissions as well as the role associated with the task. For example, a user with the Guest role can only view a when granted read permission for it. Similarly, to edit a with a Creator role, you need both read and write permission on the .

To easily enable access to sets of users, grant permissions to groups. For example, say you have five users who require read and execute access to run several . To allow this, you must share each with each of these users. But if the users are in a single Operations group, you can simply assign read and execute access to the Operations group instead of assigning the permissions to each user individually.

To use permissions, enable the .access.control.enabled Data Collector configuration property, and configure the permissions on a -by- basis.

By default, the .access.control.enabled property is disabled. When pipeline permissions are disabled, access to pipelines is based on the roles assigned to the user and its groups.

You can configure the following permissions:

For details about sharing with users and groups, see Sharing a.