Dashboard
Where allow, hold, and block decisions for your education agents surface in the ArmorIQ dashboard.
ArmorEdu does not have its own dashboard route. Education agents show up in the same org-scoped ArmorIQ dashboard as every other registered agent: there is no separate /dashboard/armoredu screen. What changes is which agent and which decisions you're looking at, not which UI you use.
Where decisions surface
Every tool call your ArmorEdu policy evaluates produces one of allow, allow_log, hold, or block. These are not a bespoke ArmorEdu view; they appear in the same places any policy decision does:
- Active Agents on the main dashboard counts your course-management, research assistant, and OIT operations agents alongside every other registered agent in the org.
- Intent Intelligence shows the intent plans generated by those agents, with approved/blocked percentages and per-agent activity.
- Each plan's risk level reflects what the underlying tool call touched: a
grant_domain_adminorexport_student_recordscall reads as higher risk than a read-onlysearch_coursescall, because the plan carries broader or more sensitive scope.
Held actions and approvals
hold is the enforcement action that routes a call to a human before it runs. For the three bundles, that's publish_final_grades (course), submit_grant_proposal above the configured amount (research), and create_privileged_account (OIT). See Bundle Templates for the full list per bundle.
A held call becomes a plan in the held state: waiting on a pending delegation approval. Find it in the Plans queue, where an authorized approver reviews the plan and approves or rejects it. Approving lets the call proceed; rejecting keeps it blocked. See Plans Governance for the full status lifecycle, and note that a plan's status is computed at read time, so a hold you approved a moment ago should reflect immediately.
If a call you expect to be held instead completes immediately, or a held plan never appears, check that the policy's toolEnforcement entry for that tool actually says hold and that the policy's targetId matches the agent that made the call. See Troubleshooting.
Org-scoped, not agent-type-scoped
Everything the dashboard shows is scoped to the selected organization, the same way it is for every other product vertical. There's no ArmorEdu-only filter or education-specific chart. If you have course, research, and OIT agents registered in the same org, their activity, plans, and holds all show up together, distinguished by agent name and policy, not by a product tab.