This documentation is for busy studio owners and admin staff running live classes, not for software developers. It explains how Classia works in practical terms: what to set up first, what to check before publishing, and what causes support-heavy weeks. Most examples are written for UK studios running term-based classes with mixed child and adult enrolments. If tomorrow’s admin list looks long, start with the section that matches the problem in front of you.
If tonight is triage night
Pick the next page by what is currently blocking you:
- New account and first setup: Getting started
- Term and timetable build: Term planning and class setup
- Request queue decisions: Enrolments and status management
- Parent-facing pages and requests: Public pages and enrolment requests
- Payment setup or arrears pressure: Payments and billing (UK)
- Register problems: Attendance and registers
- Access confusion: Parents, participants, and roles
- AI assistant connection: Connect an AI assistant to Classia
- Something has gone wrong: Troubleshooting
Do one guide at a time. Do not jump between four pages and change settings in parallel.
What this hub is designed to do
It is designed to help you run a full term with fewer avoidable corrections. In practice, that means:
- Clear setup order before launch.
- Clear request decisions during busy weeks.
- Clear payment language families can understand.
- Clear safeguarding boundaries when children are involved.
It is not designed to impress. It is designed to keep your week workable.
Three real studio snapshots
1. Dance school with 12 weekly classes and 85 pupils
The owner sets up Autumn term first, then publishes six classes, not all 12. She reviews request quality for two days before publishing the rest. That staged launch avoids a Friday-night approval backlog.
2. Martial arts club with children and adults in the same venue
The club runs separate class groups for ages 7-11, 12-15, and adults. They train staff to check parent details before approving under-18 requests. They keep one daily queue owner so decisions stay consistent.
3. Tuition centre moving from spreadsheets mid-year
They migrate current-term classes and active learners first. Old rows stay in spreadsheets for reference. After one month, they import history in batches. They avoid importing three years of mixed records on day one.
Safeguarding note
Where children are involved, speed is rarely the right priority. Confirm guardian details, role access, and public visibility controls before pushing through a queue. A short delay is manageable. A safeguarding correction is usually messy, stressful, and public.
Related guides
- Getting started
- First 30 minutes
- Set up your first term
- Connect an AI assistant to Classia
- Public enrolment step by step
- Approve, reject, waitlist, and match resolution
- Schedules, due items, arrears, and offline payments
Related feature
FAQ
Where should a new admin team start tomorrow morning?
Start with First 30 minutes, then move to Set up your first term.
Which guide helps with parent-facing pages?
Use Public pages and enrolment requests.
Where are UK payment terms explained clearly?
Use Payments and billing (UK) and the glossary payment terms page.
Is there guidance for under-18 enrolment handling?
Yes. Use the trust and safeguarding section, and the public enrolment guides.
When should we use troubleshooting pages?
After checking the expected process guide, not before.
Can this replace all team handover notes?
No. Keep short handover notes. Use these guides as the base standard.