Separate institution data
Institution boundaries determine which records each workspace can access.
Your institution’s records need clear ownership and controlled access. AcademicGrid is designed around institution boundaries, role-based permissions, and traceable operational changes.
Request security reviewInstitution boundaries determine which records each workspace can access.
Roles and permissions determine what staff, leaders, families, and students can see or change.
Sensitive actions can be tracked so administrators have a clearer operational record.
Contact and portal discovery forms use validation and abuse controls. Institution setup is managed through onboarding.
Discuss backup retention, restore procedures, and recovery expectations as part of your service agreement.
Platform administration is separated from public pages and institution workspaces.
We’ll discuss the controls available for your deployment, the evidence your team needs, and any requirements that need further planning.
Contact security teamPlatform traffic uses TLS encryption. Encryption at rest and key management requirements are reviewed against the deployment and service arrangements for your institution.
Bring your requirements to a security review. We will discuss the controls, evidence, and any certification or compliance requirements relevant to your deployment. This page does not claim independent certification.
Backup retention, restore procedures, recovery time, and acceptable data loss are confirmed during service and rollout planning. Discuss your requirements before agreeing production service terms.
Audit logging supports the review of sensitive operational actions. The events covered, administrator access, exports, and retention requirements should be confirmed for your rollout.
Institution boundaries and role-based permissions govern access to student records. Parent and student experiences are scoped to linked records and the access enabled by the institution.