User roles and access levels
Exactly what each role can open, and how to decide who gets which.
Access in SupremeStay is granted by ticking permissions on a user. There are five of them, and they are not a ladder — they are five separate doors. A user holds however many they need, and every user must hold at least one or the invitation is refused.
Above them sits one account that is not a permission at all.
The account owner
The person whose account the property belongs to is the subscription owner. There is one, they have everything, and their permissions cannot be edited — the checkboxes are greyed out on their row, including for themselves. This is deliberate: it stops a property being locked out of its own settings by a mistake.
Everyone else is granted access with the five permissions below.
What each permission opens
| Permission | Can open |
|---|---|
| Management | Everything: Dashboard, Customers, Reservations, Transactions, Inventory, Housekeeping, Chat, Transport, Digital Signage, Restaurant, Reports and Settings. |
| Reception | Dashboard, Customers, Reservations, Inventory, Housekeeping, Chat, Transport. |
| Housekeeping | The Housekeeping board. |
| Restaurant | The restaurant point of sale. |
| Transport | Pick-ups, drop-offs and the transport schedule. |
Everyone, whatever they hold, sees Sticky notes.
The three lines worth reading twice:
- Management is the only permission that reaches Settings — and therefore the only one that can change rates, policies, taxes, or anybody else’s access.
- Management is also the only one that reaches Transactions and Reports. Reception can take a payment on a booking but cannot open the property’s financial picture.
- Housekeeping, Restaurant and Transport are deliberately narrow. Someone holding only Housekeeping sees room status and nothing about money at all.
Assigning them
Permissions are set when you invite someone from Settings → Users, and changed the same way afterwards.
A few other things the invite form does:
- At least one permission is required. Saving with none ticked is refused.
- Email cannot be changed after inviting. Editing a user leaves the email field locked; to move someone to a different address, invite the new one and delete the old.
- Language is set per person at invite time, and they can change it themselves later on their Account page.
Choosing who gets what
- Management goes to the people who are accountable for the property, not to everyone who is senior. It is the permission that can change money.
- Reception is the everyday one. Most front desk staff need this and nothing else.
- Permissions combine. A duty manager who also works the desk holds Management and Reception; a supervisor covering the restaurant in the evening holds Reception and Restaurant.
- Start narrow. Adding a permission later takes seconds. Working out who changed a rate three weeks ago because everybody had Management takes an afternoon.
What permissions do not control
- Language is per person, on their own Account page — not part of their access.
- Which property someone can open is decided by which properties they were invited to, not by permission. Someone can be Management at one property and Reception at another, and the sidebar changes as they switch.
- Actions are always attributed. Whatever the permission, every change is recorded against the person who made it in the activity log — see System reports.
If something does not work
| What you see | Why |
|---|---|
| Someone signs in and the workspace is nearly empty | They hold a permission for a module that is switched off, or only a narrow one such as Housekeeping. |
| A permission checkbox is missing from the invite form | That module is off for the property. Switch it on first. |
| I cannot save an invitation | At least one permission has to be ticked. |
| I cannot edit the owner’s permissions | The subscription owner’s access is fixed and cannot be changed by anyone. |
| I cannot change a user’s email | It is locked after inviting. Invite the new address and delete the old user. |
| A colleague cannot see Reports or Transactions | Those need Management. Reception does not reach them. |
| Access differs between two properties | Permissions are per property. Check the user at each one. |