Admin Control Plane Overview
Operator control plane
The admin app is the Builder Insights control plane for event management, insight review, reporting, imports, and operations. It turns field capture into visible, actionable signal for operators, product teams, and leadership.
The admin app succeeds when
- newly synced records are easy to verify and trust
- operators can manage context and reporting without guesswork
- leadership can move from raw data to patterns quickly
Operator map
Product areas
Shows team and executive metrics, trend summaries, charts, and top-level system health.
Defines the context model that mobile users rely on before they capture field signal.
Provides the most direct path to review, search, enrich, and validate captured records.
Supports PMO-style CSV ingestion, mapping reuse, preview flows, and upsert behavior.
Supports exports, backup-oriented workflows, database visibility, and administrative maintenance.
Holds schema alias configuration, environment-driven behavior, and support-oriented controls.
Operator workflow
Start on the dashboard to understand recent activity, trends, and whether data appears to be flowing normally.
Use events and related configuration to keep the mobile capture model clean and current.
Use insights views to confirm that new records arrived, remain readable, and preserve their meaning.
Operators can add structure, correct issues, and support downstream analysis without losing source fidelity.
The app should make it easy to turn records into summaries, maps, leaderboards, and distributable outputs.
Technology stack
| Area | Current choices | Why it matters |
|---|---|---|
| App framework | Next.js 16, React 19 | supports the web control plane and route-driven operator workflows |
| UI layer | Material UI | provides the structured tables, forms, and dashboard surfaces the portal depends on |
| Data access | MongoDB native driver | connects the admin and backend workflows to the shared system of record |
High-trust areas
If event setup or metadata is wrong here, mobile capture context and later reporting both become unreliable.
Filters, detail views, and AI summaries should reflect the same meaning that was captured in the field.
Mapping drift can create hard-to-see data quality issues that only show up later in reporting.
Leadership trust depends on summary views matching the underlying records closely enough to defend the story.
Best companion docs
Use this for a guided visual tour of the portal and what each major view is meant to communicate.
Data model and APIUse this to understand the shared contract that keeps mobile capture and admin reporting aligned.
Testing and releaseUse this for QA and release coordination once admin changes need to move safely into production.
Repo references
Use the admin repo for code-adjacent truth, especially for route behavior, environment setup, and operator guidance.
README.mddocs/PRODUCT_OVERVIEW.mddocs/TESTER-GUIDE.md