Team, roles & permissions

Everyone gets a login. Not everyone sees your revenue.

The reason stores share one counter login is that per-seat pricing makes proper accounts expensive. Logins are unlimited here, so your Saturday consultant, your seamstress and your bookkeeper can each have their own — seeing exactly the part of the store that's theirs.

staff logins, on every plan
1 click
to remove someone who leaves
4
separate training switches per person
Team · Cande Bridal
4 people · 1 invite pending
Invite
AG
Adriana G.
owner · everything
active
JT
Jess T.
manager · no margins
active
SR
S. Reyes
seamstress · workroom only
active
NB
Nia B.
consultant · Saturdays
invite sent
BK
Bookkeeper
reports & exports only
active
The permission grid

Pick a person and see exactly what they can do

Roles are a starting point, not a cage — every switch can be set per person.

Owner — Adriana
9 of 9 permissions
Sell & take payment
Take deposits, balances and run checkout
allowed
See margin & cost price
Gown cost, margin and store revenue figures
allowed
Alterations workroom
Queue, seamstress assignment, fitting schedule
allowed
Place designer orders
Send purchase orders and change ship dates
allowed
Build or edit courses
Author courses, edit blocks, publish versions
allowed
Assign courses & chase progress
Give courses to people and see who is overdue
allowed
View training reports
Roster, matrix and the five report tabs
allowed
Export training evidence
One-file audit export of certificates and results
allowed
Financial reports & exports
Month end, deferred revenue and CSV exports
allowed
The owner role exists so there is always one account that can restore anyone else’s access. Everything it does is still named in the audit trail.
Joining

An invite, not a shared password

Generate a single-use invite link and send it to the person yourself; they click it and they're in, with no password to set or forget and exactly the access you chose. Six specific capabilities can be granted or revoked per individual — see reports, see payments, build courses, assign training, view training reports, export evidence — rather than one blunt role switch.

Onboarding courses →
Leaving

Removing someone doesn't lock out the store

Because accounts are personal, a departure is one click — and nobody else has to learn a new password. Their notes, sales and certificates stay attached to the record so your history stays intact.

The shared counter login is how a former employee still has access eight months later. That's the problem per-seat pricing quietly creates.
Accountability

Who changed the price, and when

Personal logins make the audit trail meaningful: discounts, voided payments, edited contracts and alterations pricing all carry a name. Not to police your team — so a dispute has an answer.

See the audit trail →
The question every owner asks

"Can I stop my Saturday staff seeing what the store makes?"

Yes. A consultant can take a deposit, book a fitting and read a bride's whole record without ever seeing margin, cost price, group revenue or another consultant's numbers. Reports and exports are separate switches again, so your bookkeeper can pull month end without touching the sales floor.

Multi-store groups get the same grid per location — a manager sees their own store, an owner sees all of them. Group permissions →

Why unlimited logins matter

Security you can't afford isn't security

Charge a boutique per seat and it will share one login — every time. Then permissions are theatre, the audit trail says nothing, and the person who left in March can still open the till screen. Making logins free is the cheapest security decision we could make for you, so we made it on every plan.

See pricing How others price seats

Bring your staff list to the demo

We'll set up the roles the way your store actually runs, in front of you, in about five minutes.

Book a demo Staff training