Team & roles
Add your staff — with a login, or without one — and use roles to control exactly what every person who does sign in can see and do.
Two settings run side by side. Team is the people; Roles is their permissions. You invite a person to your team and give them a role — and the role decides what they see in the app and what they're allowed to do. Change the role, and everyone who holds it changes with it.
Team
Open Settings → Team and press Invite member. The first thing the form asks is Access, right above the email box — Decide this first — it changes what the rest of the form needs.
- Can log in — We email them an invitation. Email required. They set their own password on first sign-in and never touch yours. Until they accept, they show as Pending and you can resend the invite.
- No login — On the calendar and the booking page, but never signs in. No email needed. Use it for the stylist who just needs to be bookable. They still get a full profile and their own calendar column; the team list marks them No login, and Grant access gives them a login later without turning them into a second person.
Then pick their Role and the branches they work at on the Access step, and set their booking, schedule and days off. Later you can move someone between branches, Disable them for a season, or Remove from team them entirely — which revokes their access immediately.
Owners always reach every branch, so they need no branch selection. Managers and custom roles only see the branches you tick.
Roles
Open Settings → Roles. A role bundles two things: which permissions a person has, and which sections of the app appear in their sidebar. Gloora ships three you can't delete — Owner, Manager, and Staff — and lets you build your own.
Press Add custom role to create one. The editor has two halves: Identity for its name and base role, and Permissions where you switch on exactly what it can do — grouped into Pages (what shows in the nav), Bookings, Money, Clients, Team, and more. Want a role close to a system one? Duplicate it and adjust the copy.
The base role is a ceiling, not a starting point
Every custom role picks a Base role (privilege ceiling) — and that base caps how far its permissions can reach. Switch on a high-trust permission above the ceiling and it stays locked, no matter what you toggle. So a role built on Staff can never quietly gain owner-level money access. Set the ceiling first, then grant within it.
The owner is the exception to all of this: owners bypass every permission check and see everything, which is why the Owner role is locked and can't be edited. When you want a tailored set, build a custom role instead.