Modules
Every module in the product, organised into the seven navigation groups the application itself uses.
This is the heart of the documentation. Every module is documented against the same template, so any two modules can be compared directly and nothing is silently omitted.
The seven groups
| Group | Modules | Purpose |
|---|---|---|
| Operate | 8 | Daily command surface — what is happening now and what to do about it |
| Analyze | 13 (+ sub-modules) | Depth — where money goes, why it moved, what it buys |
| Govern | 8 | Controls — rules, gates, attribution, and evidence |
| Security | 3 | Estate posture — inventory, threat, and compliance |
| Admin | 7 | Tenancy — users, workspaces, connections, integrations, identity |
| Account | 2 | Commercial — plan, entitlements, credits, profile |
| Help & Updates | 2 | Assistance — support tickets and error history |
You are not locked into these groups
The sidebar layout editor lets each user regroup modules into anywhere from 3 to 15 custom groups, persisted per user. The groups documented here are the defaults.
In a product of this breadth, a fifty-module sidebar serves nobody — letting each person shape it to their role is what keeps the surface navigable. Configured in Settings.
How the groups connect
The product is deliberately a connected system rather than a set of independent dashboards. Each module page carries a Connects to section naming the modules it feeds and depends on — those are how the connections are traced.
The module template
Every module page answers the same seven questions in the same order:
| Section | What it answers |
|---|---|
| At a glance | Route, navigation group, page permission — the facts you need to find it and grant access to it |
| What it is | A plain-language definition in two or three sentences |
| Who it is for | The roles that live in this module day to day |
| How it works | The actual mechanism — where data comes from, what is computed, what is persisted |
| Features | The concrete capability list |
| How to use it | A numbered operating procedure, from first use through to steady state |
| Why it matters | The business outcome, in terms of money, risk, or time |
Start here
Apex
The natural-language control plane. The lowest-friction entry point in the whole product — start here if you would rather ask than learn a dashboard.
Overview
The default landing page and primary spend posture view. The page most users open first each day.
Opportunity Queue
Where every detection across every cloud lands as a costed, scored finding.
Complete module index
Every module, route, group, and permission in one table.