Settings and Operations

Settings and Operations

Overview

Settings and operationaloperations administrationpages arelet database-backedplatform in CMS v2. Platform operatorsadministrators manage runtime settings,configuration, themes, notification delivery, backups, jobs, updates, documents, and selected feature flags from the portal.flags.

Settings Categories

Active settings categories include:

Category	Typical contents
Authentication	JWT,Sign-in, activation, MFA, and federated login settings.
Backup	Backup provider, tooling, storage, and retention settings.
Billing	Invoice settings, invoice visibility, billing mode, and billing usage selection.
Notifications	Email provider, SMTP,delivery Graph,settings, budget alert,alerts, and templatenotification settings.templates.
Platform	Defaults, self-provisioning, region retention, quotas, timezone, and platform options.
Portal	Portal shelltitle, settings, titles,theme, login options, and display configuration.
Updates	Update enablement, channel, updaterPatch APIManager key,connection, and deploymentupdate metadata.settings.

Full settings reads require platform roles. Updates require PlatformAdministrator. Non-platform portal users receive only whitelisted non-secret shell feature flags.

Settings Page

The Settings page is available at /settings forto platform roles. It uses tabs forincludes Backend, Billing, Platform, Portal, and Themes.Themes tabs.

Shared categorySettings panels supportcan include refresh, search, save-all, switches, text fields, number fields, color picker, tenant selector, currency selector, and file picker controls.

Settings are edit-only records. The portal does not create or delete settings rows.

Secrets

SecretMost settings are encryptededited beforein persistence,place. If a setting is missing, confirm the environment has been prepared with the required deployment steps.

Sensitive Settings

Sensitive settings such as passwords, connection strings, and API keys are masked in APIthe responses,portal. andWhen preserveda masked value is left unchanged, CMS keeps the existing value.

Only update sensitive settings when the maskreplacement value is submitted unchanged.

Examples include SMTP password, Graph client secret, Azure Storage connection string, updater API key,known and otherapproved deploymentfor credentials.the environment.

Themes and Branding

The Themes tab lets platform administrators create, edit, validate, delete, and select database-backed portal themes. Theme JSON uses MudTheme JSON, not raw C#.

Branding assets can includeinclude:

app

• App bar logo,logo.
login
• Login logo,logo.
• Login wallpaper.
• Font metadata.
• Theme colors and logintypography.
wallpaper.

Missing

If databasea assetstheme fallor asset is missing or invalid, CMS falls back to staticdefault portal assets.styling.

Notifications

Administration > Notifications manages delivery settings and notification templates.

SupportedThe Delivery tab controls email delivery areassettings. includeThe SMTP,Templates Microsofttab Graph,lets operationalplatform toggles,administrators edit template name, subject, description, enabled state, and templatebody content.

Platform administrators can send a test sends.message SMTPfor testa validatesselected connectivitytemplate andafter STARTTLSconfirming negotiationthe whenactive enabled;delivery itprovider doesis not send an email.

Notification templates are platform-scoped records. Reads are limited to platform roles, while updates and test sends require PlatformAdministrator.configured.

Backups

The Backups page is available at /backups for platform roles. It lists stored backups and exposes manual run, refresh, restore, provider settings, storage settings, and connection tests.

Backup files are named with backup timestamp and tier. Manual and pre-restore backups are notretained removedseparately byfrom scheduled tierbackup cleanup.

Retention uses a roll-up model where lower tiers retire after a higher tier exists for a later backup date, with configured retention counts still capping active tier windows.

Restoring a backup creates a pre-restore safety backup first.

Timezone and Localisation

CMS stores operational timestamps inconsistently UTC. The portaland displays timestampsthem using the user's timezone wherewhen set,set. otherwiseIf Platformthe >user Generalhas SystemTimeZoneId,not otherwiseselected UTC.a timezone, CMS uses the system timezone setting.

The localisation feature defines English asis the default andlanguage. French asis the first additional language.language MudBlazorin componentthe translationslocalisation use MudBlazor translations, while CMS-owned text should use application resources.plan.

Documents and Terms

Documents and terms are managed through platform document APIs and portal document surfaces. Required documents can blockrequire user or tenant acceptance before users continue normal portal usework. until accepted.

New subscription terms arecan checkedappear during subscription creation usingwhen tenantenabled.

Access

Settings, backups, notification administration, jobs, updates, and region scope priority: tenant, selected region, all regions, then platform.

Operational Notes

Database-backed settingsthemes are theplatform sourceoperations forareas. runtimeIf configuration.a APIuser andcannot Portalsee startupone doof notthese createpages or backfillactions, confirm the user has the required databaseplatform setting rows from appsettings.

Take a full MySQL backup before applying settings, themes, notification, backup, timezone, quota visibility, billing usage selection, update, or document scripts.role.

Known Gaps

Manual Review Required: Feature documents include several deployment script notes. Confirm each target environment has applied the required scripts before treating all portalSome settings and operational pages depend on environment preparation. Confirm the relevant deployment steps have been completed before treating every setting or operational action as complete.available.