Restricted administration
Digital Brain Admin
Sign in with an authorized platform administrator account.
Platform administrator access is verified after authentication.
Restricted administration
Sign in with an authorized platform administrator account.
Platform administrator access is verified after authentication.
Overview & control center
Blueprint-aligned V1 operations overview. Later-version modules remain visibly Planned.
Live Core API, database, schema and service state.
Current normalized V1 provider route.
Registry-driven routing policies and provider/model priorities are operational.
Open Blueprint-prescribed Admin modules.
Live counts for the selected project.
Latest selected-project events.
Latest coordinated backup generation.
Exact 12-module Blueprint order.
AI foundation
Live provider registry, active model controls and capability routing configuration.
Provider Registry and model lifecycle controls are operational.
Routing policies, priority/fallback controls and STT/TTS-ready capability slots are operational; quota telemetry remains unavailable.
Knowledge foundation
V2 ingestion, OCR, evidence, structured memory, organization and authorization-first retrieval.
Operational data is loaded from the V2 intelligence snapshot without fabricated provider or quality values.
Main operational center
Project context contains people, files and knowledge, memory, connectors, Actions / Jobs, reminders, Automation and Vault operational boundaries.
Live Project counts and assignment context.
Assignments are managed by Platform Admin. Stored legacy role values are not permission levels.
Project-scoped file and knowledge operations retain their existing Core boundaries.
Upload an original file only in the selected Project context.
Connector lifecycle is administered in Connectors. Actions retain their own confirmation safety, and Jobs retain worker-owned execution; no role-based permission matrix is introduced.
Reminder and Automation state remains separate, actor-owned where applicable, and Project-scoped. Scheduler status is available under System.
Vault infrastructure is local-only. Admin never receives decrypted records, passwords, Secure Notes, tokens, or Assistant prompts/responses.
Connector catalogue and lifecycle
Connector catalogue is centralized; instance registration, credentials, activation and capability inspection remain explicitly Project-specific.
CMS external capability awaits an approved API specification. WooCommerce and Custom API live connectivity remain unverified without approved external configuration. Credential values are never displayed.
Controlled workflows
Workflows, triggers, actions, approvals, runs and queues.
No workflow, approval or execution control on this page performs an action.
Permanent assets
V2 original-file preservation, OCR/extraction, reviewable tagging, exact-duplicate lineage and project knowledge.
Runtime values come from the project-scoped V2 ingestion and intelligence records.
Admin-owned account lifecycle
Create accounts and manage the single User ↔ Project assignment boundary.
Assign or remove existing users using the canonical Admin assignment lifecycle.
Protected boundaries
Current V1 identity, Core boundary, isolation and recovery protection.
External assurance and later hardening are not claimed complete.
Recovery architecture
Coordinated database, file and local-model backup state.
Database, original files and Ollama are scheduled and checksum verified.
Disposable restore validation is available. Destructive production restore is not exposed here.
Accountability
Recent V1 mutation and orchestration events for the selected project.
Connector, automation, approval and advanced recovery audit domains are not implemented.
Configuration
V1 owner-controlled, versioned project settings.
AI and Voice V2 capabilities are operational; Connector and Automation settings remain V3 planned and not started.
Consolidated platform administration
Security, Vault infrastructure, Backup & Recovery, Audit, Settings and Service Health in one operational destination.
Live Core API readiness, database and schema; Worker and Scheduler are separately reported.
Destructive restore is not exposed in Admin.
Project audit and Timeline/Event inspection remain scoped to their Project context. No secret payload is rendered.
AI & Voice configuration is in AI & Voice; Project configuration remains Admin-mediated and Project-scoped. No normal-user Settings controls are embedded here.