DocsOperateThe console

The console

The console is the whole product for anyone who does not use a terminal. Every screen answers one question, and no screen requires knowing how the runtime works.

Console → Dashboard, the signed-in landing screen

Console → Dashboard, the signed-in landing screen

screenshot slot, save as public/screens/…png and set  src

The dashboard is a summary, not a control panel. Everything on it links to the screen that can actually change something.

Dashboard

What is the state of things right now? Open incidents, waiting approvals, recent decisions, ingestion health.

Activity

What has happened? Every source event and every governed action, newest first, each linking back to its original. This is the screen to open when somebody says "when did that change?"

Console → Activity, filtered to one source with an event expanded

Console → Activity, filtered to one source with an event expanded

screenshot slot, save as public/screens/…png and set  src

Filter by source, by person, by date. The permalink on each row is the point of the whole screen.

Approvals

What needs me? Pending requests with the agent, action, target and environment that identify exactly what you are authorizing. See Approvals.

Decisions

What does Memnox believe we decided? The review queue plus everything already approved. See The review queue.

Graph

How does this connect to that? The organizational graph, navigable node by node.

Console → Graph, one node selected with its neighbourhood visible

Console → Graph, one node selected with its neighbourhood visible

screenshot slot, save as public/screens/…png and set  src

Start from a decision and follow evidence, or start from a person and follow ownership.

Projects

What are we working on, and who owns it? Projects, their knowledge scope and their sources.

Analytics

How are we doing? Volumes and rates over time, and the catch-up digest of what changed since you last looked. See Analytics and catch-up.

Others, the screens you visit when something needs changing

Policies

The rule set in force, its version history, and the ability to validate, simulate and roll back. Editing here is for workspace-level rules; repository rules stay in the repository. See Writing policies.

Console → Policies, showing the current version and its history

Console → Policies, showing the current version and its history

screenshot slot, save as public/screens/…png and set  src

Every change is versioned by content hash. Rolling back is a first-class action, not a restore from backup.

Safety packs

Install, remove and set the per-environment mode of the 33 shipped policy packs.

Incidents

Open, acknowledged and resolved, with the evidence behind each. See Incidents.

Agents

Every registered agent, its capabilities, its trust score, and the controls to suspend or rotate its credential — and beside them, what each agent may know: its owner, what it is for, what it may commit alone, and whether it is live, lapsed or halted. See Hiring and retiring an AI worker.

Console → Agents, one agent selected showing capabilities and trust score

Console → Agents, one agent selected showing capabilities and trust score

screenshot slot, save as public/screens/…png and set  src

Suspending an agent takes effect on its next call. Rotating issues a new credential and invalidates the old one.

People

One person across every tool, resolved by email. See People.

Connectors

Connect, pause and disconnect integrations, and manage which triggers each one listens to. See Integrations.

Audit

The hash-chained record, its verification state, and CSV export. See Activity and audit.

Settings

Organization profile, members and roles, permalink base URLs, notification sinks and webhook subscriptions, billing.

Who should be given what

Person

Engineer

Activity, Approvals, Policies, Agents, Incidents

Team lead

Approvals, Decisions, Incidents, People

Operations

Activity, Decisions, Projects, People

Compliance

Audit, Decisions, Incidents, Settings → members

Executive

Dashboard, Analytics, Incidents