Permissions & Access
How permissions work in Cadenio
A model that is easy to reason about and safe by default: each person sees only what they need, and you open up the rest in a controlled way.
Permissions & Access
A model that is easy to reason about and safe by default: each person sees only what they need, and you open up the rest in a controlled way.
The core idea: access is denied by default. A new member sees no flows or folders until they are granted access. This prevents accidental exposure and is the foundation of least privilege — instead of 'everyone sees everything and you scramble to restrict.'
Owner
Admin
Member
What a regular member (with no grants) and an Admin see when they join the organization.
| Resource | Member (default) | Admin |
|---|---|---|
| Flows (templates) | None until granted | All |
| Folders | None until granted | All |
| Runs | Only those they own or are responsible for | All |
| Tasks | Only those they created or were assigned | All |
| Organization settings | No access | Management access |
How to grant access
Instead of configuring permission by permission, start from a preset and fine-tune per folder or flow when needed. To scale, grant access to a group and add people to it.
Relationship access
Regardless of grants, a person can always work on the tasks and runs where they are the creator, owner, or assignee. Someone with edit rights can fill a task; completing it requires being responsible for it.
Approvals
On approval tasks, only the configured approvers decide — not even the run owner or an Admin approves on their behalf unless they are on the list. This is the control compliance expects.
External participants. Need someone outside to fill in a step? Share the task by link with per-action permissions (fill, upload, comment, complete). Links expire and can be revoked at any time — without giving access to the organization.
FAQ
Nothing. Cadenio is deny-by-default: a new member sees no flows or folders until they are explicitly granted access — through a preset, a folder/flow grant, or a group that has access. The exception is tasks and runs they own or are responsible for: there they can always act.
The Owner owns the organization and has unrestricted access. An Admin also has full access by default, but can be limited by an exception rule that only the Owner can create. Regular members get tailored access.
You grant access with a preset (Viewer, Member, Team Lead, Process Manager) or granularly on a specific folder or flow. To scale, use groups: grant access to the group and add people to it.
Only the people configured as approvers for that task — not even the run owner or an Admin can approve on their behalf unless they are on the list. This enforces segregation of duties for compliance.
You share specific tasks by link with per-action permissions (fill fields, upload files, comment, complete). Links expire and can be revoked at any time.
Our team can help design roles, groups, and presets that fit your governance.