All press

Engineering

Building multi-tenant studios without the ceremony

A short engineering note on how we model studios, staff, and permissions — and the choices we made to keep the surface area small without painting ourselves into a corner.

ET

Engineering team

StyleMatch

14 March 20267 min read

A studio in StyleMatch is a multi-tenant unit: it has an owner, a roster of staff with different role permissions, and any number of locations and services hanging off it. Underneath, we wanted to keep the modelling boring and the surface area small.

Three ideas, no more

  • Studio — the tenant. Owns everything that follows.
  • StudioMember — the join between a User and a Studio, with a StudioRole.
  • StudioRole — a named bag of permissions drawn from a fixed catalog.

The catalog is small on purpose. New permissions are an explicit decision, not a throwaway flag. Routes that need a permission go through one guard; the guard checks the active StudioMember's role and either lets the request through or returns 403.

The Super Admin — the studio owner — is a member like everyone else, with the special property of being un-suspendable and un-deletable through the staff surface. That rule lives at the schema level, so the UI can simply hide the menu items.

Want to be part of the next chapter?

Set up your studio in minutes — keep your bookings, customers, and team in one calm workspace.

List your business