Administration Database

Why This Exists

This document defines conceptual database responsibilities for the Administration Domain. It does not define physical SQL implementation.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Administration storage must preserve platform configuration, support workflow, feature flag, audit review, policy configuration, and governance history.

Conceptual Tables Or Collections

Table or collection	Responsibility
administration_platform_configurations	Configuration key, scope, value reference, version, status, and effective dates.
administration_feature_flags	Feature flag key, rollout state, targeting rules, owner, and status.
administration_support_cases	Support case priority, status, source references, assignment, and resolution.
administration_support_case_notes	Internal notes, authorship, classification, and timestamps.
administration_tenant_views	Admin-facing tenant view metadata and OrganizationId references.
administration_policy_configurations	Policy configuration records, target domain, version, approval, and status.
administration_audit_reviews	Audit review scope, source evidence references, status, reviewer, and findings.
administration_governance_records	Governance decisions, exceptions, reasons, authority, expiry, and status.
administration_integration_configurations	Integration type, scope, status, and non-secret configuration references.
administration_admin_dashboards	Admin dashboard composition and references to analytics models.
administration_admin_actions	Recorded admin actions, actor, target, result, and timestamp.
administration_audit_log	Domain audit events for administration changes.

Indexing Considerations

Administration should support indexes for:

• configuration_key.
• configuration_scope.
• feature_flag_key.
• organization_id.
• support_case_status.
• support_priority.
• policy_target_domain.
• audit_review_status.
• governance_expiry_date.
• actor_id.
• created_at.

Audit Requirements

Audit logging is required for:

• Configuration changes.
• Feature flag rollout changes.
• Emergency disable actions.
• Support case resolution.
• Audit findings.
• Governance decisions and exceptions.
• Policy configuration approvals.
• Integration configuration changes.

Data Boundary

Administration may store snapshots or summaries for admin workflow context, but those must be labeled as administrative view data. Source facts remain in their owning domains.