What do staff see in the portal (vs my dashboard)?
The staff portal shows the same pages as your dashboard, trimmed to each person's plan and permissions — blocked items are hidden entirely.
The staff portal is the same ResoFlow — same Bookings list, same Timeline, same Floor plan where your venue takes bookings — inside a trimmed shell that only shows each person what they're allowed to use.
How the portal menu works. On phones and tablets the portal shows a bottom tab bar — three destinations, an Add button in the middle of them (the big round pink +), and More, which opens a sheet with the rest — Search or do anything at the top (it only offers the things your role lets you do), then four quick steps — the pages you open most (over the last 30 days, remembered for you at this venue; until then a starting set for your role), never one already on your bottom bar — then the full list (and Profile, Settings, Help and Sign out). Help opens the Help Centre's staff topic in a new tab — the guides for shifts, time off, swaps, clocking in and PINs. The dashboard's More on a phone is the same sheet. Add opens Seat a walk-in, New booking, Add to the waitlist and Find a table at the bottom of the screen, and Stop online bookings for someone who can change special dates — each only if the person's role allows it, with the same checks as the page's own button (a role with none of them gets four destinations and no Add). By default those three are the first two destinations plus the Scanner, which always keeps a place because it's what staff reach for most on a phone (gift cards, loyalty cards, event tickets). On bigger screens the portal has the same left-hand menu as the dashboard — your venue's name with "Staff portal" under it, the destinations grouped the dashboard's way — and it folds to icons from the button beside the venue's name (or the [ key) — folded, the venue's mark is that button; each person's choice is remembered. Every destination is checked against your plan first, then against the signed-in person's permissions, and anything blocked is hidden completely — staff never see padlocked or greyed-out pages, so a Host's menu is just shorter than a Manager's. For example, Guests only appears if your plan includes guest profiles AND the person can view guests.
Each person picks their own bottom buttons. On a phone or tablet, tap More then Customise buttons, choose up to three destinations (up to four when there is no Add button), and tap Save — they appear in the order they were picked. The choice is saved against the person, not the device, so every phone or tablet they sign in on shows the same ones, and two staff sharing one device each get their own. Anything not chosen is still in the More sheet, and if a chosen button later stops being available (a plan change, or a permission removed) it quietly drops out and the usual button takes its place. Reset to default in the same sheet puts the standard buttons back. The dashboard's phone bar can be customised the same way too — More, then Customise buttons — each owner or manager for themselves.
View as. Managers and admins get a View as switcher on the portal Home — a Manager can see the portal exactly as a Host does (the tabs and buttons follow that role's permissions), then switch back. It only ever narrows: nobody can view as a role above their own, and their real access is unchanged throughout.
What's never in the portal. Billing and plan management, support conversations, the set-up wizard, and plan-quota banners are dashboard-only — staff don't see any of them.
Settings in the portal. A Settings entry appears only for staff who hold a settings-view permission. Managers get the operational subset by default; Hosts have no settings access at all, so they never see the entry. Owner-only settings pages stay blocked even if someone types the address directly.
Typing a URL doesn't bypass anything. Opening a blocked page by its address bounces the person back with "You don't have permission to access that section." — the menu and the pages enforce the same rules.
A few more differences worth knowing:
- Theme and clock follow the person, not the device. Each staff member's light/dark choice and time format are saved to their profile, so a Host's dark mode doesn't change what the next person sees. The sign-in screen before anyone signs in (the names and the PIN pad) follows the device's own light or dark setting, so a tablet set to dark shows a dark sign-in screen at night.
- Idle sign-out uses the one time you set in Settings → Security policy (Sign out a shared device), and staff PIN sessions last at most 12 hours before a fresh sign-in is needed.
- Who's signed in is always named at the top of every portal page on the venue's own devices — their initials, their name ("Sam R.") and, on a wider screen, their role — with Switch beside it. Tapping the name opens their profile.
- Switch at the top of every portal page signs the person out and goes straight to the PIN pad for the next one. It only asks first when something on the page isn't saved ("You have unsaved changes on this page — sign out anyway?"). Switch person in the menu (and the More sheet on phones) does the same — the device stays set up, ready for the next PIN.
- If an owner or admin signs in on the portal page with their password, owners and admins are both sent to the main dashboard Home.
Related: How do staff sign in with a PIN? · What can each role do? · Why can't my staff see a page or button?