...
In addition to the global permissions configured for Groups, FlexDeploy supports a hierarchical permission model for folders, projects, and releases. This permission model allows fine-grained access control to meet any security requirements. Default permissions can be set on the root folder for the entire hierarchy.
| Tip |
|---|
|
Overriding Security
To override the security permissions, first open a folder or project by double-clicking on it. Then click on the Security tab.
Click the Override Security button to override the permissions of the parent folder.
...
Select the permissions you wish to grant for any particular groups.
You can begin typing the name of the group that you want to add to find it quickly.
...
Click on the group to add it.
Click the Save button to save any changes.
At any point, if you decide to inherit permissions from parent again, then toggle Override Security off and click Save.
The table below provides a summary of the permissions for folder and project type. For Release permissions, view Release Security.
Folder Security
Permission | Description |
|---|---|
Read | Folder and sub-folders read is allowed, i.e. folder can be opened by user. The read permission is added automatically if a group is assigned to any of the folder permissions. |
Create Folder/Project | Project and Folder can be created in this folder. |
Create Release | Releases can be created in this folder. |
Configure Folder | Folder can be configured. |
Project Security
Permission | Description |
|---|---|
Read | Project read is allowed, i.e. project can be opened by user. The read permission is added automatically if a group is assigned to any of the project permissions or the 'Create Folder/Project' folder permission. |
View Logs | Project execution and associated logs can be viewed |
Configure Project | Project can be configured (allows updates on Configurations tab of project). |
Configure Files | Project files can be discovered, updated, and evaluated. Only applies to package-based projects |
Inactivate Missing Files | Inactivate missing files is available when discovering project files. Only applies to package-based projects |
Configure Commands | Build and Deployment commands for package-based projects can be managed. This should generally be restricted to admin users. Only applies to package-based projects. |
Execute | Grants permission to execute build/deploy/execute/test workflows. Deployment to specific environments are further controlled by Deployment Permissions. |
| Tip |
|---|
The FlexDeploy permission model offers great flexibility for managing security. However, you must understand that with fine-grained security comes the overhead of needing to configure and maintain it. You should avoid managing permissions at a level lower than you really need. For example, if you choose to manage all security at the individual project level, you will need to configure the security every time you create a new project. Instead, if you establish permissions near the top of the folder hierarchy, you will only need to configure security when you create new high-level folders or when your security requirements change. |