Role-Based Access for Dance Studios
Role-based access designed for studios: owners, admins, teachers, and parents each see only their scope, with teacher-class and parent-child permissions.
Role-based access in Dance Solutions is designed so owners, admins, teachers, and parents each see only their scope, with teacher-class and parent-child permissions limiting access to what each person needs.
How it works
- Assign a role: Pick owner, admin, teacher, or parent for each person.
- Scope teachers: Connect teachers to the classes they actually teach.
- Scope parents: Link parents to their own children only.
- Review access: Check who can see what and adjust roles as staff change.
Frequently asked questions
What roles does the design include?
The core roles are owner, admin, teacher, and parent. Each is designed with a defined scope, and permissions follow studio relationships like a teacher's classes or a parent's children.
Can a teacher see the whole studio?
No. Teacher-class permissions are designed to limit teachers to the classes they actually teach, not the studio's full enrollment, payments, or private notes.
How are parents kept from seeing other families?
Parent-child permissions are designed to scope each parent to their own children, so the portal never exposes another family's details.
Is role-based access live in this version?
No. This is a prototype preview on sample data. The roles and permissions shown are the intended access architecture rather than a live, enforced system.
Can I explore the role views without an account?
Yes. The free Recital Readiness Check runs on sample data without an account, and the demo illustrates how each role's view differs.