- Secure Access
- Role-Scoped Permissions
- Audit History
- Encryption
- Backups
- Sensitive Data Boundaries
- A class teacher may need teaching information.
- A SENCO may need additional SEND information.
- A DSL may need access to restricted safeguarding records.
- An HR user may need confidential workforce information.
- A parent or carer may need approved information about their own child.
- An external professional may need limited access for a specific learner and purpose.
- EdiWay is designed to keep those differences meaningful.
Organisation
Which school is the user working within?
Role
What responsibility do they hold?
Learner
Which learner is involved?
Class
Does the user have an appropriate teaching relationship?
Family Relationship
Which parent or carer relationship is recorded?
Professional Relationship
Why does an authorised professional require access?
Information Domain
Is the information teaching, attendance, SEND, safeguarding, medical, HR or another controlled area?
Action
Is the user allowed to view, edit, export, approve or share?
This helps schools move beyond an all-or-nothing model of access.
- Learners
- Staff
- Classes
- Timetables
- Attendance
- Behaviour
- Assessment
- SEND
- Safeguarding
- Medical records
- HR
- Operations
- Marketplace activity
Where wider organisational or trust oversight is enabled, access still needs to be explicitly governed.
Being able to oversee more than one school should not automatically provide unrestricted learner-level access across them.
Secure Login
Authenticate users before allowing access.
Additional Login Protection
Support stronger authentication controls, including two-factor authentication capability.
User Accounts
Maintain distinct staff, learner and family identities.
External Accounts
Support controlled professional access where enabled.
Temporary Access
Allow limited access models where appropriate.
Expiry
End access when a temporary or professional relationship should no longer remain active.
Authentication establishes who the user is. Permissions determine what that user is allowed to do.
Safeguarding
Restricted safeguarding records remain inside the dedicated safeguarding workflow.
SEND
Support information is available according to appropriate educational responsibility.
Medical and Care
Sensitive learner health and care information remains within its own access boundary.
HR
Employment information remains separate from ordinary school operational access.
Professional Casework
External collaboration remains limited to authorised learner-specific relationships.
Family Information
Parents and carers receive information appropriate to their relationship and permissions.
Connecting these workflows does not remove their boundaries.
- A teacher's ability to view a learner does not automatically provide access to that learner's safeguarding record.
- A general administrator should not automatically receive DSL-level access.
- A parent or carer account should not expose internal safeguarding records.
- A trust overview should not automatically open individual safeguarding cases.
User
Who completed the action?
Record
What information was affected?
Action
What happened?
Time
When did it happen?
Workflow
Which area of EdiWay was involved?
History
What relevant earlier activity remains available?
Sensitive workflows may maintain additional specialist history within their own records. Audit information helps provide accountability without becoming a substitute for good school governance.
- Authentication
- Permissions
- School scoping
- Audit history
- Controlled exports
- Sensitive-domain restrictions
- Backup and recovery
- Product and release assurance
Security should not depend on one control alone.
Data Backups
Maintain recoverable copies of appropriate platform information.
Recovery Procedures
Support restoration where required.
Record History
Preserve appropriate workflow history.
Controlled Changes
Reduce the risk of silent or uncontrolled changes in sensitive workflows.
Product Assurance
Continue testing migration, recovery and release behaviour as the platform develops.
Backup and disaster-recovery capability forms part of EdiWay’s wider technical governance approach.
Teacher
Needs useful classroom and learner-support context, not the complete school record.
Cover Teacher
Needs appropriate teaching information, not confidential HR or safeguarding detail.
Parent or Carer
Needs approved information about their child, not internal school records.
External Professional
Needs information within the authorised learner relationship and purpose.
Marketplace User
Needs transaction information, not educational or safeguarding records.
Trust User
Needs appropriate oversight, not automatic unrestricted school-level access.
Connected does not mean copied everywhere.
Data Exports
Allow appropriate authorised data export.
Reports
Keep sensitive information inside suitable reporting permissions.
Documents
Control access to private or shared files.
Evidence Packs
Use dedicated workflows for higher-consequence information sharing.
Professional Sharing
Limit information to the agreed scope and authorised relationship.
Access History
Maintain appropriate evidence of access or delivery where the workflow supports it.
The detailed information-sharing model belongs to Permissions, Consent and Information Sharing.
Parents and Carers
Access appropriate family-facing information connected to their learner relationship.
Professionals
Work within defined learner-specific relationships.
Time-Limited Access
Professional access can be limited to the period in which it is required.
Revocation
Access can be brought to an end when the relationship changes.
Scope
Only appropriate information should be included.
The complete rules for consent, sharing purpose, access scope, expiry and revocation belong to the dedicated permissions page.
A technical administrator may need to:
- Configure the platform
- Manage accounts
- Support implementation
- Investigate technical issues
- Maintain system operation
That does not automatically mean they should:
- Make safeguarding decisions
- Determine SEND status
- View every confidential HR record
- Make clinical decisions
- Approve learner provision
- Decide disciplinary outcomes
EdiWay’s wider governance model separates system administration from professional decision-making.
- Drafting
- Summaries
- Reports
- Communication
- Teaching resources
- Review preparation
- Evidence organisation
But AI does not create new permission. A user should not be able to ask AI to retrieve information they could not otherwise access. AI outputs remain human-reviewed.
- Retention periods
- Data subject access
- Corrections
- Deletion requests
- Privacy responsibilities
- Personal data exports
- Individual rights
belong to the dedicated Privacy and Data Protection and Data Retention and Subject Rights pages. This page focuses on the security and governance controls around using the School Platform.
User Roles
Who should have which responsibilities?
Staff Access
Which people need access to sensitive domains?
Policies
How should information be used within the school?
Sharing Decisions
When is information appropriately shared?
Retention
How long should particular information be retained?
Incident Response
What school procedure applies when something goes wrong?
Professional Decisions
Who has authority to make safeguarding, SEND, HR, medical or other consequential decisions?
Good information governance combines platform controls with appropriate school leadership and policy.
Learner Records
Keep the canonical learner record school-scoped.
Teaching
Limit classroom access to relevant learners and responsibilities.
Attendance
Protect individual learner records while enabling authorised oversight.
SEND
Keep support information appropriately restricted.
Safeguarding
Use stronger specialist access boundaries.
HR
Keep confidential workforce information separate.
Reporting
Restrict sensitive data, exports and drill-through.
Marketplace
Keep commerce access separate from educational records.
Professional Collaboration
Use learner-specific, purposeful external access.
Security is not a separate feature added after the workflow. It should be part of how the workflow works.
1. Identify the User
Establish who is accessing EdiWay.
2. Establish the School
Keep the action within the appropriate organisation.
3. Check the Role and Relationship
Understand why the user requires access.
4. Check the Information Domain
Keep specialist information inside the correct permission boundary.
5. Allow the Required Action
View, edit, approve, export or share only where authorised.
6. Record Important Activity
Maintain appropriate audit or workflow history.
7. Review Access
Change permissions as responsibilities and relationships change.
8. Remove Access
End access when it is no longer required.
This helps schools maintain a connected platform without turning access into a permanent entitlement.
Yes.
EdiWay is being designed specifically around UK education workflows, learners, families, school staff and authorised professional relationships.
No.
Access can be shaped by school, role, learner, class, relationship, domain and action.
No.
Safeguarding records remain inside a separately controlled workflow.
No.
Administrative responsibility does not automatically create unrestricted access to every sensitive information domain.
Two-factor authentication capability forms part of EdiWay’s security controls.
Encryption for stored information and information in transit is represented within EdiWay’s security foundations.
Yes.
Audit-trail and user-activity capabilities are represented across the platform, with additional history inside specialist workflows.
Backup and disaster-recovery capabilities form part of the current security foundation.
No.
Family access is shaped around the recorded learner relationship, permissions and information domain.
Where enabled and authorised, professionals can work through defined learner-specific relationships.
That does not provide unrestricted access to the learner record.
Temporary and expiring access models are represented within the platform.
Appropriate data exports are supported.
Export rights remain subject to permissions and the sensitivity of the underlying information.
No.
The platform can enforce configured permissions and sharing controls.
The school and relevant authorised people remain responsible for the legal and professional basis of sharing.
No.
EdiWay AI is designed to operate within permission-aware context rather than provide unrestricted access to school information.
EdiWay should not reduce data protection to a generic marketing badge.
The platform provides data-protection, retention, access, consent, audit and information-sharing controls, while schools remain responsible for their own data-protection obligations and how the platform is configured and used.
Independent penetration-testing assurance remains part of ongoing product and release assurance and should not currently be presented as complete across the whole platform.
A connected platform does not need to mean unrestricted access.
EdiWay is specifically designed around information boundaries so related workflows can connect while permissions remain distinct.
Permissions, Consent and Information Sharing
Understand who can access or receive information, for what purpose and for how long.
AI Governance
Understand how permission-aware, draft-first and human-reviewed AI is governed.
Safeguarding Boundaries
Understand where technology stops and safeguarding authority remains with people.
Privacy and Data Protection
Understand EdiWay’s wider approach to privacy responsibilities and personal information.
Data Retention and Subject Rights
Understand retention, access and individual-rights workflows.
Implementation, Migration and Product Assurance
Understand rollout, migration, testing and release assurance.