Roles
Roles bundle permissions. Each user has one role; permissions are per resource and per action (read, create, update, delete).
URL: /settings/roles · create /settings/roles/create
Default roles
| Role | Scope |
|---|---|
| Owner | Full access including subscription |
| Admin | Full admin access, no subscription |
| Manager | Full operational; limited on users/billing |
| Planner | Dispatch + shipments + orders |
| Finance | C/R, invoices, payment terms, GL |
| Read-only | Read only |
Custom role
Click Add role, name it, and tick the desired actions per resource. A user on a custom role sees the right menu items appear or disappear automatically.
Key principles
- Branches are not handled via roles, but via user-level access — see Users.
- Owner cannot be removed while it is the sole owner.
- Changes apply immediately to users on that role.
Related
Last updated on
