Project Security
- Karl Henselin
In addition to the global permissions configured for Groups, FlexDeploy supports a hierarchical permission model for folders projects. 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.
Any Folder or Project can override the permissions of its parent, which will apply to all its children unless overridden again.
If security is not overridden, you will see the inherited permissions in read-only format.
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 each object type.
Permission | Description |
|---|---|
Read | Grants permission to open objects for viewing. |
View Logs | Grants permission to view logs for underlying executions. |
Create Folder/Project | Grants permission create objects. |
Configure Folder/Project | Grants permission to manage objects under configure tab. |
Configure Files | Grants permission to configure Files and its Attributes. Allows for populate of files as well. |
Inactivate Missing Files | Grants permission to inactivate missing files while populating files. |
Configure Commands | Grants permission to manage the Build and Deploy commands of files. |
Execute | Grants permission to execute build/deploy/execute/test workflows. |
Â
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.
- style