Most studio software treats access as a payment problem first. If someone paid for a membership, bought a pass, or booked a drop-in, the answer is simple. But real studios are rarely that simple. A person might be a teacher, a work-study student, a facilitator, a founding member, or a community volunteer before they are ever a line item.
Sangha starts from the person and the studio relationship. One human has one profile, and the system can understand that their access may come from more than one source. A teacher can attend class because of their role, save on workshops because of a pricing policy, and still pay normally for something outside those benefits. That honors the reciprocal and role-based nature of the community while preserving the financial clarity that sustains it.
This matters because access decisions shape trust. When the front desk has to remember a special case, the person receiving access can feel like a problem to be explained. When the rule is part of the system, the exchange becomes clear, respectful, and repeatable. The studio can be generous without becoming disorganized.
A whole-studio access model also reduces the hidden administrative work that builds up around side spreadsheets and fake products. Complimentary access, role perks, workshop savings, class passes, and policy exceptions can all point to the same source of truth. The team can see why access was granted instead of reverse-engineering it from a note in an old account or a made-up teacher membership.
The point is not to make studio life rigid. The point is to make the real flexibility of studio life visible. Sangha is built for the mixed economy that already exists inside community-centered studios, where payment, service, teaching, and belonging often overlap.
