Skip to main content

A connected platform. Clear boundaries.

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 review
Your workspace
Institution context
Access controls
Roles and permissions
Your records
Institution boundaries
Role-based permissions
Access follows each person’s responsibilities.
Audit trail
Sensitive operational changes can be reviewed.

Separate institution data

Institution boundaries determine which records each workspace can access.

Role-based access

Roles and permissions determine what staff, leaders, families, and students can see or change.

Audit logging

Sensitive actions can be tracked so administrators have a clearer operational record.

Protected public forms

Contact and portal discovery forms use validation and abuse controls. Institution setup is managed through onboarding.

Recovery planning

Discuss backup retention, restore procedures, and recovery expectations as part of your service agreement.

Separate platform administration

Platform administration is separated from public pages and institution workspaces.

Your review, made practical
How institution records are separated
How users are added and access is approved
Which permissions and audit records you need
Your hosting, backup, and recovery requirements
Security review

Bring your requirements to the table.

We’ll discuss the controls available for your deployment, the evidence your team needs, and any requirements that need further planning.

Contact security team

Security FAQs

How is encryption handled?

Platform traffic uses TLS encryption. Encryption at rest and key management requirements are reviewed against the deployment and service arrangements for your institution.

Can we review certifications and compliance requirements?

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.

How are backup and recovery requirements agreed?

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.

What audit records are available?

Audit logging supports the review of sensitive operational actions. The events covered, administrator access, exports, and retention requirements should be confirmed for your rollout.

How is student access controlled?

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.