To assign a user as a group admin, click on "Edit This Pipeline Group" on the 'Pipelines Configuration' tab on the Administration page and edit it to add the following:

<pipelines group="studios">  
     <authorization> 
         <admins> 
            <user> jez </user> 
            <role> groupAdminRole </role> 
         </admins>
     </authorization>
     <pipeline name="go_pipeline">  
     ...
     </pipeline>
</pipelines>
        

Here, the Go admin has delegated group admin privileges to a user "jez" and all users defined under the role "groupAdminRole". The privileges of a Group Administrator have been described in the next section.

As a group administrator of a pipeline group, a user is privileged to:

• View and operate (trigger, rerun stages etc.) all the pipelines in this group.
• Add other group admins to this group
• Authorize users/roles with 'view' and 'operate' permissions for this pipeline group.
• Add and Delete pipelines to/from the group.
• Add a pipeline using the "Add New Pipeline" wizard, but only to the groups he is allowed to administer.
• Edit pipelines belonging to the group. Which includes renaming, adding, deleting and modifying stages and jobs.
• Restfully view and operate (trigger, rerun stages etc.) all the pipelines in this group.
• Restfully edit the pipelines belonging to this group.

Note: A group administrator cannot view any tab other than the 'Pipeline Configuration' on the Administration page. Hence, he/she cannot modify the source xml, server configuration or perform user management.

Also, he/she cannot view or edit the "Pipeline Templates". But an existing pipeline template can be used if its needed to create a pipeline in the group.