Accounts, users, and personas

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 exactly one persona.

Persona	Typical capabilities
Administrator	Full tenant administration: users, groups, events, rosters, products, bookings, payments, refunds, and account settings. Owners and teachers use it.
Attendee	Purchase eligible products, manage personal access, and manage their own bookings.

“Owner” and “teacher” describe a person's relationship to the business, not additional authorization personas. All administration is performed in the admin system. The attendee demo contains no administrative functionality. Authorization is enforced by the API; hiding a 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.