Release Teams and Permissions
In Digital.ai Release, use teams to group users who have the same role. You can assign permissions to teams on folders, top-level templates, and top-level releases. When designing the release flow of a template or a release, you can assign tasks to teams. Team members will then be responsible for completing the task and will be notified when the task starts.
In Digital.ai Release, templates and releases that are stored in a folder inherit the security settings of the folder in which they are located. If you create a template in a folder or move a template to a folder, there are no individual settings on the template; you must define teams and permissions on the folder level.
A folder inherits teams, permissions, and all other settings from its parent folder. You can also define all settings on the folder itself. If you deselect the Inherit permissions from parent folder option on a folder, all settings are copied and are no longer in sync with the parent folder.
You can also manage folder permissions in YAML. For more information, see Manage Release folder permissions in YAML.
In cases where a template or release does not have a folder, permissions can be set in the Teams & Permissions screen in the Show menu. Because of the complications this can cause with managing permissions, we recommend moving all templates into folders as a best practice. For more information on migrating into folders, see Migrating templates to folders.
Note: As of v.9.6, the global Manage triggers permission was removed. Any existing global triggers will now inherit the global Create template permission, and users can no longer use triggers for any template that is not in a folder. If you are upgrading with root-level templates that have trigger permissions, we recommend migrating the triggers into folders.
To configure release teams:
- Click Folders from the left navigation bar.
- Select a folder.
- Click Teams & Permissions.
- Click New team to add a new team.
- Add a role by typing in the Global roles column. For more information, see configure roles
- Add individual users by typing in the Users column.
- Click Save.
The following system-defined teams are created by default in Digital.ai Release, which you cannot remove.
|Folder owner||Users who manage folders, subfolders, and folder security.||All folder permissions|
|Release Admin||Contains the release owners, the users who are responsible for executing the release. Members of this team receive extra notifications. For example, when a task fails and the release is stopped.||All release permissions|
|Template owner||Users who design templates.||All template permissions|
Note: You can add, remove, and assign users and permissions to the system-defined teams.
Important: System-defined teams are similar to regular teams but with some permissions given to them by default. Revoking some of the permissions from the system-defined teams is not recommended as it may result in unpredictable behavior.
- Click Folders from the left navigation bar.
- Select a folder.
Click Teams & Permissions.
Note: If the folder is the child of another folder, the Inherit permissions from parent folder option is selected by default. If you want this folder to have different permissions, disable this option.
- Under Folder permissions, add release teams to each permission.
- Click Save.
In Digital.ai Release, the following permissions are required for templates and releases that are not stored in a folder:
- The Edit Template Security permission.
- The Edit Release Security permission, on a specific template or release.
- The Edit Security global permission.
For more information, see configure permissions.
To configure permissions on a folder, the Edit Folder Security permission is required.
The following permissions apply to folders:
|View folder||View the folder in the Folders tab.|
|Edit folder||Rename, move, delete or add a subfolder to the current folder.|
|Edit folder variables||Edit folder variables.|
|Edit folder security||Edit the teams and permissions on a folder.|
|Edit folder teams and permissions||Edit the teams and permissions on a folder, with the limitations listed above.|
|Edit folder notifications||Edit the notifications on the folder.|
|Apply Changes||Apply any changes to the folder from the CLI or version control tab.|
|Generate Configuration||Generate Configuration for the folder from CLI or version control tab.|
Teams with the Edit folder teams and permissions permission can manage the team composition and the permissions of all the teams within the folder, similar to the Folder Owner permission. There are two limitations:
- You cannot modify teams that have the Edit folder security or Edit teams and permissions permission.
- You cannot add or remove the Edit folder security or Edit teams and permissions permissions.
Teams with the Edit folder notifications permission will get the notifications of all the teams within the folder.
You can view the Teams & Permissions tab if you have the Edit folder teams and permissions permission. You cannot view the Edit folder teams and permissions and Edit Folder Security permissions or the teams that have these permissions from this tab.
The following permissions apply to templates:
|View templates||Can see templates organized by folder in the Folders screen and listed together in the Templates screen.|
|Edit templates||Change the template by adding and editing tasks and phases.|
|Edit template security||Edit teams and permissions templates that are not in a folder.|
|Lock task||When a template task is locked only users with lock permissions are able to edit or unlock it. A locked task appears striped to indicate that it is locked. For more information, see Configuring lock tasks.|
|Edit task precondition||Edit the task’s precondition in a template.|
|Edit task failure handler||Edit the task failure handler on a task in a template.|
The following permissions apply to releases:
|View Release||View all releases in this folder and any releases that do not have a folder.|
|Edit Release||Edit the release by adding and moving tasks and phases. Edit release properties and variables.|
|Create release||Create a release from a template.|
|Create release in another folder||Create a release from a template in other folder.|
|Start Release||Start a planned release.|
|Abort Release||Abort an active or planned release.|
|Edit Release Security||Edit teams and permissions in a release (if the release hasn’t already started in a folder).|
|Restart phase||Teams with the Restart phase permission are allowed to restart a phase in a running release (in-progress release).|
The following permissions apply to tasks in a release:
|Lock tasks||Lock tasks to prevent users without lock permissions from editing them.|
|All task permissions||Inherits all release task permissions that follow in this section (not including the lock task permission).|
|Perform task transitions||Can change the state of a task including Complete, Skip, Fail, Retry, Abort, and Reopen.|
|Perform task transitions in advance||Can change the state of a task, such as Complete or Skip in advance (before the task is completed).|
|Assign task ownership||Assign tasks to another user or team. If the user has task ownership, this permission is given by default.|
|Edit title and description||Edit task title and description.|
|Edit task-specific properties||Edit configuration data that is specific for the task type.|
|Edit scripts||Edit Jython, Groovy or External script task types.|
|Edit flag||Change the alert status and description for tasks.|
|Edit tags||Add or remove tags on tasks in a release.|
|Edit dates||Change start date, end date and duration for a task.|
|Edit blackout periods||Enable or disable the Postpone during blackout period setting at the task level.|
|Edit preconditions||Edit preconditions on tasks in a release.|
|Edit failure handlers||Edit failure handlers on tasks in a release.|
|Edit reporting attributes||Edit reporting attributes on tasks in a release.|
|Manage attachments||Add or remove attachments from tasks in a release.|
From Release 22.1, a release owner cannot perform task transitions without the required permissions. In the earlier releases, a release owner could complete, skip, or abort a task without the Perform task transitions or Edit tasks permissions.
To configure the release owner task transition permission, set the
xl.features.release-owner.task-transition.allowed = true in the
xl-release.conf file. By default, the value is set to
The following permissions apply to delivery patterns:
The following permissions apply to deliveries used in Software Delivery:
|View Deliveries tab||View deliveries inside the Deliveries tab in the Folders screen.|
|Edit delivery||View, edit, or create deliveries.|
|Edit tracked item||View deliveries inside the Deliveries tab in the Folders screen and perform operations on their tracked items.|
The following permissions apply to delivery patterns used in Software Delivery:
|View delivery pattern||View delivery patterns inside the Patterns tab in the Folders screen.|
|Edit delivery pattern||View, edit, or create delivery patterns.|
The following permissions apply to dashboards:
|Edit dashboards||Edit custom dashboards in folders.|
|View Dashboards tab||View the Dashboards tab in a folder.|
The following permissions apply to release groups:
|View release groups||View the Groups tab in a folder.|
|Edit release groups||Edit or create release groups.|
The following permissions apply to GitOps-enabled version control:
|View versions||View the Version control tab in a folder.|
|Edit versions||Connect folder to Git, create and apply versions of folder content.|
The following permissions apply to configurations:
|Edit configuration||Edit entries in the Configuration tab in a folder.|
|Manage triggers||Edit triggers for the folder in the Triggers tab and the Triggers item in the template drop-down menu for the folder.|
|View triggers||View triggers for the folder in the Triggers tab and the Triggers item in the template drop-down menu.|