Two Interfaces
- Platform control plane: global tenant management for Super Admins (/platform).
- Tenant CMS: editorial operations inside a tenant boundary (/cms).
This separation is intentional: it supports clearer audit boundaries and reduces accidental cross-scope actions.
Roles (High-Level)
- Super Admin: platform owner scope; manages tenants and platform governance.
- Admin (Tenant): manages tenant users and tenant configuration boundaries.
- Editor-in-Chief: tenant content oversight and workflow management.
- Editor: content creation within assigned editorial scope.
Core Concepts
Tenant
A tenant is an isolated workspace. Users, content, and configuration are bound to a tenant.
Domain
A domain represents an editorial area (e.g., business, health, technology) used to scope content and access.
Editorial Profile
An editorial profile defines domain context, target audience, default language, and writing guidelines used by workflows.
Validation Gate
Validation gates define quality constraints and review signals applied to generated or edited content.
Prompt Template
Prompt templates define structured instructions used in supported AI-assisted workflows. Edits are versioned to preserve auditability.
Operational Endpoints
- /api/public/health – basic health response.
- /api/public/version – version info.
- /api/ops/status – operational status (authenticated deployments may restrict access).
For UI access issues, gather the affected URL, time, and user role/tenant context and contact support@minfra.ai.