Role-based workspaces
Navigation and actions are controlled by school roles and permissions. Teachers work with their assignments; student and parent views focus on information relevant to them.
Access & review
School information.
Clear responsibilities.
Choosing school software includes checking who can access information, who can change it, and how work is reviewed before publication.
Product controls
Access follows the school role.
Review before release
Lesson plans and assessments use draft and review steps. Publishing content or releasing an assessment is separate from preparing a draft.
Defined school context
Academic years, classes, sections and subject assignments define the context for everyday tasks. Parent access is associated with linked children.
Before rollout
Review the deployment with your team.
Operational safeguards depend on the agreed deployment and service arrangement. Request the relevant details before importing school data.
Questions to discuss
- Hosting location, data residency and the providers involved
- Backup frequency, retention and restoration procedures
- Encryption, identity management and account recovery
- Logging, access reviews and incident response contacts
- Data export, retention and deletion responsibilities
- Any independent security assessment or certification required by your school
Reporting a security concern
Contact our team with a short description and the affected page. Do not include passwords, access tokens or student records in your initial message. Ask for a suitable channel before sharing sensitive evidence.
Contact the team →Read our privacy policy and terms for the published policies.
A conversation, then a plan
Have a school security checklist?
Share your requirements so we can discuss the deployment, evidence and responsibilities that your school needs to review.