How do roles and permissions work?
Owner, admin, member — plus custom roles.
01System roles
Every member holds a role: owner (full control), admin (management except deletion, ownership and the money-level settings), or member (day-to-day access). What you can see and do follows your role.
02Roles are bundles of permissions
A role is not a hard-coded tier — it is a set of permission keys, one per capability, and the platform checks the key rather than the role name. That is why a member can be given approval rights without being made an admin.
03Custom roles
Organisation Settings → Roles & Permissions lists the system roles alongside any custom ones you create. A custom role can be named, given exactly the permissions it needs, renamed later, and deleted; the system roles cannot be deleted.
04What a missing permission looks like
Things you cannot do are absent rather than greyed out — no tab, no button, no menu entry. That is a presentation choice, not the security model: the server re-authorises every single call regardless of what the screen offered, so a hidden button is not a lock and a forced request still fails.