All featuresAround the school
Several schools, without mixing their data
Each business has its domain, its identity and its account — the same tool underneath.
In short
- A school is recognised by its domain: clients, instructors, activities and spots belong to it.
- Each school collects on its own Stripe account.
- Modules — waivers, equipment, tides, waiting list, email campaigns, support — are enabled school by school.
Separation is not a display filter
Two schools on the same tool share neither clients, nor sessions, nor invoices. Ownership is carried by the data itself, not by a filter someone could forget to apply.
Each keeps its identity: name, logo, cover image, description, and the address its emails are sent from.
What is set per school
- The Stripe account that receives the money
- Activities, spots and instructors
- The enabled modules
- Booking, cancellation and invoicing settings
At a glance
- Recognition
- by domain
- Collection
- one Stripe account per school
- Modules
- enabled independently, school by school
Frequently asked
Can one school see another's clients?
No. Ownership is carried by the data, and every query is bounded to the school making it.
Can a multi-site group steer everything from one place?
Yes, a dedicated console lists the businesses and their configuration.