Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Restrict who can use a flow action

Updated on March 15, 2022

It is a best practice to limit flow actions to the users who really require them.

To restrict a flow action:

  • Update the Security tab of the Flow Action form to identify one or more privileges that allow run-time use of the action.
  • Update one or more Rule-Access-Role-Obj rules, for specific access roles, to convey privileges to access roles.

When processing an assignment at, users can only view and select from the flow actions that match their privileges.

Pega Platform provides a privilege for each standard flow action. You can follow this model and create a privilege for each new flow action that you create.

To make design easier, the Work-.AllFlowActions privilege allows access to all standard flow actions. This privilege is supplied for expedient debugging and power users and should not be used for normal work.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us