- 2 minutes to read

What permissions are required to use BPM?

Quick Answer

BPM requires a BPM license. Everything else is set on Roles, in three permission sets:

To... The Role needs Permission set
Open the Repository Access Repository: Allow Repository Model
View BPMs BPMs: Access (read-only) Repository Model
Create or change BPMs BPMs: Create, Modify Repository Model
Create or change Domains (swimlanes) Domains: Create, Modify Repository Model
See events on the BPM A Log View the Role can use, plus Access Log Log Views
See payload and context of those events View Body, View Context on that Log View Log Views
See the lightbulb on a Service Each linked Resource must be in at least one Monitor View your Role can access Monitor Views
Run Remote Actions Execute Action Monitor Views

Each permission is Inherited, Allow, or Deny, and Deny always wins.

Typical Roles

Business Users

Access on BPMs plus the process's Log Views, such as Order 2 Cash in the Order-to-Cash demo, to follow an order with BPM Log Search. Leave View Body off if they shouldn't see payloads.

Process Designers

Add Create and Modify on BPMs and Domains, and Access on the Services they place in the cells.

Operations

Make sure the Resources behind the Services are in a Monitor View the Role can access, and grant Execute Action.

Symptoms and Fixes

Symptom Likely cause
No Repository in the menu Access Repository not allowed for any of the user's Roles
BPM visible, but no Log View to choose in Log Search The Role can't use any Log View, or none of those associated with the BPM
A BPM doesn't appear in a grouped Log View The Role can't see that BPM
No lightbulb on a Service Its Resources aren't in any Monitor View your Role can access, or no Resources are linked
No Remote Actions Execute Action not allowed

Next Steps