Note: Team owners will always have "Admin" permission on all team-shared resources (e.g. org connections, CI jobs and Pipelines), which bestows the same level of access as the "Edit" permission, with the addition of being able to delete team-owned resources and update their permissions.
List of available Pipeline permissions
Levels of access for a pipeline are:
Edit - this allows users to edit details of the pipeline, including adding, removing or rearranging static environments and dev sandboxes.
View - this allows users to view the pipeline, but user cannot change any pipeline settings.
None - this setting means users cannot see the pipeline or edit any of its details.
Admin - a team member becomes an owner of the pipeline, and they gain the ability to assign Pipelines permissions to other team members.
This permission doesn't automatically give an
Admindeployment rights for all the CI jobs within the pipeline. It's because permissions for team-shared CI jobs used within the pipeline are set up individually for each CI job.
Note: A team member with an
Adminaccess is also authorized to delete a pipeline, should there ever be a need for this.
Note: Even if a user has the "None" permission assigned for pipeline, that does not stop the user from running the CI jobs within the pipeline. Ability to Run the job is controlled by individual CI job permissions.
You may check this article which explains how to set team shared CI job permissions.
Assigning permissions for team-shared Pipelines
This step by step guide will help you manage permissions assigned to users for the team-shared Pipelines on your Gearset team.
Navigate to Pipelines & CI jobs page, and follow these steps:
Under Team-shared Pipelines, click on the right arrow button
: right next to the Pipeline you want to set permissions for.
Under Users section, select Edit pipeline users...
Next, under Access column select the type of permission (e.g.
None,View,EditorAdmin) you want to assign for an existing Member on your Gearset team.Note that all Team Owners by default have an Owner access to all team-shared pipelines, so you can't amend or downgrade this access.
Once you've assigned the necessary permission(s) to the user(s), make sure to scroll up a bit and hit
(see screenshot below). This is to ensure that your changes will be applied!
Check out the below sample video for navigating to the Team shared CI job in a pipeline.