Process access¶
Process access decides who can start a process and who supervises its cases. It is where the process stops being a diagram and becomes something a group of people uses.
Permissions¶
The Permissions section assigns a group or a user to a target task:
| Field | Meaning |
|---|---|
| Group or user | Who receives the access. The field suggests existing users and groups as you type |
| Target task | Which task the permission applies to. The selector reads Select an option until you choose one |
Adding a permission reports that it was assigned; removing one reports that it was removed. Check the wording when you remove: the confirmation should say removed, not assigned.
Permissions are additive: a user who matches two rules gets both. Removing a rule does not remove access granted by another.
Supervisors¶
Supervisors can follow the process: they see its cases in Process Supervisor without being assigned to them.
- Add a supervisor: the page confirms the assignment.
- Remove a supervisor: the page confirms the removal.
A supervisor is not a participant: supervising does not let someone work a task unless the task is also assigned to them.
Who can start the process¶
A process is startable by a user when they are assigned to its initial task, either directly or through a group. If nobody is assigned, the process appears in no one's new case dialog.
That is the usual cause of "the process is active but nobody can start it": the diagram is fine, the initial task has no assignment. Check it here before looking anywhere else.
Permissions to edit this page¶
Editing process access requires design permission for the process. See Permission reference.
Related¶
- Task properties — assignment rules per task.
- Processes — activating the process.
- Process Supervisor — the supervisor's view.