How do roles and permissions work?
Owner, admin and member, plus custom roles.
01System roles
Every member holds a role, and what you can see and do follows it.
- Owner
- Everything, including deletion, ownership transfer, Plan and billing, and Usage.
- Admin
- Everything except deletion, ownership, Plan and billing, and Usage.
- Member
- The day to day work: members, flows, offerings, orders, customers, forms and storage to see, and their own time.
02Roles are bundles of permissions
A role is not a fixed tier. It is a set of permissions, one for each tab of your organisation settings and each part of the doors, and the platform checks the permission rather than the role name. Some parts have a view and a manage permission. A permission always comes with the ones it needs: managing includes viewing, and every screen that uploads includes uploading files. Switching a permission off also switches off every permission that needs it, and the confirmation names them first. Daily acts such as seeing money on items, taking payments, taking sales, uploading files and sending refunds have permissions of their own, so a role can do its job without building or configuring anything. That is why a member can be given approval rights without being made an admin.
03Custom roles
Permissions in your organisation settings lists the system roles alongside any custom ones you create. Opening a role shows every permission under its area, with a tick on the ones the role holds. On a custom role, pressing a permission switches it on or off, and the role can be renamed or deleted; the system roles stay fixed.
04What a missing permission looks like
Things you cannot do are absent rather than greyed out: no tab, no button, no menu entry.