Skip to main content

Branding and Configuration

Summary​

Platform stores tenant presentation metadata, company settings, service-level configuration, tenant overrides, and references to externally managed secrets. Some channel/provider records are foundations rather than proof of an active integration.

Audience​

  • Platform and customer administrators
  • Implementation, support, development, DevOps, architecture, and security teams

Purpose​

This page clarifies configuration scope and ownership while excluding secret-bearing names, values, infrastructure details, and sensitive operating procedures.

Architecture​

Business concepts​

  • Tenant branding — Implemented: source supports display/logo references, color/theme metadata, login presentation, and email presentation fields linked to the platform client.
  • Company settings — Implemented: category/key/value metadata can be managed for a tenant; settings may be marked secret and therefore require protected handling.
  • Configuration catalog and service values — Implemented foundation: source supports definitions, versioned service configuration, tenant overrides, audit records, and external secret references.
  • Global defaults and tenant overrides — Implemented foundation: a configuration service resolves tenant values before service/default values where records exist.
  • Channel and storage configuration — Foundation: email, storage, SMS, and messaging-channel records and administration surfaces exist. Provider activation and production readiness require confirmation.
  • Ownership — Requires confirmation: the final approval matrix for global, service, and tenant-level changes is not encoded as documentation-ready policy.

Technical implementation​

Branding can be established during provisioning and updated for a client-linked tenant. Configuration records are persisted separately by scope and include version/audit metadata. Secrets are represented by references rather than being appropriate for documentation or general administrative output.

Screenshot placeholder: Tenant branding administration overview. Capture only after the approved administration interface is available and scrub all tenant-identifying values.

Screenshot placeholder: Tenant configuration scope and override view. Capture only public-safe field labels; exclude values, secret references, and infrastructure details.

Source References​

  • microservices/src/platform-service/Api/PlatformAdminEndpoints.cs
  • microservices/src/platform-service/Api/PlatformTenantBrandingEndpoints.cs
  • microservices/src/platform-service/Api/PlatformConfigEndpoints.cs
  • microservices/src/platform-service/Application/ConfigurationService.cs
  • microservices/src/platform-service/Domain/Entities/TenantBranding.cs
  • microservices/src/platform-service/Domain/Entities/CompanySetting.cs
  • microservices/src/platform-service/Domain/Entities/ConfigurationEntities.cs
  • microservices/src/platform-service/Application/TenantProvisioningOrchestrator.cs

See Also​

Keywords​

  • Tenant presentation
  • Configuration scope
  • Tenant override
  • Secret reference

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-14
  • Review cycle: Quarterly