The basics
How roles work in Scanqur
Five roles, ready to use
You invite each team member with one of five roles, each mapped to real duties:
- Manager: everything except owner-level settings (menu, orders, reservations, reports)
- Kitchen: the live order feed and product availability, to see what to prepare and mark what has run out
- Waiter: orders on the floor (view, deliver, complete)
- Host: reservations (confirm, decline and manage bookings)
- Staff: day-to-day basics without settings or reports
Invites that fit how teams hire
Invite each person by email with a role. The invitation arrives in their inbox, and you can also copy its link to send it yourself, by WhatsApp for example. Each invitation belongs to one person. New teammates accept, create their own login, and land directly in their role’s view. The free plan includes 2 team members; Pro includes 10.
Step-by-step guide
Set up your team in fifteen minutes
- 1
Map people to roles
Before touching the dashboard, list your team and their duties. If a duty isn’t in someone’s job, it shouldn’t be in their dashboard. When in doubt, choose the narrower role.
- 2
Send the invitations
On the Team page, invite each person by email with their role. If an invitation email does not arrive, copy the invitation link and send it to that person directly.
Watch the tutorial
See how to invite staff and manage team access directly from your Scanqur dashboard.
- 3
Have everyone log in before the shift
Each teammate accepts, sets a password, and takes a two-minute tour of their view. Kitchen sees orders; host sees reservations. The tour is short because the screens are.
Tip: Onboard on a quiet afternoon, not five minutes before Friday service.
- 4
Retire the shared login
Once everyone has their own account, the owner login goes back to being yours alone. That password changes today.
- 5
Review the roster when the team changes
New hire → invite with a role. Departure → remove the account, effective immediately. Promotion → change the role. The roster should always match the schedule on the wall.
Access hygiene
Team management best practices
Do this
Grant the minimum, expand on need
It is painless to widen someone’s access when a real need appears, and awkward to narrow it after an incident. Start narrow.
Remove departures the same day
Offboarding is one tap. Make it part of the same conversation as returning the apron.
Use manager roles for real deputies
The person who runs the room when you are away should have manager access, so you can actually be away.
Avoid this
Don’t hand out manager roles as compliments
Roles are about duties, not seniority or trust. A ten-year veteran waiter still doesn’t need pricing access to deliver plates.
Don’t share accounts between shift-mates
Two cooks sharing one kitchen login recreates the old problem in miniature. Accounts are free, give each person theirs.
Don’t leave invite links floating
Treat invitation links like keys: send each one only to the person it is for, and cancel any invitation still unanswered once the hiring wave is done.
The Scanqur way
Team features sized for real teams
Personal logins for everyone
Each teammate works under their own account. Accountability without surveillance, and no more sticky-note passwords.
Role-based permissions
Five roles cover the classic restaurant org chart. Access follows the role, and a promotion is a one-tap role change.
Invitations you can forward
Every invitation has its own link: if the email goes to spam, copy the link and send it by WhatsApp. One invitation per person, so access always matches a real name.
Focused screens per role
Kitchen opens to live orders; the host opens to bookings. Less searching, fewer mistakes, faster shifts.
Illustrative example
A restaurant owner takes his first real day off
A fictional business, to show how the pieces fit together.
Hassan ran his 40-seat restaurant through one Scanqur login, his. Every 86’d dish, every reservation confirmation, every order question went through his phone. His last full day off predated the restaurant.
Setting up the team took one quiet Tuesday afternoon, on Pro, which allows up to ten team members: his second-in-command became manager, two cooks got kitchen access, three waiters got waiter roles, each from their own invitation, and his host got reservations. Then he changed his own password and kept it to himself.
The room reorganised itself within a week. The kitchen marks orders done at the pass, the host confirms bookings from the stand, and his deputy handles menu changes on Hassan’s day off, which now exists and is a Sunday.
The unexpected bonus came a month later, when a waiter left on short notice. Hassan removed the account from his couch in ten seconds. No password change, no team disruption, no sticky note.
Common questions
Team & roles, answered
Invite each person to Scanqur with a role: manager, kitchen, waiter, host or staff. Everyone gets a personal login scoped to their job, so nobody works under the owner account and nobody sees screens their role doesn’t need.
Managers get near-full access including menu, orders, reservations and reports. Kitchen sees the live order feed. Waiters handle orders on the floor. Hosts manage reservations. Staff covers day-to-day basics without settings or reports. Owner-level settings stay with the owner.
Invite a specific email with a role attached. The invitation is emailed, and you can copy its link to send it yourself if needed; each invitation is for one person. Invitees create their own account and land directly in their role’s view.
Remove their account from the Team page and access ends immediately, with no shared-password rotation and no disruption for the rest of the team. This is the single biggest security upgrade over one-account setups.
Yes, in one tap. Promote a waiter to manager or narrow an access that turned out too broad; the change applies on their next screen load.
Yes. The free plan includes 2 team members and Pro includes 10, enough for a café with two employees or a full brigade with kitchen, floor, host stand and management.
Only if their role includes it. Reports and analytics belong to manager- and owner-level access; kitchen, waiter, host and staff roles don’t see financial data.
Shared logins mean no accountability, no safe offboarding, and every accident available to everyone. Role-based access costs a few minutes of setup and removes all three problems permanently.

