Admin Overview ​

The admin area is where InfraScout is configured. Anything that affects more than your own work — enrolling agents, registering MCP servers, granting access, reading the audit trail — lives behind the Admin entry in the user navbar. Only users whose Entra identity carries an admin role see the entry.

Entering the admin area ​

Clicking Admin in the user navbar swaps the navbar layout: the user-area links (Chat, Agents, Sessions, Insights, Executions) are replaced by five hover-dropdowns, each leading into a tabbed admin section. A persistent Admin badge to the right of the InfraScout logo reminds you that you are in elevated context.

The Home icon to the left of the dropdowns takes you back to the user area without signing out. The right side of the navbar (SSE indicator, API status, user menu) is identical to the user area.

Section map ​

The five admin sections each cluster a tabbed page set. The pattern is the same everywhere: the page header carries the section title, a one-line description, and an Admin Access chip that links to whichever Entra group grants entry; the body is a tabbed UI with each tab as a separate route.

Agent Management — operational control of the agent fleet:

  • Agents — full agent list with enrollment, revoke, and group assignment
  • Agent Groups — define groups for AI-driven assessments
  • Updates — pipeline of in-flight and historical agent updates
  • Update Policies — when and how agents are allowed to update themselves
  • Inventory Policies — what each agent collects on its scheduled inventory sweep

AI Integrations — everything that controls how the AI can act:

  • Playbooks — the assessment playbook catalog
  • Tool Groups — bundles of tools the AI can be allowed to call in a single chat
  • AI Providers — Claude model credentials and per-tenant defaults
  • Agentic Workflows — multi-step automated assessments (documentation in progress)
  • MCP Servers — register external MCP servers as additional tool groups
  • Memory — the persistent memory store the AI uses across sessions

Role Management — who is allowed to do what:

  • Users — every Entra user discovered through the connectors
  • Groups — Entra security groups synced through the connectors
  • Connectors — the Entra ID connection itself

Notifications — outbound communication. The Delivery Log and Templates tabs document every notification InfraScout has tried to send and the message templates it used. (Documentation in progress.)

Audit & Compliance — what happened, by whom, and when:

  • Audit Events — raw security-relevant events (documentation in progress)
  • Browser Sessions — active and historical portal logins
  • MCP Sessions — every connection from a Claude (or other MCP) client
  • Executions — tenant-wide command execution log
  • Chat Audit — every chat conversation, retained for compliance review

Conventions ​

The admin pages follow a few consistent patterns.

Tabs are routes. Each tab in a section is its own URL. Bookmarks land on the right tab; the back button moves between tabs as you would expect.

Cards over tables for editable entities. When the entity is something you create, name, and edit (a tool group, a playbook, an MCP server, an AI provider), the page renders cards with Edit / Delete controls. When the entity is something you observe (a user, a session, an execution), the page renders a table.

Refresh is always optional. Every admin page subscribes to the same SSE stream as the user area. The Refresh button in the header is a fallback for forcing a full reload.

Show deleted toggles. Most user, group, and policy lists default to active items only. A Show deleted toggle in the header reveals soft-deleted rows when you need them.