Skip to content

Roles and the shape of your app

Sign two colleagues into the same workspace and they may see what look like two different products: one gets a rail of seventeen hubs with Treasury and Payroll inside Finance, the other gets two or three rows. Neither is broken. The navigation is a projection of what each seat is allowed to do, computed fresh on every page load.

The rail on the left shows hubs, not pages. In order:

Hub The pages inside it
Home Today, Approvals, Issues
Properties Properties
Inbox Inbox
Calendar Calendar
Pricing Price rules
Reservations Reservations, Bookings to Review, Complimentary Stays, Import Bookings
Guests Guests, Guest Screening, Reviews
Operations Housekeeping, Maintenance, Lock Codes, Access, Duty Roster
Channels Channels, WhatsApp, Booking website, Guest app
Automation Agent Hub, Message Templates, AI assistant
Finance Payments, Treasury, Expenses, Payroll, Assets, Period Close, Charges, Payables, Payees, Fees & Taxes, Guest tax, Accounting export
Reports Property Reports, P&L Report, ROI, Monthly Break-even, Cash Report, Operating Models, Daily Report, Occupancy Report, Report Builder
Partners Owner Portal, Owners, Owner Payouts, Investor Portal, Investors, Investor Model, Deals, Track Record, Proposals, Launch, Deployment
Support Support
Audit Audit
Billing Billing
Setup Settings, Feature status, Team, Access matrix, API keys, Webhooks

Click a hub and it opens its first page; the hub’s other pages appear as a tab bar across the top of the page. A hub with only one page you can open (Properties, Inbox, Calendar, for most people) opens straight to it with no tab bar. Some pages have tabs of their own below that - Settings has General, Operations, Payment channels and Approvals; Reservations has Inquiries, Bookings, Past stays and Extensions. That is why directions in this help centre read Hub → Page → Tab.

Three ingredients, multiplied together:

  1. Your capabilities. Your seat’s roles each grant a set of permissions (capabilities), and your seat holds the union of them.
  2. The page registry. Every page in the app declares the view capability that gates it. A page not in the registry doesn’t exist; a page whose capability you lack isn’t shown - and isn’t reachable by its address either. The rail and the page guard read the same registry, so what you see and what you can open never disagree.
  3. The hubs. The pages you can open are laid into the hubs above, in a fixed order. A hub with no page you can open does not exist for you: a role that can’t see any finance page gets no Finance hub at all, which is why a Cleaner’s app has no trace of one rather than a grayed one. Inside a hub, the tab bar shows only your own pages.
Who What their rail looks like
Admin Nearly everything: all seventeen hubs, with every page except the Housekeeping queue and the two external portals.
Front-of-house roles (Point of Contact, Booking Manager, Guest Manager, Co-Host, Front Desk) Home (Today), Properties, Inbox, Calendar, Reservations and Guests, plus Lock Codes, the Daily Report and Report Builder. The Point of Contact and Booking Manager also get the Agent Hub; the Booking Manager adds Approvals and Issues; Front Desk adds Maintenance.
Account Manager The front-of-house set plus Approvals and Issues, the Finance hub (all but Guest tax), all of Reports, Partners (without the two portals), WhatsApp, the Agent Hub, and Settings and Feature status.
Property Manager Home (Today, Approvals, Issues), Properties, Calendar, Reservations, Guest Screening and Reviews, Operations (Housekeeping, Maintenance, Lock Codes), the Agent Hub, the Daily Report and Report Builder.
Cleaner, Inspector, Maintenance Housekeeping and Maintenance - their working queue - and Support.
External Accountant Finance and Reports, read-only (without Payroll, Fees & Taxes, Accounting export or the Daily Report), Partners including the Owner Portal, and the guest tax rules - nothing operational.
Auditor Audit, the Daily Report, the Occupancy Report, Complimentary Stays and Report Builder.
Property owner, Investor Their own portal only, as a plain row (no hubs and no search palette), plus Support.

The roles matrix lists every role and every screen it reaches.

If a page you expect isn’t in your rail, your seat doesn’t hold its capability - that’s the whole diagnosis. Nothing is loading late, and typing the address won’t help (same registry, same answer). The fix is a role change on Setup → Team, decided by whoever holds that power in your workspace.

Four refinements worth knowing:

  • Locked, not hidden. A page your role may use but your workspace’s plan doesn’t include stays in the rail, marked locked, and clicks through to Billing. Role says you can; plan says not yet - those are different answers, shown differently.
  • The bell is chrome, not a page. Notifications reach every seat and live behind the bell icon, not a rail row.
  • Support is everyone’s. Every seat has the Support row, but it does not count as a page of the product: it never becomes your start page.
  • Where the rail looks empty. A seat entitled to no page at all - possible for misconfigured external seats - lands on a page that says so plainly and offers the two useful moves: switch workspace or sign out.

Two baselines sit under the role library. Every seat, without exception, can see its own notifications and the support portal. Every member-flavored seat also gets a small read floor - Today, Reservations, Guest Screening, Guests, Reviews, Lock Codes, Calendar, Properties, the Daily Report and Report Builder - which is why most operational roles share the same first few hubs. Portal-only seats (Cleaner, Inspector, Maintenance, Investor, the property Owner, the External Accountant) are deliberately below that floor: their job needs one surface, so their seat gets one surface.