Dynamic permissions & roles – permissions that travel with the process
In many organisations permissions are static: you set them once, and they stay until someone remembers to adjust them. linqi thinks differently. Permissions and roles can be assigned with fine granularity in linqi – and above all: processes can change them during the run. A process can, for example, define who may handle an item, restrict permissions for a specific step, or revoke access once an item is completed.
That is the difference between “maintaining permissions” and “permissions that belong to the item”. Instead of manually re-adjusting when an item reaches the next state, the process itself handles the permission assignment – automatically, traceably and without the risk of forgetting. This keeps the principle of least privilege not just a goal, but enforced in day-to-day operation.
Who may do what – the workflow decides
linqi distinguishes between clearly defined roles and fine-grained permissions that you can assign per mandator and per area. On top of that, the process itself can grant and revoke permissions: for example, it can define who is allowed to handle a specific item, which people have access within a parallel section, or restrict access when a step is completed. These actions run as normal process steps – documented and traceable. The result is a permission landscape that moves with operation instead of going static.
Frequently asked questions about dynamic permissions & roles
What is the difference to static permissions?
Static permissions are set once and stay. In linqi, processes can grant, change or revoke permissions during the run – so the permission assignment adapts to the current state of the item.
How granular are the permissions?
linqi distinguishes many clearly defined permissions – for example for process handling, exports, administration or process definition – that you can assign per role.
Can a process define who may handle an item?
Yes. The process can set the handlers of an item (also in parallel sections) and restrict or extend access accordingly.
What happens to permissions when an item is completed?
Permissions can be revoked automatically as soon as the process calls for it – so access is not kept open unnecessarily long.