Your kitchen needs orders. Your host needs reservations. Nobody needs your revenue reports except you. Scanqur’s team management lets you invite staff with a role (manager, kitchen, waiter, host or staff), and each sees exactly the screens their job requires.
Casa Verde
4 team members · 1 invite pending
The typical setup: one account, one password, written on a sticky note by the register. Every waiter, cook and weekend temp logs in as "the owner". Then a price gets changed by accident, a product vanishes, and there is no way to know who, when, or how. And when someone leaves, changing the password logs out the entire team mid-service.
A restaurant already runs on roles: kitchen, floor, host stand, management. Scanqur maps its dashboard to those same roles, so the software finally matches how the room actually works. Each person gets their own login and precisely the access their job needs; nothing more, nothing missing.
You invite each team member with one of five roles, each mapped to real duties:
Send an invitation to a specific email, or generate a shareable invite link with a role attached, which is practical when onboarding several people at once. New teammates accept, create their own login, and land directly in their role’s view.
When a shared password walks out the door with a former employee, your only fix disrupts everyone. With individual accounts, you remove one person in one tap.
A trainee looking for today’s orders has no business two taps from your pricing. Full access for everyone means every mistake is possible for anyone.
A cook confronted with analytics, settings and reservations hunts for the one screen they need. Role-scoped views make each job faster, not just safer.
Each teammate works under their own account. Accountability without surveillance, and no more sticky-note passwords.
Five roles cover the classic restaurant org chart. Access follows the role, and a promotion is a one-tap role change.
Onboard the summer crew with one link per role instead of five individual emails.
Kitchen opens to live orders; the host opens to bookings. Less searching, fewer mistakes, faster shifts.
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.
In the Team page, invite each person by email with their role, or generate a role-scoped invite link for group onboarding.
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.
Once everyone has their own account, the owner login goes back to being yours alone. That password changes today.
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.
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.
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 role-scoped invite links like keys: share them deliberately and regenerate them once the hiring wave is done.
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: his second-in-command became manager, two cooks got kitchen access, three waiters got waiter roles via a shared invite link, 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.
7
team members, each with their own view
15 min
total setup time
1
weekly day off, finally real
Roles shine brightest when these features are switched on.
Complete or cancel with a reason, keep every order on file, and read revenue, average order value and cancellation rate monthly.
Read articleThe guest browsing your menu tonight books a table for tomorrow, on the same page. No second platform, no fees per guest.
Read articleOne code per table, orders arrive tagged in your dashboard, and the floor keeps moving. Full setup guide.
Read articleInvite your team, hand each person their slice of the dashboard, and take back your phone, and maybe a day off. Free with Scanqur.
Teams from two-person cafés to full brigades run on Scanqur roles.