Accounts, users, and roles
Top-level accounts
A top-level account is the tenant boundary for a studio, independent teacher, or event business. It owns groups, events, event instances, products, payment configuration, entitlements, and bookings.
The authenticated session selects exactly one account. Consuming systems must not add an account ID to protected requests; the API derives it from that session and filters tenant-owned data accordingly.
Users and participation
A user is any person using the system. A membership connects that user to an account and assigns one or more roles.
| Role | Typical capabilities |
|---|---|
| Owner | Full administration and payment connection setup |
| Administrator | Groups, events, products, bookings, and refunds |
| Teacher | Event and instance administration plus operational booking visibility |
| Attendee | Purchase eligible products and manage their own bookings |
Authorization is enforced by the API; hiding an admin control in a client is not a security boundary.
Groups
Groups organize attendees for restricted events—for example, members, beginners, or teacher-training participants. An event instance can be open to everyone, restricted to one or more groups, or not bookable.