Owner vs Master: Who Should See What in Your Booking Calendar
The moment you hire your first master, your calendar stops being just a schedule — it becomes a question of access. Salon staff calendar permissions sound like a boring settings-page detail, but get them wrong and you either hand a new hire your entire client list on day one, or you make them ask you for basic information every single day. Neither is free.
The day this actually bites you
Picture a barbershop with two chairs. The owner cuts hair and also handles bookings, prices and the client list. She hires a second barber — a good one, with his own following. Two weeks in, he's frustrated: he can't see his own upcoming appointments without texting her, doesn't know which walk-in slots are open, and has started keeping his "regulars" in his personal notes app instead of the shop's system. Three months later he opens his own chair across town — and takes 40 of those regulars with him, because they were never really in the shop's system. They were in his phone.
That's not a hypothetical. It's the default outcome of two extremes: giving a new hire nothing, or giving them everything.
What "everything" actually costs
Owners who skip permissions entirely and just hand out one shared login are optimizing for convenience today and paying for it later. A master with full access can see every client's phone number, every other master's schedule, revenue figures, and cancellation history — none of which they need to do their job. If that master leaves on bad terms, you're not revoking a permission, you're hoping they don't screenshot your client list on the way out.
This isn't paranoia. It's the same reason a restaurant doesn't give every server access to the safe. Access should match responsibility, not trust level — trust can change; a well-designed system shouldn't have to change with it.
What "nothing" actually costs
The opposite mistake is just as common and less talked about: an owner who's been burned before locks everything down, and now a master can't see their own week without asking. That friction shows up as small delays — a master texting "what do I have tomorrow?" — that add up to real time lost, and a subtler cost: a master who feels like a subcontractor rather than part of the business tends to act like one. They stop caring about the shop's booking page, the shop's reviews, the shop's growth, because none of it visibly belongs to them either.
The split that actually works
The right model isn't about trust at all — it's about scope. A master should have full control over their own chair and zero visibility into anyone else's business.
- Owner sees every master's calendar, every client's full history and contact details, revenue and cancellation reports, and can edit services, prices and hours for the whole business.
- Master sees and manages only their own calendar — accepting, rescheduling or blocking their own time — and only the client details relevant to their own upcoming appointments.
That's it. No shared logins, no "just ask the owner," no full client export sitting in someone else's notes app. A master who wants to know if they're free on Thursday should be able to check without a text message. A master who's leaving shouldn't be able to walk out with the full client database, because they never had it — just their own slice of it.
This is also why the jump from solo master to a real team usually causes more chaos than the actual hiring decision. The scheduling habits that worked for one calendar — one shared notebook, one phone number for everyone to text — don't scale to two people without someone deciding, explicitly, who sees what. Waiting until after the second hire to figure this out means retrofitting permissions onto a system that already has bad habits baked in.
Client ownership is the real stake here
Underneath the permissions question is a bigger one: whose clients are these, actually? Your client base is arguably the most valuable asset your business owns — more valuable than the chairs, the lease, or this month's revenue. Every time a client's full contact details and visit history sit in a master's personal phone instead of the shop's system, that asset is quietly leaking out the door. Not through malice, usually — just through a booking system that never drew a line between "your calendar" and "the business's calendar."
Getting the owner/master split right isn't about distrust. It's about making sure that when a master does leave — and eventually, some will — the business keeps its clients, its history and its bookings, because those never lived in one person's inbox to begin with.
This is exactly the gap ScheDjin's role system is built to close: an owner sees the whole calendar, every client, every number; a master gets their own chair, their own bookings, nothing more. No shared password, no manual gatekeeping, no client list that walks out the door with a resignation. If you're about to hire your first team member, ScheDjin sets this up in the settings tab before the awkward part ever comes up.