Scoped identity and tenant authorization
Review the boundaries behind connected educational workflows
Use this hub to inspect security, privacy, accessibility, AI transparency, subprocessors, operational status, and public product changes.
What stays connected
More than a collection of classroom tools
Each capability keeps the relevant course, standards, sources, revisions, people, and next action available to the authorized workflow.
Human review for AI-assisted work
Accessibility preferences and supported interaction modes
Truthful status and change communication
How the workflow works
Trust is implemented through visible product decisions
ClassLattice trust controls are attached to the records and workflows they govern: identity scope, Vault ownership, education-record access, AI source lineage, human review, publication state, provider delivery, and operational readiness.
- 01
Scope identity and records
Organization, school, course, role, and Vault checks determine access; a route, provider connection, or matching display name does not create authority.
- 02
Keep AI work inspectable
AI-assisted artifacts remain editable, retain source and usage lineage, and pass through educator review before evidence, learner release, publication, or other consequential state changes.
- 03
Preserve authorship and sources
Authorship History and Primary Source Citations keep assistance, revision, and source context attached to the work instead of reducing integrity to a hidden score.
- 04
Expose operational truth
The product distinguishes local saves from provider delivery, healthy from degraded service, drafts from published records, and codebase capability from deployed production evidence.
Built into ClassLattice
Capabilities that support the full workflow
Each capability below is part of the current product and keeps its own records, permissions, review points, and reusable outputs.
Privacy and Access Center
Understand and review access to education records.
- Documents
Platform Administration
Monitor tenant configuration and operational readiness.
- Documents
School AI Policy
Create, review, and publish district or school AI-use policies with versioned content, multi-role approval workflow, and truthful product-enforcement mapping. Policies are saved to the Vault for provenance, and link to ClassLattice Academy for professional development. Non-legal-advice templates only.
- Documents
Authorship History
See how student work developed and where assistance was used.
- Documents
Primary Source Citations
Keep source context attached to learning artifacts.
- Documents
Continue the product and trust review
Inspect the connected workflow, access model, AI review points, and operational behavior together so the buying decision is based on what the product actually does.