{"id":25371,"date":"2026-11-04T22:01:09","date_gmt":"2026-11-04T22:01:09","guid":{"rendered":"https:\/\/alteg.io\/?p=25371"},"modified":"2026-11-06T15:29:09","modified_gmt":"2026-11-06T15:29:09","slug":"staff-permissions-salon","status":"publish","type":"post","link":"https:\/\/alteg.io\/en\/blog\/staff-permissions-salon\/","title":{"rendered":"Staff permissions in a salon: a manager\u2019s quick setup playbook"},"content":{"rendered":"
Set up role-based access, give every job the narrowest rights it needs, and hide client contact details from anyone who doesn\u2019t contact clients. That\u2019s the whole system in one sentence. Everything else is detail.<\/p>\n
If you do nothing else this week, do these three things in your salon software:<\/p>\n
\n
Keep one owner account with full access, and don\u2019t share its login with anyone.<\/li>\n
Give everyone else a narrower starting role \u2013 for example receptionist (appointments and payments, no financial reports) and stylist (own schedule and own clients only).<\/li>\n
Hide client phone numbers and email addresses, and switch off client-list export, for everyone who doesn\u2019t need them.<\/li>\n<\/ul>\n
Give every role the narrowest access that still lets them do their job, then widen deliberately.<\/td>\n<\/tr>\n
\n
Hide contact details by default<\/td>\n
Phone numbers and email addresses should be visible only to the people who actually contact clients.<\/td>\n<\/tr>\n
\n
Treat exports as a separate right<\/td>\n
Exporting the whole client list is a far bigger risk than opening one client card, so grant it rarely.<\/td>\n<\/tr>\n
\n
Limit how far back people can look<\/td>\n
Restricting access to past appointments and transactions cuts backdated edits and casual browsing.<\/td>\n<\/tr>\n
\n
Check the logs, not just the settings<\/td>\n
A log of exports and changes tells you who actually did what.<\/td>\n<\/tr>\n
\n
Altegio covers this in team member access rights<\/td>\n
Preset roles, per-section rights, hidden contacts, export rights and security logs are all set up per team member.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
What is role-based access, and how does it map to salon jobs?<\/h2>\n
Role-based access control (RBAC) means permissions attach to a job function, not a person. Give someone the junior stylist role and they get that role\u2019s access \u2013 no more, no less. It beats the old habit of copying an account and adjusting it by hand for each new hire, which is how salons end up with a receptionist who can delete last month\u2019s payments.<\/p>\n
The areas that matter in a salon break down cleanly:<\/p>\n
\n
Appointments and calendar<\/strong> \u2013 who can view, create, move or delete appointments, and whether that extends to colleagues\u2019 columns.<\/li>\n
Payments and discounts<\/strong> \u2013 who can take payment, change a service price or apply a discount at checkout.<\/li>\n
Finance<\/strong> \u2013 cash registers, transactions, payroll and supplier data.<\/li>\n
Inventory<\/strong> \u2013 stock levels, product arrivals and write-offs.<\/li>\n
Reports<\/strong> \u2013 revenue, team performance and appointment lists.<\/li>\n<\/ul>\n
Contact details deserve their own rule. Hide phone numbers and email addresses by default from junior and front-of-house roles that don\u2019t phone clients. Separate toggles, rather than one fixed role label, let you give access without giving control: a senior stylist might see a client\u2019s visit history but not their phone number. Card numbers are a different matter \u2013 they shouldn\u2019t sit in client notes or comments at all. Online card payments belong with a payment provider, and in Altegio they go through a connected provider such as Stripe or Adyen.<\/p>\n
How do you build permission templates that don\u2019t decay over time?<\/h2>\n
Templates only stay useful if you resist the urge to widen them \u201cjust in case\u201d. Every right you grant is one more thing to audit later, so start narrow and add only when a real task demands it.<\/p>\n
\n
Write a one-page role map.<\/strong> List each job \u2013 receptionist, senior stylist, junior stylist, manager, accountant \u2013 and the rights it needs. This page becomes the standard you check everyone against.<\/li>\n
Start everyone from a role, not from scratch.<\/strong> In Altegio, a team member\u2019s Access tab offers eight preset roles: Owner, Manager, Receptionist, Call Center, Accountant, Team member, Read-only and System Manager. Each comes with a preset set of rights, and you switch off the ones that person doesn\u2019t need.<\/li>\n
Copy rather than rebuild.<\/strong> Once one receptionist is set up exactly right, use Copy permissions to give the next receptionist the same rights. When your role map changes, recheck every team member in that job.<\/li>\n
Allow individual exceptions sparingly.<\/strong> A trusted senior team member might get a report their role lacks. Write the exception on the role map, don\u2019t just quietly toggle it.<\/li>\n
Put someone in charge of access.<\/strong> Name an access owner, usually the manager or owner, who reviews rights on a set schedule rather than whenever something goes wrong.<\/li>\n<\/ol>\n
Roles also affect your subscription. In Altegio, a team member is counted in the subscription if they provide services and have a work schedule, or if their role includes any editing rights. Read-only and System Manager are free roles for people who only view data or manage the team and subscription. The price itself depends on the number of team members and the billing period \u2013 see Altegio pricing<\/a>.<\/p>\n
![\"Diagram](\"https:\/\/alteg.io\/blog\/wp-content\/uploads\/2026\/08\/staff-permissions-salon-01.jpeg\")
<\/p>\n