Page Comparison

...

• Global permissions allow coarse grained permissions setup. See Global Use global permissions control access to various objects in FlexDeploy. Global permissions do not control access at individual item level but rather at entire object level, i.e. if you grant Create / Update access to group, members of that group can create or update any workflow. See global permissions for FlexDeploy group.
• Deployment permissionsUse deployment permissions to restrict available environments on deployment request form. See Deployment deployment permissions for FlexDeploy group. Control access to various menu items in FlexDeploy. For example, use Read and Create / Update permission for Workflow to allow specific actions to FlexDeploy Group.Control environments available on deployment request form, reference Creating/Editing a Groupif you want to restrict specific group of users from deploying environments other than development and test, then configure deployment permissions accordingly.
• Finer grained permissions
  1. Project - control access (read, create, configure, execute etc.) to specific projects for FlexDeploy groups. This allows you to control finer grained access (createYou can configure this for a project or folder. Configurations at folder level apply to all projects contained in it. See Project Security.
  2. Release - control access (read, configure, execute etc.) at project of folder level. See Project Security.
  3. Release
  4. Pipelineto specific release for FlexDeploy groups. You can configure this using global permissions and override at specific release as necessary. See Release Security.
  5. Pipeline - control access (abort, replay, skip etc.) on pipeline execution. Pipeline allows for abstraction in to roles that are mapped to FlexDeploy group and/or users. For example, developers, leaders, managers, operators etc. You can define available permissions on each pipeline role. See Pipeline team security.