Skip to main content

How to bulk assign access to team shared pipelines and CI jobs to a single user?

Provide access to multiple pipelines and ci jobs to single user

Jacob Joshua avatar
Written by Jacob Joshua
Updated yesterday

Below guidelines will lead you through assigning multiple permissions for team-shared Pipeline(s) and CI jobs to a single member on your Gearset team.

  • In My account menu, select Users tab. This will present a list of all the users in your Gearset team.

  • You should see the Users tab open with a preview showing all the users.

  • Select a team Member by clicking on this button:

    This will display user's profile. Scroll down a bit to Pipelines & CI jobs section - here you can see all the team-shared resources (Pipelines & CI jobs) that selected member has access to.

  • Then click on Edit access to pipelines & CI jobs button

While remaining on the same page (if you followed the steps above), you can switch tab to Delegate access to other pipelines & Ci jobs.

  • This page shows all the pipelines and CI jobs that this user doesn't yet have any access to.

    • Here, similarly to the other tab, you can assign Pipeline permissions (None, View, Edit, Admin) or permissions for Standalone CI jobs (None, Run, Edit, Admin).

Bulk assign access to other CI jobs

This option, once enabled, activates the checkboxes next to all Standalone CI jobs that user doesn't have any access to.

To assign bulk access, follow these steps:

  • By ticking relevant checkboxes, select all the CI jobs or individual jobs for which you want to grant user the same level of access. Normally, these are jobs for which user currently has None access assigned (3).

  • Now define the access type you want to grant for selected CI jobs (4) by selecting either: Validate, Run, Edit, Admin or Owner.

  • Click Save

    and Gearset will give your chosen access level to all the selected jobs.

Quick video demonstration where we're assigning "Run" permission for all the CI jobs that user Jacob doesn't have access to.

​Note: After access is assigned, the jobs have disappeared off the list. This is expected behavior because the jobs are no longer classified as CI jobs that user doesn't have any access to.

Assigning permissions to multiple members

Below guidelines will lead you through assigning permissions for team-shared Pipeline(s) and CI jobs to multiple member on your Gearset team.

How to assign permissions for user-owned or team-shared org connections which are not used in Gearset Pipelines?
For guidelines, please refer to our documentation on sharing org credentials with team members where we explain how to assign access via Delegate org access page in the app.

Did this answer your question?