Picture a host stand tablet logged in as the general manager. The host can see last night's sales by server, a guest's phone number and email, and the notes a manager wrote about a server who ran late twice last week. Nobody planned that. It happened because one shared login was easier than setting up five. In my view, restaurant roles and permissions are a hospitality decision, not an IT chore: a host, a server and a general manager need different screens, and the right boundaries protect your guests, your team and the trust between them.
I'm Richard Yu. I have more than 15 years of startup and go-to-market experience, much of it in customer success and solutions engineering, and I'm a co-founder and the Managing Partner for marketing and operations at the restaurant I co-founded in San Francisco. I built Regular, the hospitality operating system, inside that restaurant, one service at a time. Here is how I think about who should see what.
Why Everyone Seeing Everything Backfires
Open access feels friendly. In my experience it usually creates three problems, and they show up slowly.
The first is comparison without context. When a full leaderboard sits on a shared screen, a newer server on slow weekday sections reads it as a verdict on them, not as information. Coaching becomes harder because the number arrived before the conversation did.
The second is guest privacy. A guest who books for an anniversary gives you a phone number and an email so you can confirm the table. They did not agree to have that sitting on a tablet anyone can pick up. When someone leaves the team, whatever they could see often leaves with them in their memory or their screenshots.
The third is noise. A host at 6:45 on a Friday needs tonight's book, allergies and seating notes. Sales reports and labour figures are just more to scroll past while the door is opening.
So my starting position is simple: each person gets the least access that lets them do their job well tonight, and you add from there when a real need appears.
Staff See Their Own Numbers
Servers and bartenders should see their own performance. Hiding it treats them like they cannot handle the truth. Showing them everyone else's turns a coaching tool into a scoreboard.
In Regular, Server Performance splits each table turn into stages from seated to departed, and staff only ever see their own numbers, plus team figures large enough that nobody can be singled out. That second part matters more than it sounds. Picture a bar team of three. If the bar's average check is shown to the team, and two bartenders know their own figure, the third person's number is simple arithmetic. A team figure is only anonymous when the group is big enough.
What a server sees for themselves should point to something they can change at the next shift: time from seated to first order, time from entrées to dessert, how their tables pace against the party sizes they had. I wrote more about using those stages in how to coach the stages of a table. The rule I keep is that a manager should have discussed a number with someone before that person stumbles on it alone.
Managers See Their Department
A front-of-house manager and a kitchen manager run different parts of the same night. They both need depth, but mostly in their own area. The general manager and owners see across the whole restaurant.
Guest information deserves its own thinking, because it is the data most worth protecting. Here is how I would split it for a typical independent restaurant:
- Host: tonight's reservations, visit history, VIPs, allergies and seating notes. This is what Today's Guests is for. Phone numbers only if the host is the one confirming or calling guests.
- Server: allergies, the occasion and seating notes for their own section. Rarely a phone number or email.
- Kitchen lead: allergies, covers and large-party menus, without guest contact details.
- Front-of-house manager: the full book, server performance for their team, attendance.
- Owners and general manager: guest contact details, email campaigns, reports and the whole team's numbers.
Department boundaries also depend on a clean staff list. If a former server is still active somewhere, they may still have access. That is why I start with one employee list and a single source of truth before touching permissions.
Custom Roles for How You Actually Work
Job titles in a small restaurant rarely match the org chart. Picture a lead server who opens on Tuesdays, handles the book on Wednesday when the host is off, and works the floor the rest of the week. A rigid "server" role gives them too little. A "manager" role gives them too much.
This is where custom roles help. In Regular there are built-in roles plus your own custom roles, and for each app you choose No Access, View or Full Access. Our lead server might get View on tonight's reservations and Full Access on nothing beyond their own coaching notes. A bar manager might get Full Access to attendance for the bar team and View on the reports. The details are on the roles and permissions page.
Sign-in in Regular is invite-only, so access starts with a deliberate decision rather than a shared password on a sticky note.
On technology: it should hold the boundaries consistently, so nobody has to remember who is allowed to see what at 8 p.m. It should not become a way to watch staff more closely than you would on the floor. If a permission exists only so someone can check up on a colleague, I would leave it off.
Checking What Someone Sees
Setting roles once is not the job. Checking them is. The most useful habit I know is to look at the screen through the other person's eyes. Regular has View As, which lets an owner see exactly what someone sees, and I find it catches mistakes a settings page hides.
Before your next service, run this check:
- Pick three people: a host, a server and a manager. Use View As or sit with them while they log in.
- Ask: can this person see any guest phone number or email they do not use tonight? If yes, remove it.
- Ask: can this person see another named colleague's performance numbers? For staff, the answer should be no.
- Look for anyone who left or changed roles in the last month and confirm their access matches today.
- Check shared devices at the host stand and bar. Each should sign in as a role, not as an owner.
- Write down one change, make it, and note it for your weekly manager review.
Privacy rules for guest and employee data vary by place, so check what applies in your city and state before deciding how long to keep contact details. If you want to see how roles look in practice, you can book a Regular demo. You can also find me on Instagram.
Frequently Asked Questions
What roles should a restaurant set up in its software?
Most independent restaurants can start with host, server or bartender, kitchen lead, front-of-house manager, and owner or general manager. Then add custom roles for the people whose jobs cross lines, like a lead server who covers the host stand. Give each role the least access that lets them do tonight's job, and add more only when a real need appears.
Should servers see each other's sales numbers?
In my view, no. Servers should see their own numbers so they can improve, plus team figures large enough that no individual can be worked out. A full named leaderboard on a shared screen often turns coaching into comparison. Managers can discuss rankings in a private conversation where the context, like sections and party sizes, comes with the number.
Who should have access to guest phone numbers and emails?
Only the people who use them. Owners and general managers usually need contact details for follow-up and email campaigns, and a host may need phone numbers to confirm bookings. Servers and kitchen staff usually need allergies, occasions and seating notes instead. Check local privacy rules for how long you may keep guest data.
How often should a restaurant review staff access?
A quick check each week during the manager's routine works well, plus a check whenever someone joins, leaves or changes role. Look at what a host, a server and a manager actually see on their screens, confirm former staff no longer have access, and make sure shared devices sign in with a limited role rather than an owner login.