Management portal
Operator view for saved customer cases, team queue, scan evidence, recurrence alerts and integration health.
Configured
Public summaries remain redacted for authorized-local records; management uses the principal id to route work.
Client
Test
Principal id
authorized-test
Identifiers
14
Services
5
Identifier mix
1 phone · 1 email · 1 domain · 1 handle · 1 address
Business entities
1
Selectable clients
4
configured
Human review backlog
0
critical + high findings
Partner queue
0
legal / trust dependent
StealthScore
70 → 82
case-derived
Principal risk heatmap
Severity distribution across findings
Critical
0
High
0
Medium
1
Low
3
Team queue
Lane distribution
- Action ready11
- Validated7
- Closed / monitor1
- New exposure1
SLA / deadline board
Cadence ownership
- Day 2 broker opt-outDry-run
- Day 7 partner reviewWaiting partner
- Day 14 re-scanPlanned
- Day 30 report-outConnected
Partner dependency queue
Items blocked on legal / trust partner
Integration health
Honest readiness across the mesh
- Postgres case backendLive
- Case KanbanLive
- Case calendarLive
- Executive reportsLive
- DocsLive
- SheetsLive
- FilesLive
- TraceLive
- BrowserOpsLive
- SearchOpsLive
Daily operations briefing
- 1. Clear human-review backlog (0 items).
- 2. Confirm partner review scheduling (0 items).
- 3. Run protected OSINT adapters or workflow scans against the selected client.
- 4. Verify downstream Docs, Sheets, Files, BrowserOps and Sandbox handoffs.
Implementation runway
Pilot gaps are surfaced as locked or degraded, not hidden
- 1. Customer onboarding creates the source client record and return key.
- 2. Management routes only operate on saved authorized-local clients.
- 3. Roadmap services remain locked until billing, approval, and executor coverage are present.