Open this guide when you are still doing admin late and need records that hold up under pressure. It covers how Classia connects participants, families, adults, and user roles, so the right person can take the right action without guesswork. You will also see where safeguarding checks are strict by design, especially for children and public-facing enrolments. The aim is fewer corrections in week three, fewer payment disputes in week six, and fewer awkward parent emails after class.
A real Tuesday evening in a small studio
Two classes have just finished and parent questions are arriving. One parent asks why she cannot see her child’s payment plan in the portal. Another asks why her daughter is marked active in one class and trial in another. A teacher covering Saturday asks whether he should change participant details himself.
That is the exact point where this section matters. Not in theory, but in the small, repeated decisions that either keep your term calm or create backlog.
In Classia, those decisions depend on a few connected records:
- Participant record (stored in the participant profile used by the app, shown as Participant in the app).
- Adult record (usually parent or guardian contact).
- Family record (household link between adults and participants).
- Enrolment record (status, dates, responsible adult where required).
- User account role (admin, teacher, parent, participant role shown as
dancerin current UI).
When these links are clean, day-to-day operations stay predictable. When one link is wrong, it often shows up somewhere else first: a failed approval, a portal access complaint, or attendance that does not match payment expectations.
How these records fit together in plain language
Think of the account as the outer boundary. Everything in this guide lives inside one account, and policies enforce that boundary.
Inside the account:
- Participants can belong to one or more families.
- Adults can belong to one or more families.
- Families hold the household relationship between adults and participants.
- Enrolments attach participants to classes, with status and dates.
- For under-18 participants, enrolments require a responsible adult.
That responsible adult is not just a free text contact. Classia validates it:
- The adult must be in the same account.
- The adult cannot be archived.
- The adult must belong to at least one of the participant’s families.
These checks are strict for a reason. If a child’s enrolment is attached to the wrong adult, safeguarding and payment conversations quickly become unsafe and confusing.
Role boundaries that reduce accidental edits
Classia supports account roles admin, teacher, parent, and dancer (participant role label). Role links control what people can see and do.
In practice, studio owners get the most stable results when role boundaries are clear:
- Admins run setup, approvals, corrections, and access decisions.
- Teachers focus on teaching and class-level information.
- Parents and participants use portal views tied to their own details.
A common friction point is trying to solve staff scheduling pressure by giving broad admin access to everyone. It feels faster for a week, then slows the whole term because too many people can change core records.
Suggested setup sequence for a new term
Most studios do better with a sequence than a checklist pasted in chat. This order is reliable for mixed-age programmes.
- Set up or review family records.
- Add or tidy adult records (email and phone especially).
- Add or tidy participant records (date of birth and family links especially).
- Create or confirm enrolments and responsible adult links.
- Review user access in Settings users.
- Verify parent and participant portal access after approvals.
A UK dance school running 12 weekly classes with 85 participants can usually complete this in two focused admin sessions before term starts. The same school often spends double that time if it starts from enrolments and patches family links later.
Examples
Example: Siblings in multiple classes
A Manchester dance school has two siblings aged 6 and 9 in ballet and acro. One parent pays by card monthly; the other guardian handles attendance messages. The studio links both adults to one family record, both children to that family, and assigns the paying adult as responsible adult where needed.
The right person sees payment information, and staff do not need to manually explain the same balance to two contacts each week.
Example: Adult participant and child participant share one surname
A martial arts school has a 32-year-old beginner and his 11-year-old daughter in separate classes. The adult participant can use the participant portal role (dancer label in current UI) tied to his own enrolment details. The child’s enrolment still needs a responsible adult link.
No confusion between self-managed adult enrolment and under-18 safeguarding requirements.
Example: Staff turnover mid-term
A swim school has 14 classes and loses one admin in week four. The owner removes the user from Settings users, resends one pending invite to a replacement, and verifies there are still at least two active admins.
Access remains controlled, and no one shares passwords during the handover.
Safeguarding checks that belong in normal admin
Safeguarding is not a separate annual task. It is present in regular data decisions.
For this section, safeguarding-critical moments are:
- Linking children to families.
- Selecting responsible adults on under-18 enrolments.
- Deciding who gets portal access.
- Deciding what team members can edit.
If any of those are uncertain, pause and resolve before moving on. A delayed class update is easier to recover than an unsafe access decision.
Where pressure usually builds in week one
Week one pressure usually comes from three places:
- New enquiries arriving while term setup is still unfinished.
- Parents asking for portal help during class changeover.
- Staff requesting urgent access five minutes before teaching.
The fix is not a longer handbook. It is short, repeatable checks:
- Review minors without responsible adults.
- Review pending invites and invite expiry.
- Review recently approved enrolment requests and portal provisioning.
Keep this as a 20-minute weekly slot and your backlog stays small.
Signs this section is healthy
You can tell these pages are working when:
- Parents ask fewer "who can see this" questions.
- Staff know who owns access decisions.
- Enrolment approvals need fewer follow-up corrections.
- Portal payment visibility issues are resolved in minutes, not days.
These are small signals, but they stack up across a full term.
What this is not designed for
This section is not designed for shared household logins, anonymous guardian records, or unrestricted staff access. If your studio currently depends on those habits, move in steps and assign one person to own the change.
Related guides
- Participants, families, and responsible adults
- Team access and account invites
- Parent and participant portal access
- Enrolments and status management
- Public pages and enrolment requests
- Trust, verification, and safeguarding
Related feature
FAQ
What records matter most in this section?
Participant, adult, family, enrolment, and user-account role records drive who can see data and who is responsible for each enrolment.
Can staff invites create teacher or parent access from Settings users?
The Settings users invite flow sends admin invites. Parent and participant portal invites are provisioned from relationship-based invite flows.
When is a responsible adult mandatory?
For participants under 18, enrolments require a responsible adult from the same account and linked family, and that adult cannot be archived.
How do portal permissions stay scoped?
Portal access is scoped by account and role link, so parent and participant users only see details tied to their payer or participant relationship.
What if we are moving from spreadsheets?
Map households first, then adults and participants, then enrolments and portal access, so payer and safeguarding links are correct from day one.
What is the quickest weekly health check?
Review pending invites, recently approved enrolment requests, and minors missing responsible-adult links before classes start each week.