#Roles and permissions
Roles with permissions per kind of object can be defined, but they are not yet assigned in the interface and not applied — today everyone who can sign in has the same access to the Designer and the Execution app.
#What decides what today
flowchart LR S["Signing in"] --> D["The whole Designer"] S --> E["The whole Execution app"] C["Catalog assignment"] -. "what is offered,<br/>not what is allowed" .-> E R["Role"] -. "defined, not applied" .-> X["—"]
| What | Effect today |
|---|---|
| Signing in | Gives access to the Designer and the Execution app, in full |
| Catalog assignment | Decides which catalogs a person is offered — see catalogs |
| Group membership | Decides who gets a task in a multi-instance step over the group — see users and groups |
| Protected system admin | Cannot be changed or removed by others |
| Role | ⚠️ No effect |
| Process owner | Receives comment notifications; it grants no rights |
⚠️ Keep the circle of people with an account to those who may see and change everything: there is no way yet to give someone only the Execution app, or only some processes.
#The roles page
Roles & permissions lists roles and, per role, what it would allow — view, manage or admin — for processes, projects, forms, systems, users, roles, catalogs, areas and groups.
⚠️ The page is only in the sidebar when experimental features are switched on for your installation.
❌ Roles cannot be given to a person in the interface.
❌ Nothing checks roles or their permissions yet.
A role that is still held by someone cannot be deleted. The message is German.