Staff & scheduling
Everyone gets their own login and sees only their job
Invite staff by email, give them a role, and they get a dashboard scoped to it — servers see the floor, the kitchen sees tickets, managers see everything. Schedules and clock-in hours live in the same place.
14-day free trial, everything unlocked.Included in every plan
One person, one login
Offboarding is a click — not a password change for the whole team.
Role-scoped views
Servers, kitchen and managers each land somewhere useful.
Shifts & hours
Schedule the week; staff clock in and see their own shifts.
Attribution
Order activity is traceable to a person, not to "the tablet".
Access
Roles that mean something
A role isn't a label — it changes what the person can reach. Kitchen staff never land on your revenue reports, and a server doesn't need to be trusted with your payout settings.
- Invite by email; the person sets their own password.
- Server, kitchen and manager roles with scoped navigation.
- A dedicated /staff dashboard: POS, orders, kitchen and my shifts.
- Remove someone and their access is gone — no shared credential to rotate.
Scheduling
The rota and the hours in the same system as the service
Build the week's schedule, let staff see their own shifts, and track clock-in hours against what you actually rostered.
- Weekly schedule visible to the people on it.
- Clock-in hours recorded per staff member.
- Staff see their own shifts on their own dashboard — no group chat screenshot.
Accountability
Who did what, without watching anyone
Order changes and payments are attributed. The live "handled by" field tells you who touched it last, and the audit trail tells you the whole story when it matters.
Payments record the staff member who took them.
Order changes leave an audit trail rather than only a last-toucher name.
Useful for training and for the rare argument about a bill — not for surveillance.
A shared login isn't a shortcut. It's the reason you can't answer who did that.
Rolling it out
How to put staff & scheduling into your restaurant
The order that works, and roughly what each step costs you in time. Every step links to the step-by-step guide in the Help Center.
- 01List who needs accessServers, kitchen, managers. Decide the role before you send the invite — it's what their dashboard will be.Read the guide
- 02Send the invitesStaff → Invite, email plus role. They set their own password and land in a scoped dashboard.Read the guide
- 03Build the first week's scheduleGet one week in so staff can see their shifts in the same place they take orders.Read the guide
- 04Kill the shared loginThe day everyone has their own account, retire the one you were all using. That's the point of the exercise.Read the guide
Works with
None of this is sold separately. These are the parts of the platform this one leans on most.
Frequently asked questions
- Does every staff member need their own account?
- They should. Individual logins mean role-scoped access, accurate attribution on orders and payments, and one-click offboarding instead of changing a password everybody knows.
- What can each role see?
- Servers get the floor and order taking, kitchen gets the ticket board, and managers get the full dashboard. Staff land on a dedicated dashboard with POS, orders, kitchen and their own shifts.
- Can staff see their schedule?
- Yes. Shifts are visible to the people rostered on them from their own dashboard, and clock-in hours are recorded per person.
- Can I see who took a payment?
- Yes. Payments record the staff member who took them, and order changes leave an audit trail beyond just who touched the order last.
- Is there a limit on staff accounts?
- The Starter plan caps staff; higher plans are unlimited. See /#pricing for your market.
Start using staff & scheduling this week
Free for 14 days with everything unlocked. Set it up alongside how you work today, and keep whichever parts earn their place.