Children's records hold some of the most sensitive information your church keeps: allergies, medical notes, behavioural notes, and a log of who collected whom. Knowing who can see it is part of running the ministry properly — and it's a question safeguarding leads and data-protection officers ask.
Who this is for
Church administrators, safeguarding leads, and anyone responsible for deciding which volunteers get access.
The short version
Access is decided by the role a person holds. Four roles reach children's information:
| Role | What they can do |
|---|---|
| Super Admin | Everything, including check-out overrides |
| Admin | Everything, including check-out overrides |
| Children | Day-to-day children's ministry work — rosters, check-in, check-out with a code |
| Everyone else | No access |
A member with no relevant role sees no children's data at all. The Children menu isn't there for them.
What this means in practice
Give volunteers the Children role, not Admin. The Children role covers everything a volunteer needs on a Sunday: seeing their roster, checking children in and out, reading allergies and pickup notes. It does not let them override a check-out, which is the one action that should require a staff member.
Handing out Admin to save a conversation is how a volunteer ends up able to release any child without a code — and able to see finance, giving, and every member record besides.
Only Children-role members and above can be made teachers. The teacher list is drawn from members holding Children, Admin, or Super Admin, which means classroom assignment can't accidentally hand access to someone who has none.
Your church's data stays your church's data
Churchease is used by many churches on the same platform, and children's records are scoped to the church that entered them. No other church can see your children, your classrooms, your allergy notes, or your check-out history — regardless of role. An Admin at another church has no more access to your records than a stranger does.
What's recorded about access
Check-outs are logged: who released each child, when, and — for staff overrides — the reason given. Failed check-out attempts are logged too, though the code someone typed is never stored.
You can review this at Children → Checkout History. It's the evidence trail you'd need after an incident, and it's worth knowing it exists before you need it.
Reviewing who has access
Go to People, filter by role, and look at everyone holding the Children, Admin, or Super Admin role. Ask of each: does this person still serve here?
Volunteers move on, and a role nobody removed is a quiet access problem. Reviewing at the start of each term takes ten minutes.
Removing a role takes effect immediately.
A limit worth understanding
Roles control who can reach children's information. They don't distinguish between classrooms — a volunteer with the Children role can see the whole children's ministry, not only the room they teach in.
If that matters to your church, the control is the role itself: give it only to people you're content to have see every child's record.
Related articles
- How do I make someone a teacher?
- Checking children in and out on a Sunday
- Getting started with children's ministry