设置
Roles and what each one can do
The default role bundles, what each can and cannot reach, and how role, permission and app enablement combine to decide your sidebar.
最后更新
Who this is for: Owner, Manager — managing roles requires
org.roles.manage.
The default roles that ship with a Nerve organisation, and the boundary of each.
How to read this#
Three things decide whether you can reach a screen, and all three must be true:
- Your role carries the permission that screen requires.
- The app that owns the screen is enabled on the property.
- You are in a context — an organisation and a property — where that role applies.
That is why two people with the same role can see different sidebars: app enablement is per property, so it doubles as a feature gate. A screen you cannot reach is not hidden-but-present; the navigation is built from your resolved permission set, and a direct URL to it returns an unauthorized state that does not reveal whether any data exists behind it.
Roles are configurable per organisation. The table below is what each role carries by default.
Default role bundles#
| Role | Can | Cannot |
|---|---|---|
| Owner | Everything in the permission catalog | — |
| Manager | Front Desk (all), Housekeeping, Reservations reads plus messaging, reviews and content, ledger read, Revenue including accepting recommendations, member invite and management, property create and settings, audit read | Edit rates, availability or restrictions; manage channels; payables, receivables, night audit; role management; app enablement; the Integration Hub |
| Front Desk | Reservations, check-in and check-out, room assign and block, folio post and transfer, payments and refunds, invoices, guests, Housekeeping status | Everything else — no Reservations module, no Accounting, no Settings, no Members |
| Accountant | Ledger, chart of accounts, payables create and approve, receivables, night audit, reservation read | Front-desk mutations, Reservations, Revenue, Settings |
| Read-only | Read reservations, rates, bookings, messages, reviews, ledger, analytics, forecast and recommendations | Any mutation |
Permissions behind the Front Desk screens#
| Screen | Permission |
|---|---|
| Reservations | frontdesk.reservation.read |
| Room Rack | frontdesk.room.assign |
| Rooms & Units | frontdesk.room.block |
| Guests | frontdesk.guest.read |
| Arrivals & Check-in | frontdesk.checkin |
| Departures & Check-out | frontdesk.checkout |
| Folios & Billing | frontdesk.folio.post |
| Group Billing | frontdesk.folio.post |
| Payments | frontdesk.payment.take |
| Stay-Time Policies | frontdesk.reservation.read |
| Ancillary Catalog | frontdesk.ancillary.sell |
| Room Status Board (Housekeeping) | housekeeping.status.update |
Permissions behind the Settings screens#
| Screen | Permission |
|---|---|
| Members | org.members.invite |
| Roles | org.roles.manage |
| Hotel | hotel.settings.manage |
| Terminology | hotel.terminology.manage |
| Organisation | org.manage |
| Operator Links | org.manage |
| Delegation Roster | org.manage |
| Portfolio | org.portfolio.read |
| Audit Log | org.audit.read |
| Notifications | core.notifications.manage |
| Step-Up Security | core.stepup.manage |
| Data Import | core.import.read |
See also#
- Realms — why some accounts are asked to re-authenticate when they cross into another portal
- Front Desk overview — the module these Front Desk permissions gate