Skip to content

Settings overview

A FedMS instance has three layers of configuration:

  1. Drupal core configuration — site name, time zone, languages, caches, themes. Standard Drupal /admin/config.
  2. FedMS framework configuration — event/session/attachment types, task patterns, ECA models, federation settings. Specific FedMS admin paths.
  3. Tenant-specific configuration — orgs, events, sessions, users, memberships. The day-to-day operational content.

This section covers the first two layers. The third is covered in the User guide and the workflow-specific pages of this Admin guide.

Configuration management

Configuration in FedMS uses the standard Drupal config-management stack:

  • config_devel — modules export their owned config to config/install/ or config/optional/ directories.
  • config_split — splits config between environments (develop, live, test, this_site).
  • config_ignore — ignores changes to certain config (e.g. the site UUID).
  • config_rewrite — applies declarative tweaks to upstream config on install.

For developers, see Developer guide → Config management.

For administrators, the practical implication is:

  • Changes you make in the admin UI are captured.
  • They are exported back to config files on the next config export.
  • On managed SaaS, exports happen as part of the deployment pipeline.

Where the settings live

Settings area Admin URL Owner
Site information /admin/config/system/site-information DevOps
Languages /admin/config/regional/language Content Manager / DevOps
Date and time formats /admin/config/regional/date-time DevOps
Mail transport /admin/config/system/mailer-transport DevOps
ECA settings /admin/config/workflow/eca/settings DevOps / Engineer
Webform settings /admin/config/webform/settings Content Manager
Webform Content Creator /admin/config/webform_content_creator Content Manager
Pathauto /admin/config/search/path/patterns Content Manager
Cron /admin/config/system/cron DevOps
Theme /admin/appearance DevOps

In this section