ArmorEdu Overview
Policy controls for education and research AI agents, covering FERPA data handling, research-data governance, and privileged-access limits.
ArmorEdu is the ArmorIQ policy vertical for AI agents that operate on academic data. It applies the same intent-token and policy engine used across the platform to the situations that matter in higher education: student-record confidentiality, research-data classification, grant handling, and privileged IT operations.
An ArmorEdu policy targets a specific agent and decides, per tool call, whether the action is allowed, logged, held for human approval, or blocked. The controls are expressed as declarative fields in a policy document, so a registrar's data rule reads as a data rule rather than as procedural code.
What ArmorEdu Governs
ArmorEdu ships three starter policy bundles, each written for a distinct campus agent. They are examples you adapt to your own agents and org, not turnkey compliance certifications.
| Bundle | Agent it governs | Blocks | Holds for approval |
|---|---|---|---|
| Course & Student Records | Course-management agent | External export of student records | Final-grade publication |
| Research Data & Grants | Research assistant agent | Sharing restricted or export-controlled datasets | Grant proposals above a set amount |
| Office of IT | OIT operations agent | Granting domain-admin privileges | Creating privileged or service accounts |
See Bundle Templates for the tools, data categories, and thresholds each bundle defines.
How It Fits the Platform
ArmorEdu agents integrate through the ArmorIQ SDK. Before a tool runs, the agent obtains an intent token and the policy engine evaluates the ArmorEdu policy that targets it. A hold routes the action into the approvals and plans flow; every decision is recorded in observability.