Permissions and roles

A role is a set of permissions. Each permission is an all-or-nothing grant over one area of the admin — there’s no separate “view” versus “edit” split. Turn a permission on for a role and everyone with that role can use that whole area; turn it off and the area disappears for them.

You manage roles and their permissions in Settings → Roles & Permissions — visible to anyone with the Roles & Access permission.

The permissions

Each permission is a job: grant it to the people who do that work all day. The two with the longest reach — Subscription & Billing (spends your money) and Roles & Access (decides everyone else’s permissions) — are granted to nobody but the admin role until you say otherwise.

Permission	What it unlocks
Appointments	The front desk: view, create, and manage all appointments, and take payment at checkout — including applying coupon codes and selling or redeeming gift cards. A stylist without this permission still sees their own appointments.
Refund Overrides	Deviate from your cancellation and no-show policies for one appointment — refund more or less, or keep a different amount. A reason is always required and recorded. Marking a no-show that simply follows your policy needs only the Appointments permission. Only available on plans with Deposits & No-Show Protection.
Pricing Overrides	Change the service or add-ons on an existing appointment, and add paid add-ons mid-visit. A reason is required when the change reprices the appointment.
Scheduling Overrides	Book past scheduling rules: beyond the booking window customers can normally book, and before a stylist’s start date. Each override is confirmed per slot and recorded.
Customers	Client records: profiles, notes, visit history and tags, importing a client list, and — on plans with them — building intake forms and waivers and reading signed responses. Signed forms can include health information, so grant this accordingly.
Catalog	Manage what you sell: services, categories, collections, and add-ons, plus packages on plans that include them.
Marketing & Growth	Grow the business: email campaigns and win-back, discount codes, the gift card programme, the loyalty programme and its rewards, and booking-page traffic — including which of your clients visited without booking, with their contact details. Campaigns go to every opted-in client, so this permission can email your whole list.
Financials	The bookkeeping page and its transaction history, plus — on plans that include them — the dashboard financial cards, analytics, invoice settings, and correcting gift card balances or refunding gift card purchases.
Subscription & Billing	Your JustBook subscription: change the plan, update the payment method, and buy add-ons, message credits, and extra storage. This permission spends the business’s money.
Team	Manage the team — stylists and user accounts. Deciding what each role can do is separate: that’s Roles & Access.
Roles & Access	Decide who can do what: edit roles and their permissions, grant override permissions to individuals, and revoke anyone’s override codes. Someone with this permission can grant any other permission — treat it like the admin role.
Settings	Business configuration: business info, branding, branches, the Customer Journey and Booking Policies tabs, reminders and notifications, tags and statuses, and data export — plus integrations and invoice configuration on plans that include them.
System Logs	The Logs page — business activity, notification deliveries, payment events, reminder history, and override usage.

Descriptions in your admin are trimmed to your plan: a permission never lists a screen your plan doesn’t include, so what you see may be shorter than the table above. See Plans and billing.

For the complete grid of which built-in role has which permission, see the permissions matrix.

Override permissions: per person, not just per role

The three override permissions can also be granted to an individual team member on top of their role — open their profile under Team and use the Override Permissions card. A grant adds to what the role gives; it never takes anything away. If a permission shows as Included in their role, it comes from the role and is managed in the roles grid instead.

Override codes: a one-time yes

Sometimes someone without an override permission needs to make one exception — a refund adjustment while the manager is off-site, a booking before a new stylist’s start date. Instead of granting a standing permission, a manager who holds the permission can issue an override code from My Profile → Override Codes:

Choose what the code allows — one kind of override, or All overrides if you’d rather not pick (you can only issue what you hold yourself).
Choose how many uses it has and how long it lasts. The default is a single use that expires in 7 days. You can also turn on Unlimited uses or Never expires — handy for a trusted front desk, but that turns the code into a standing PIN: anyone who learns it can keep using it until you revoke it.
Share the 8-character code. You can view or copy it again any time from your Override Codes list — each time you view it there, that’s recorded too.
The team member enters it right where they’re blocked (the no-show or cancellation dialog, the edit-appointment page, Add to visit, or the booking calendar). A reason is still required and recorded.

Your codes are yours alone. They live on your own profile, not in Settings, because a code carries your authority — it lets someone else do something because you said they could. Nobody else can see or copy a code you issued, not even an owner. The card only appears if you actually hold an override permission to delegate.

Options you don’t have are never offered: a permission your plan doesn’t include (Refund Overrides without Deposits & No-Show Protection) doesn’t appear in the roles grid or as a code option.

Keeping an eye on codes

Anyone with the Logs permission can open Logs → Overrides to see the full picture: every time a code was issued, used, viewed, or revoked, who used it, and whose authority they were borrowing. It shows the record of what codes were used for — never the codes themselves.

You can revoke your own codes from your profile at any time. Owners and admins (anyone with the Roles & Access permission) can also revoke anyone’s code from Logs → Overrides — useful when someone leaves and their standing code needs to be shut off. Revoking never reveals the code.

Each appointment’s Overrides card (on the appointment page) lists every override ever applied to it — what was changed, when, the reason, and both who made the change and whose authority allowed it. If someone used a code, it names the person who issued that code, so “who approved this?” always has an answer.

How roles work

Every team member has exactly one role. The role’s permissions decide what they can reach.
Built-in roles are admin, manager, receptionist, and stylist. Their names are fixed, but you can adjust which permissions each one grants (except admin, which always has full access).
Custom roles — create your own role with a tailored permission set in Settings → Roles & Permissions, then assign it when you add or edit a team member. Custom roles are included in every plan.

Shared reference data isn’t gated

Some information is open to any signed-in team member regardless of their permissions, because everyday work needs it — the service menu, the list of stylists, branches, appointment statuses, and availability. Seeing what exists is always allowed; only changing it, and viewing sensitive data (financials, customer details, logs), is gated by the permissions above. This is why a receptionist without the Appointments permission can still open the Calendar and see who’s working.

Permissions vs. your plan

A permission answers “is this person allowed?” A separate question is “does your plan include this feature?” — loyalty, packages, and invoicing are unlocked by your subscription, not by a role. If a feature is missing for everyone, it’s a plan question, not a permissions one. (Roles and permissions themselves are included in every plan.)