System Settings

Settings → System is an administrator-only workspace control surface. Its settings affect authentication callbacks, links in messages and webhooks, retention, credential storage, and performance investigation. Make one high-impact change at a time and verify the affected flow before making the next.

Application URL

The application URL is used in email links, webhook payloads, RSS, public status-page links, and the displayed OIDC callback URL. The effective value has this precedence:

The database value set in Settings → System → Application URL.
NEXT_PUBLIC_APP_URL in the deployment environment.
http://localhost:3000 as a development fallback.

Set an externally reachable, canonical https:// URL in production. A database value can be cleared to return to the environment fallback. The settings form accepts http or https, but production deployments should use HTTPS.

Before changing the URL, update reverse-proxy/ingress routes and the OIDC provider's allowed redirect URI. After saving, test a notification link, an RSS/status link, an inbound/outbound webhook URL as applicable, and a fresh OIDC sign-in in a private browser window.

OIDC and encryption

The System page exposes the OIDC configuration and displays a callback URL derived from the effective application URL. OIDC client secrets require a valid ENCRYPTION_KEY; in production the page warns when that key is missing.

Do not rotate the application URL, OIDC configuration, and encryption key in one change window. Each has a separate failure mode and rollback decision. Follow Authentication, OIDC SSO setup, and Encryption for their complete procedures.

Retention

Retention controls are system-wide and destructive when cleanup executes. The System page opens the retention workflow, but its policy, preview, and recovery boundaries are documented separately in Data retention. Take a tested database backup before reducing a window.

Administrator Health Center

The System page links to Administrator Health Center, an Admin-only on-demand summary of database connectivity and capacity, migrations, scheduler and job health, paging configuration and backlog, notification and integration failures, SLA-query performance, public URL consistency, encryption configuration, and release availability. The former Performance Monitoring route redirects here so administrators have one operational destination.

Unknown evidence is not reported as healthy. The Health Center complements the incident timeline and external infrastructure, database, backup, and provider monitoring; see the Health Center guide for thresholds and boundaries.

Safe change procedure

Record the current value, deployment version, and a rollback owner.
Confirm a second active administrator has access.
Take or verify a database backup for destructive or credential-related work.
Change one setting and save it.
Test the directly affected path using a normal user session or external recipient where relevant.
Review application logs, notification history, and audit records.
Document the result and rollback plan before proceeding to another setting.