Allow Removing or Setting “No Access” for Users in Step Update Security

Currently, when using Step Update Security, it is only possible to add security groups or users. However, there is no option to remove an existing user or explicitly set their permission to No Access.

In our use case, we want to apply security to a specific folder and ensure that the CLM user does not have access. With the current functionality, the CLM user cannot be removed or restricted through Step Update Security, which limits our ability to properly control folder permissions.

Requested enhancement:

• Allow removal of existing users/groups when using Step Update Security.

• Allow explicitly setting “No Access” for a specific user (e.g., CLM user group).

• Enable administrators to fully control folder-level security through the step configuration.

Benefit:

This enhancement would provide more flexible and complete security management, allowing administrators to ensure that unwanted users (such as CLM system users) can be removed or restricted when configuring folder permissions.

 

Use Case

When the workflow creates a new supplier folder and the “Finance” subfolder, the security settings must be automated so that only the “Finance Security” group has access.

To meet confidentiality requirements, access for default groups (for example, the “CLM User” group) must be removed so that these users cannot view the folder.

Current Platform Behavior

Based on the current platform design, the Update Security step in a CLM workflow is additive only. This means it can grant permissions to additional users or groups, but it cannot remove existing permissions, remove inherited permissions, or set a group's access level to “No Access.”