How The Platform Fits Together - Home, See, Act, Prove, Configure
Summary
The platform's menu is organized into five sections that read top to bottom as a working flow: Home to start, See to watch, Act to fix, Prove to show your work, and Configure to administer your organization underneath all of it. Command Center, Onboarding, and Support each sit outside this flow, pinned in three different spots in the sidebar, not grouped together.
Home, where you start
- Overview: a board-ready executive report: where you stand, what changed, and what to do next, read top to bottom rather than worked in.
- Insights: board-ready analytics on AI adoption, productivity, and ROI.
- Dashboard: your own customizable workspace, with a persona-based widget grid. On the Ultimate plan it also has a Live tab, a continuously updating view of activity.
- My AI: a private, read-only report of your own AI usage only. See Your personal AI report.
See, what's happening, and whether you can see it all
- Users: every human and machine identity using AI, including a separate view for autonomous AI agents.
- Platforms: every AI tool detected, including tabs for tool discovery, on-device software inventory, and vendor threat intelligence.
- Assets: your inventory of data-bearing assets: what's in the estate, what discovery has proposed, how assets are grouped, and which have drifted out of policy.
- Activity: the fused, organization-wide timeline of every AI transaction and security event.
- Data flows: where information actually moves once it touches an AI tool.
- Coverage: which devices and people your sensors aren't fully reaching yet.
Some destinations are reached as a tab inside one of these rather than as their own menu entry: tool discovery, software inventory, and threat intel all sit under Platforms; AI Agents under Users.
Act, where you fix what See flagged
- Inbox: your personal triage queue, including narrative story rollups and the formal incident workflow as tabs.
- Remediation: the organization-wide portfolio of every actionable item, regardless of who owns it.
- Policies: where the rules governing AI use get authored.
Some entries in this section (and in Prove, next) depend on your plan, and each one is locked or open on its own. An entry your plan doesn't include still shows in the menu with a lock, and opening it explains what upgrading unlocks. A few entries work differently: see the note under Prove.
Prove, the evidence you can show
- Scenarios: operator-driven threat modeling: compose a threat from real objects (people, platforms, assets, agents) and resolve each to a live cohort to see where you're unprotected.
- Exposure: findings ranked into financially modeled risk scenarios. The dollar figures need Attack Simulation, which comes with the Ultimate plan or as an add-on; without it, Exposure still shows posture, threats and coverage, and each dollar figure shows as a dash.
- Compliance: readiness against named frameworks, including the external-auditor collaboration space as a linked destination.
- Audit log: the read-only record of every admin and security-relevant action.
Scenarios, Exposure, Attack Simulation's dollar figures, and Compliance's readiness programs and auditor collaboration have to be turned on for your organization, even when your plan includes them. Until they are, their menu entries don't appear. Upgrading alone doesn't turn them on; ask your account team.
Configure: administering your organization
The admin layer everything else runs on. Reaching any of it requires the Manage Users or Manage Tenant permission, and several pages carry a further permission or plan requirement on top: so two administrators can legitimately see different options here.
- Organization: the facts about your company the rest of the platform reasons from: Profile (company identity and time zone, plus the Exposure context figures that exposure and ROI calculations use), Plan & features, Data & privacy (what the endpoint sensor collects, how people are identified on shared surfaces, retention periods, an individual's GDPR export and erasure rights, and your DPIA document), and Security objectives. See Complete your organization profile.
- People & access: who can sign in, what they can do, and how they authenticate: users, roles, workspaces, tags, bulk imports, your identity provider, and the sign-in and domain policy. See Set up your team.
- Capture & devices: what devices and browsers collect, and how CyberHQ.ai gets onto them. Capture is where collection is turned on or off. The browser extension covers Chrome and Edge (Brave and Arc run it but aren't certified); the endpoint sensor extends to desktop AI apps, CLI tools, other browsers and local models; OTLP ingest covers agents running beyond your managed endpoints. Site compatibility reports whether the extension's page-reading still works as sites change. See Add your first device.
- Detection: how the platform interprets what your sensors report: coverage and offline thresholds, behavioral baselines, paste windows, exposure-chain promotion, KPI alert bands, risk scoring, and the usage classifier model. Nothing here changes what is collected. See Tune detection thresholds.
- Integrations: every connection to something outside the product: notification channels and the daily briefing, your email provider, your AI provider, API keys, and scheduled report delivery. See Connect an integration.
Three things pinned outside the flow, in three different places
- Command Center: top of the sidebar, above the main menu. Your workspace for AI activity across the organization (its live stream is part of the Ultimate plan), always one click away because it's used constantly, not occasionally.
- Onboarding: below the main menu, not next to Command Center. Your setup-progress tracker. See Your onboarding checklist.
- Support: bottom of the sidebar, next to the theme toggle and your account menu. See Get to know Support.
How it all connects
The flow is meant to be read left to right, not just top to bottom: something surfaces in See, you act on it in Act, and the outcome becomes evidence in Prove: a finding becomes a policy or a remediation, and a completed remediation becomes something you can show an auditor. Home is where you notice something needs that cycle; Configure is the admin layer every other section depends on.
Related
- Welcome to CyberHQ.ai
- Your onboarding checklist