Versions Compared

Old Version 1

changes.mady.by.user Karl Henselin

Saved on

compared with

New Version Current

changes.mady.by.user Chandresh Patel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

  • 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.

...

The table below provides a summary of the permissions for each object folder and project type. For Release permissions, view Release Security.

Permission

Description

Read

Grants permission to open

objects

folders and projects for viewing.

View Logs

Grants permission to view logs for underlying executions.

Project execution and associated logs can be viewed

Create Folder/Project

Grants permission create objects

Folders and Projects can be created in this folder.

Create Release

Releases can be created in this folder.

Configure Folder/Project

Grants permission to manage objects under configure tab

Can configure folders and projects.

Configure Files

Grants permission to configure Files and its Attributes. Allows for populate of files as well.

Project files can be discovered, updated, and evaluated. Only applies to package-based projects

Inactivate Missing Files

Grants permission to inactivate

Inactivate missing files

while populating

is available when discovering project files. Only applies to package-based projects

Configure Commands

Grants permission to manage the

Build and

Deploy commands of files

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.