Runtime Settings (Admin UI)

Settings stored in the database can be changed through the Admin UI without editing files or restarting the server. These have the lowest priority — they are overridden by config file values and environment variables.

How It Works

Database settings are stored in the SiteSettings table as a singleton row. When SeqDesk resolves configuration, database values are merged last:


defaults ← database ← config file ← environment variables

If an environment variable or config file entry exists for the same setting, the database value is ignored. This means the Admin UI is most useful for settings you do not manage through files or environment variables.

Available Settings

Site Branding

Branding fields are stored on the SiteSettings singleton row and managed through the Admin UI — not on the Admin → Platform Info page, which is diagnostics-only (see below).

Setting	`SiteSettings` field	Description
Site Name	`siteName`	Display name in the UI header (default: `SeqDesk`)
Primary Color	`primaryColor`	Main brand color (default: `#3b82f6`)
Secondary Color	`secondaryColor`	Accent color (default: `#1e40af`)
Logo URL	`logoUrl`	Custom logo image
Favicon URL	`faviconUrl`	Browser tab icon
Contact Email	`contactEmail`	Support email shown to researchers
Help Text	`helpText`	Optional help text shown to researchers

Order Configuration

Setting	Description
Post-Submission Instructions	Markdown-formatted text shown after a researcher submits an order

ENA Configuration

Found under Admin → ENA Configuration:

Setting	Description
ENA Username	Webin account username
ENA Password	Webin account password (stored encrypted)
ENA Test Mode	Toggle between test and production ENA servers

Extra Settings

Stored as JSON in the extraSettings field:

Setting	Description
Department Sharing	When enabled, researchers see orders from their entire department
Account Validation	Email domain restrictions for registration
Study Form Fields	Custom field definitions for the study form
Study Form Groups	Field grouping configuration

Modules Configuration

Found under Admin → Modules:

The modulesConfig field stores which optional features are enabled or disabled. Module changes may require a page refresh to take effect.

Immediate vs Restart-Required

Most database settings take effect immediately:

Site branding (name, colors, logo)
Contact email
Post-submission instructions
Department sharing
Module toggles

Some settings require a server restart:

Database connection changes
Authentication configuration changes

Platform Info (Diagnostics)

The Admin → Platform Info page (/admin/settings) is a diagnostics view for facility admins. It surfaces the running version, update status, tool checks, feature flags, and the effective configuration sources — it does not edit branding or facility settings.

Checking Active Sources

To see which source is providing each setting, use the config status API (also backing the Platform Info page):


GET /api/admin/config/status

Each setting in the response includes its source: env, file, database, or default. If a setting shows database as its source, it can be changed through the Admin UI. If it shows env or file, the Admin UI value is being overridden.

Secrets are masked in the /api/admin/config/status response. ena.password, notifications.relayToken, and the runtime secrets (nextAuthSecret, anthropicApiKey, adminSecret, blobReadWriteToken) are returned as ******** when set. The endpoint is restricted to FACILITY_ADMIN sessions.