Many systems ask one question when someone tries to book: did this person buy the thing that grants access? That works for a simple customer relationship. It breaks down when the same person is also a teacher, facilitator, staff member, work-study student, or community leader. In studios, roles and prices are often both true at the same time.
Sangha separates those ideas so they can cooperate. A teacher might receive regular class access through a studio-scoped role, while a workshop still uses pricing logic. The teacher could receive 20% savings on workshops because of a policy, without turning every workshop into a free teacher benefit or selling them a fake zero-dollar membership. The relationship is specific instead of blunt.
This is important because role-based access and pricing-based access answer different questions. Role-based access asks who this person is in the studio. Pricing-based access asks what this offering costs for this person under the current rules. When those questions are collapsed, teams end up with brittle workarounds and unclear expectations.
The student experience gets better too. People do not have to ask whether the system remembered them correctly, and staff do not have to manually override the same edge cases every week. The booking flow can show what is available, what is discounted, and what still requires payment with less social friction.
The deeper innovation is that access becomes relational and auditable. Sangha can honor the reciprocal roles people actually hold while preserving the pricing integrity of workshops, events, and paid offerings. That gives studios more nuance without asking the front desk to carry all of it by memory or compromising the revenue a studio needs to stay alive.
