Skip to main content
Using swimlanes we can make sure only certain user roles have access to certain process nodes. In certain scenarios, it is necessary to restrict access to specific process nodes based on user roles. This can be achieved by organizing nodes into different swimlanes. Each swimlane can be configured to grant access only to users with specific runtime roles. Roles are defined at the organization level and listed on each project version. Which user or end-user group holds a role on a given solution is configured from the Share modal on the Solutions page — see Runtime authorization for the full model (5.8.0+). Up to 5.7.0, the chosen identity provider platform was the source of truth for runtime roles. Depending on the type of node added within a swimlane, only users with the corresponding swimlane roles will have the ability to initiate process instances, view process instances, and perform actions on them. Scopes and roles for managing processes When creating a new process definition, a default swimlane will automatically be added. As the token moves from one node to the next, it may transition between swimlanes. If a user interacting with the process instance no longer has access to the new swimlane, they will observe the process in read-only mode and will be unable to interact with it until the token returns to a swimlane they have access to. Users will receive notifications when they can no longer interact with the process or when they can resume actions on it.

Permission-based expressions

Control UI element visibility and interaction based on user roles

Access roles configuration

Set up scopes and roles for managing processes

From Zero to Build course

End-to-end project build course covering swimlanes, permissions, and all major platform features
Last modified on May 12, 2026

Related topics

Process definitionTask managementPermission-based expressionsConfiguring access roles for processesExtracting additional data in business rules