Skip to main content

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

Requiring a privilege for a rule

Updated on July 1, 2021

You can update a rule to specify that a privilege is required to access or use that rule. Only certain rule forms include the Privilege field, and for the rules that do, entering privileges is optional.

The following table lists the rules that require privileges and the function of the privilege for each of the rules:

RulePrivilege function
ActivitiesOnly users with the privilege can execute the activity.
Attachment category rulesOnly users with the privilege can perform certain operations on an attachment.
CorrespondenceOnly users with the privilege can use the rule.
FlowsOnly users with the privilege can start the flow.
Flow actionsOnly users with the privilege can select certain actions.
Parse structured rulesOnly users with the privilege can execute rules.
Report definition rulesOnly users with the privilege can produce the report or chart.
Note: There are two ways to require a privilege on a rule:
  • Certain rules always require a privilege.
  • For a specific use case, you can require a privilege.
  1. Open the rule form for the rule that requires the privilege.
  2. On the Security tab, in the Privilege name field, enter the privilege name.
  3. Click Save As.
  4. Click Create and open.
For example: For example, to add the AllFlowActions privilege to the ShowDescription flow action, complete the following steps:
  1. In the navigation pane of Dev Studio, click RecordsProcessFlow Action.
  2. In the Flow Action tab, in the Action Name column, click Show Description.
  3. Click the Security tab.
  4. In the Privilege name field, choose AllFlowActions.
  5. Click Save As.
  6. Click Create and open.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us