Access and roles
What Staff vs Reception sees, role-based filtering
Access and roles
Staff Portal is role-based: Staff only sees own bookings and customers, Reception and Manager see more.
The 4 roles
Bookinda's role system:
- OWNER – everything
- MANAGER – everything except SuperAdmin operations
- RECEPTION – booking management, customer CRM, register
- STAFF – only own bookings and customers
What Staff sees in Staff Portal
Bookings
- Only own bookings (NOT other staff's)
- Only their own bookings can have state modified
Customers
- Own customers (who ever booked with them)
- Other customers not visible (privacy)
Finances
- Only own commission data (Manager → Reports → Team → Commission Activity)
- Own wage data (Wages)
- Salon-level finances NOT (Finance, Reports → Finance)
Settings
- Own profile settings (language, push, dark mode)
- Salon-level settings NOT (Settings, Marketing, Automations)
Team
- Sees team list (who their colleagues are)
- Can't edit other colleague's data
What Reception sees (in Staff Portal)
Reception also uses Staff Portal but sees more:
- All customers (not just own)
- All bookings (via salon-level calendar)
- Cash register (salon's till)
- Customer CRM operations (new customer, edit notes)
Reception gets an "expanded" Staff Portal.
What Manager / Owner sees
Manager / Owner gets the full Manager UI:
- Sidebar has "Manager dashboard" link from Staff Portal
- Full UI (booking calendar, reports, settings, marketing, etc.)
Role escalation prohibition
A STAFF-role user can't access Manager routes:
- If they type URL by hand (
/manager/settings/...), auto-redirected to Staff Portal - Backend permission check on every API call
Privilege escalation impossible.
Multi-location and role
In multi-location salon:
- STAFF sees only own location's bookings
- MANAGER can be location-specific (only Location 1)
- OWNER everywhere
Role swap process
If Staff is promoted to Reception:
- Owner / Manager → Settings → Staff → select → Role: RECEPTION → Save
- Next login, Staff gets expanded Staff Portal
- (Or Manager UI if promoted to Manager level)
When to use it
Scenario 1, new staff hire New hairstylist. Owner → Staff → + New → role: STAFF. Auth link sent. Logs in, sees only own bookings.
Scenario 2, reception team expansion New receptionist. Role: RECEPTION. Logs in, sees all customers and bookings.
Scenario 3, temporary Reception permission Anna stylist on vacation, Béla covers reception. Role temporarily → RECEPTION (1 week). After, back to STAFF.
Scenario 4, access dispute Staff says they can't see a customer. Customer probably booked with another staff. Reception permission needed.
Scenario 5, audit investigation NAIH audits salon data handling. Explain role system: Staff can't access another customer's data, privacy-respected.
Tips
- STAFF role is privacy-friendly, don't promote anyone to Reception just for "convenience."
- Reception-permission responsibility: all customer-data access falls under privacy strictness.
- Manager permission is responsible for salon finances, separate trust.
- Role swap isn't retroactive on past bookings: Staff-handled bookings stay in their name.
- Multi-location filtering is privacy-strengthening: one location's Staff shouldn't see another's customers.
- Audit log records role operations, who and when changed a staff member's role.