Skip to Content
ConfigurationRuntime Settings (Admin UI)

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

Found under Admin → Settings:

SettingDescription
Site NameDisplay name in the UI header
Primary ColorMain brand color (default: #3b82f6)
Secondary ColorAccent color (default: #1e40af)
Logo URLCustom logo image
Favicon URLBrowser tab icon
Contact EmailSupport email shown to researchers

Order Configuration

SettingDescription
Post-Submission InstructionsMarkdown-formatted text shown after a researcher submits an order

ENA Configuration

Found under Admin → ENA Configuration:

SettingDescription
ENA UsernameWebin account username
ENA PasswordWebin account password (stored encrypted)
ENA Test ModeToggle between test and production ENA servers

Extra Settings

Stored as JSON in the extraSettings field:

SettingDescription
Department SharingWhen enabled, researchers see orders from their entire department
Account ValidationEmail domain restrictions for registration
Study Form FieldsCustom field definitions for the study form
Study Form GroupsField 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

Checking Active Sources

To see which source is providing each setting, use the config status API:

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.