Everyone sees only their part.
You see everything.
A three-tier access model so every person sees exactly what they need, and no more.
How the same action looks different depending on who's doing it.
One Thursday at Downtown, seen through each role.
Front desk asks, but can't apply
( 01 )Sophie B. sends a 20% request for Ashley Carter's late-starting massage. Her staff role has no Apply button, so it goes to the manager.
The manager decides for Downtown
( 02 )Downtown's manager approves it and confirms two pending bookings. Midtown and Uptown never appear on that screen.
The owner sees every branch
( 03 )As admin, the owner sees all three branches, every payment and every approved discount for the day, in one place.
Everyone sees their part
( 04 )The same revenue screen is hidden from staff and limited to one branch for managers. Roles are set once, not policed every day.
Thursday · admin view
By branchOnly admins see this view.
Revenue · all branches
Admins only
Set once in Settings · Roles
The right view for every role.
Staff
Focused on the day's work.
Create bookings, record payments, and request discounts — focused on the day's work, not information that isn't theirs to act on.
-
Request a discount, don't apply it
-
Create and manage today's bookings
-
See your queue, not the whole business
Can do
Not in this role
Sent to the manager · 2:10 PM
Manager
Run the branch, nothing more.
Confirm bookings, approve discount requests, and see branch-level performance — authority without overreach.
-
Confirm bookings for your branch
-
Approve or decline discount requests
-
See your branch's full day
“Started 15 min late”
2 bookings to confirm · Downtown only
Admin
The complete picture.
See every branch, approve everything, and hold the complete financial and operational picture.
-
See every branch in one view
-
Own the financial and audit record
-
Set the structure, trust the system to hold it
2 discounts approved · visible to admins only
What changes on day one.
What you stop doing
- Giving every login the same permissions and hoping nothing goes wrong
- Discovering after the fact who cancelled a booking or applied a discount
- Letting front-desk staff see revenue and cross-branch data that isn't theirs to act on
- Relying on trust alone to keep access aligned with responsibility
What you start doing
- Giving every person exactly the access their role requires — no more, no less
- Tying every discount, status change, and approval to a role and a name
- Keeping financial and cross-branch data with the people who own it
- Letting managers operate with real authority without stepping on each other, or on you
Things we get asked.
Answers to what owners ask before they switch.
In a small team, role clarity matters more, not less. When one person wears many hats, they need to know exactly what they're responsible for in each context. Roles give structure to a team that might otherwise operate in comfortable ambiguity — until something goes wrong.
Roles are assigned to users when they're added to the platform. There's no complex configuration. Admin, manager, or staff — that's the decision. The system handles the rest.
In Zennly, front-desk staff handle bookings and check-ins, managers approve discounts and staff transfers for their branch, and admins see and control everything across every branch — each role only sees what its job requires.
Role-based access isn't distrust — it's design. A well-designed kitchen has different stations for different functions. The chef doesn't design the menu and plate every dish simultaneously. Roles let your team operate at their level of authority without stepping on each other.
Owners see everything across branches, managers see their branch and approve discounts, and front-desk staff handle bookings and payments. Role-based access limits each person to what they need.
Everyone deserves to see exactly what they need to do their job. Nothing more.
No credit card required · Live in a day · Real support when you need it
