What permissions are required to use BPM?
BPM Module license required. User permissions controlled via Roles—create roles with BPM view access, BPM edit access, remote action permissions, and log view filtering based on domains or business areas. Delegate process visibility to business stakeholders without granting infrastructure access or admin rights.
Permission Levels
View BPM (Read-Only)
- See BPM designer and process steps
- View service health and status
- Click Search Field Links to view related logs
- No ability to edit BPM structure or execute remote actions
Typical users: Business analysts, executives, auditors
Edit BPM (Design Permission)
- Create new BPMs
- Modify BPM structure (add/remove steps, domains, services)
- Configure process correlation logic
- Delete or restore BPMs
Typical users: Integration architects, process designers
Execute Remote Actions
- View BPM and service health
- Execute pre-approved remote actions (restart services, purge queues, scale resources)
- No access to infrastructure (Azure Portal, RDP, admin credentials)
Typical users: Operations analysts, first-level support
Full BPM Administration
- All BPM permissions
- Configure monitoring agents
- Define thresholds and alerts
- Full infrastructure access
Typical users: DevOps administrators, system administrators
Domain-Based Filtering
Use Domains to restrict access by organizational unit:
- Finance team sees only Finance domain BPM steps
- Warehouse team sees only Warehouse domain BPM steps
- Executives see all domains in unified view
Next Step
Explore more in the Troubleshooting Overview or dive into Business Process Model (BPM) to get started.
Related Topics
- Business Process Model (BPM) - Main BPM overview
- Roles - Configure user permissions
- Domains - Organize by organizational units
- Remote Actions - Execute actions from BPM
- All FAQs - See all BPM FAQs