Roles & Permissions
What each role can do in the CMS
Permissions are written as resource.action. The actions on most resources are view, create, update, delete and export.
| Resource | Owner | Admin | Manager | Employee | Viewer |
|---|---|---|---|---|---|
| Customers | all | all | all | view, create, update | view |
| Items | all | all | all | view | view |
| Reservations | all | all | all | view, create, update | view |
| Content (pages, news) | all | all | all | view | view |
| Comments | view, create, delete | view, create, delete | view, create, delete | view, create | view |
| Attendance | view, create, update | view, create, update | view, create, update | view, create | view |
| Analytics | view | view | view | no | view |
| Import | create | create | create | no | no |
| Settings | view, update | view, update | view | no | no |
| Billing | view, update | view | no | no | no |
| Team (members, invitations) | manage | manage | no | no | no |
"all" means view, create, update, delete and export. The customer role is a renter of the company and has no CMS access.
Per-member overrides
For customers, items, reservations, content, comments, attendance, analytics, import and settings an owner or admin can replace a member's allowed actions on that resource. An override replaces the role's actions, and an empty list denies everything. Team and billing permissions stay role-only, and owners are never restricted.
Roles can be combined in one membership (comma separated); a permission is granted if any of them grants it.