Give every person a suitable role (admin or studio manager, office manager, front desk, instructor, contractor or temp), and follow two rules without exception: least privilege, and one unique login per staff member. Nobody gets more access than their tasks require, and nobody shares a password. Below you'll find a copyable permission mapping and a step-by-step rollout for your studio.
TL;DR:
- Keep refunds, pricing changes, payment settings, and financial exports with administrators or finance staff; require a second approver for major adjustments such as bulk credits.
- Instructors should take attendance, start their own livestreams, and view only their class rosters; front desk staff should register families and check students in.
- Give every staff member a unique account, require multifactor authentication for administrators and finance staff, and disable departing employees’ access immediately.
- Review permissions quarterly and after each hire, promotion, or departure; assign one access owner to remove outdated access and approve role changes.
- Give substitutes a temporary instructor account limited to the classes they cover, then disable it after their final class rather than sharing credentials.
Table of Contents
- What does each staff role need to access?
- Which permissions should each role get?
- How do you set up role-based access step by step?
- How do you protect student and payment data?
- What are the onboarding and offboarding rules?
- What should the settings look like in each studio tool?
- Why does a studio-built platform make this easier?
- Our take on the most common permission mistake
- How StudioFlare helps you put this into practice
- FAQ
- Sources
What does each staff role need to access?
Start from tasks, not job titles. Studio administrative work typically falls into three tiers: front desk, office manager, and studio manager, each with distinct duties. We add two more for software access, instructors and short-term contractors.
- Admin or studio manager: owns system settings, billing configuration, staff accounts, and financial reports.
- Office manager or operations: handles family accounts, schedules, and day-to-day messaging.
- Front desk or receptionist: checks students in, adds families, and answers parent questions.
- Instructor or teacher: takes attendance, starts class livestreams, and sees only their own rosters.
- Contractor or temporary staff: gets a narrow, time-limited slice of what the job needs, such as one event's check-in list.
Studio size changes how many of these you actually need. The same source notes that smaller studios often run a part-time front desk assistant, while larger ones bring in a salaried manager to supervise staff and finances. In a small studio, one person may hold both the office manager and front desk roles. That is fine, as long as the combined role still excludes billing settings.
Keep a few actions with one or two people only: changing payment settings, issuing refunds, and exporting financial reports. If a role doesn't need to do it weekly, it shouldn't be able to do it at all.
Which permissions should each role get?
Use these categories as a checklist when you build role templates in any studio system. "Full" means view and edit, "read" means view only, and "none" means the menu item shouldn't appear.
- System settings: admin full; everyone else none.
- Billing and payments: admin full; office manager read; front desk none; instructors none; contractors none.
- Refunds and pricing changes: admin only. Hand it to a bookkeeper if you have one, never to the front desk.
- Schedule and class editing: admin and office manager full; front desk read; instructors read for their own classes.
- Enrollment and registrations: admin, office manager, and front desk full; instructors read for their rosters.
- Attendance and check-in: front desk and instructors full; office manager full; contractors only for the event they cover.
- Livestream start, stop, and scheduling: instructors can start and stop their own streams; admin and office manager can schedule and override.
- Messaging and SMS: office manager and admin can send freely; instructors send from approved templates; front desk none or template only.
- Reporting and exports: admin full; office manager read for operational reports; everyone else none.
- Payroll and time clock: admin full; staff see only their own hours.
A quick example of the logic: your front desk handles check-in and registration all day, so they get both. Your instructors need attendance and the ability to start a stream, but a parent asking for a refund at the studio door goes to someone with billing authority, not to whoever is teaching.
Pro Tip: Build your roles by subtracting, not adding. Start every new template with no access, then grant only what a written task list requires.
If you also want to control who can change the calendar, our guide to three controls that stop double bookings shows how scheduling permissions prevent room conflicts.
Physical access matters too. The same logic applies to keys, back offices, and the room where the front desk computer sits, and this overview of access control types and a risk checklist is a useful complement for the building itself.
How do you set up role-based access step by step?
- Inventory your tasks. Write down what each person does daily, weekly, and monthly: opening the studio, checking students in, sending class reminders, running a recital sign-up. This list becomes the objective test for every permission, and it stops you from granting "full" access just because it's easier.
- Design role templates before creating accounts. Name them plainly (Front Desk, Instructor, Office Manager) and assign each permission category from the checklist above. Finish the templates first, so you aren't improvising when someone is waiting for a login.
- Create a unique account for every person and turn on MFA for admin-level users. No shared "studio" login, ever. Multi-factor authentication matters most for the accounts that can touch money and records.
- Pilot with one class or one shift. Have an instructor and a front desk employee work a normal day on the new setup. Ask what they couldn't do that they should have been able to, and what they could see that they shouldn't. Adjust the templates before rolling out studio-wide.
- Schedule reviews. Put regular checks on the calendar, and tie extra reviews to events: a new hire, a promotion, a departure, a new season. Name one person as the access owner so reviews don't depend on whoever remembers.
Registration is where many studios stumble first, so pair this rollout with our guides to online dance registration and registration forms and policies to decide who can add or edit family data.
How do you protect student and payment data?
Least privilege means each person holds only the access their current job needs. Industry guidance on role-based access, unique logins, and regular permission reviews exists to prevent privilege creep, where people collect access over the years as their duties change.
Reviews matter because duties change: the guidance says to regularly review and remove old role assignments when staff change roles or leave. That habit can help bring the access people have closer to the access they need.
Shared credentials are the other big risk. When multiple people use one admin login, you can't tell who issued a refund or changed a rate, and you can't remove one person without resetting everyone. Unique logins give you a record of who did what.
For administrators and anyone handling finances, require MFA. CISA's guidance for small and mid-sized businesses recommends requiring MFA when possible and managing authentication and authorization carefully. It also says to restrict vendor and service-provider accounts and to review the connections between your systems and theirs, so treat your software vendor's access like a staff account: limited and reviewed. Finally, keep a recovery path, such as a second admin and a documented backup process, so a lost phone doesn't lock you out of your own studio.
What are the onboarding and offboarding rules?
Access management only works if adding and removing people follows the same steps every time.
Onboarding checklist:
- Create a unique account in the person's name.
- Assign the right role template, not a custom one-off.
- Train them on handling student and family data.
- Enroll them in MFA before first login if their role calls for it.
Offboarding checklist:
- Disable the login as soon as you know they are leaving.
- Revoke any API keys or connected app access they held.
- Change any shared credentials that existed, such as a Wi-Fi or social media password.
- Reassign their scheduled classes and livestreams so nothing breaks.
Review all accounts regularly or whenever staff change, and name one access owner who signs off.
Pro Tip: Add "disable account" to the same checklist you use to collect keys and studio property. If it's on the departure list, it happens.
What should the settings look like in each studio tool?
These presets give you sensible defaults for the features you touch every day.
- Registration and enrollment: front desk and office manager can add families and update contact details. Only admin or finance can change payment methods or issue refunds.
- Billing and payments: limit refunds and pricing changes to admin or finance. For major adjustments, such as a bulk credit, require a second person to approve. Our guide on collecting dance studio payments online covers the billing side in depth.
- Attendance and check-in: front desk and instructors can mark attendance. Reporting exports stay restricted to admin.
- Livestreaming: instructors can start, stop, and publish their own class streams. A manager keeps the override for scheduling and for fixing a stream that went to the wrong audience.
- Messaging: instructors send from templates only, like "class canceled" or "costume reminder." Free-form sends to all families belong to the office manager or admin.
Why does a studio-built platform make this easier?
Generic business software forces workarounds: a shared login here, a spreadsheet there. We built StudioFlare for dance studios, so the pieces you're assigning permissions to (registration, attendance, livestreaming, tuition billing through Stripe) live in one system. Before you deploy anything, map the platform's features against the permission checklist above and note any gap. A platform that fits the checklist saves you from inventing exceptions later.
Our take on the most common permission mistake
A common mistake is the shared admin login. A studio hands the owner's password to a front desk hire "just to get started," and months later nobody can say who issued a refund or why a class vanished from the schedule. Untangling it means resetting every credential and rebuilding trust with staff. This week, create a unique admin account and a unique instructor account for each person who needs one, then retire the shared one.
— StudioFlare Team
How StudioFlare helps you put this into practice
If you'd rather configure this once than build it from scratch, we've set up StudioFlare around the same principles. You get a studio-focused system where roles, class registration, and livestreaming work together.
- Built-in livestreaming tied to class registration and access control
- Automated tuition billing through Stripe
- Month-to-month pricing with no setup fee or contract: the Starter plan is $29 per month, the Pro plan is $49 per month, and each active student adds $1 per month
You can see how it all fits in our feature overview, then create your studio. Set up a front desk template and an instructor template first, and test them on one real class.
FAQ
What level of access should dance instructors have?
Instructors should be able to take attendance for their own classes and start their own livestreams. They shouldn't see billing, refunds, or financial exports. Keep their view limited to the rosters they teach.
Should front desk staff be able to issue refunds?
No. Front desk staff handle check-in and registration, so refund and pricing authority should stay with admin or finance. If a parent asks for a refund, the front desk escalates it. This keeps one accountable person behind every money decision.
How often should we review staff permissions?
Review them quarterly, and again whenever someone is hired, promoted, or leaves. Regular reviews and removal of old role assignments keep access aligned with current duties. Assign one access owner so it actually gets done.
How do you give a substitute teacher access safely?
Create a temporary account with the instructor template, limited to the classes they cover. Add an end date if your system allows it, or disable the login right after the last class. Never lend them your own credentials.
Sources
- Fortinet
- CISA Insights: Mitigations and Hardening Guidance for MSPs and Small- and Mid-sized Businesses
- Hiring Studio Administrator: Roles & Responsibilities 2026