Confidence in everyday decisions

Protect student records. Review important decisions.

Families trust you with their information. Staff need the right permissions, important changes need an explanation, and problems need someone responsible for resolving them. BCO connects staff access, approval history and human review to everyday administration.

Open security checklist Explore the guided workflows

School-controlled access Sign-in Permissions Change history Recovery Know who can act and what changed

Reviewed 29 October 2026Access and decision controlsSupport terms agreed in writing

Staff accessGive each person access to the records and tasks their role permits.

Approval historyReview who approved an important change and why.

SupportKnow whom to contact and how to raise an unresolved issue.

Protection where the work happens

Give staff the right access. Keep important changes reviewable.

Staff should see only the records they are permitted to use. Important changes need the required approval and a clear explanation afterwards.

Control who sees student information

A school-group report must not give unrestricted access to every student's information. Institution access rules and staff permissions apply to records, files and reports, with the software checking each request—not just hiding menu options.

Separate institution records
Group reports limited to the authorised purpose
Controlled access to files and downloads

Responsibility without shared passwords

Give staff the permissions their work requires. Distinguish requesting a change from approving it, so assigning a task does not silently grant authority to approve the result.

Named staff, appropriate permissions

See why a record changed

A fee correction or sensitive record change needs more than a new value. Review who made the change, when, why and the result in the relevant history, with approval where the process requires it.

A reviewable decision history

AI supports staff judgement

Indicators that a student may need attention and suggested actions are limited by staff permissions. Authorised people review the relevant records and make sensitive decisions, including decisions about student support.

Your team retains the decision

Control messages and staff follow-up

Follow-up settings chosen by your institution use approved channels, consent and contact-hour rules. Staff review replies or uncertain delivery instead of sending blind repeat messages. Provider connections and the approval to send live messages are agreed for your implementation.

Controlled sending, clear staff responsibility

Know what to do when a problem occurs

Your implementation and service agreement identify the support contact, how to raise unresolved issues, backup responsibilities and recovery arrangements. Before going live, confirm the backup and restoration checks, support hours, how long records are retained, and the service availability, response and recovery terms agreed for your institution.

A known contact for support and unresolved issues
Named backup responsibilities and restoration checks
Service commitments recorded in your order

Check an example with us

Follow an admission or fee decision.

Choose a fee correction, admission decision or student-support action. Use sample or approved test records to see who can act, what requires approval, how the decision is recorded and who takes responsibility if a problem occurs.

1
Start with your situation
Choose the people, campus and result that matter to your team.
2
Check staff permissions
Follow who can request, approve, apply, reverse or view the action.
3
Read the history
Inspect the reason, responsible person, timing and recorded result.
4
Know whom to contact
Agree who handles problems, the support contact and each team's responsibilities.

Have a security, privacy or administration question?

Describe the process or issue without personal records. Never email credentials, child-level data or confidential incident evidence.

Contact the trust team Read the school buying guide