What this module is for

Use CMS / Configuration when operators need to manage shared CMS variables instead of editing one banner, page, or resource. These variables usually drive reusable theme/design values such as colors, spacing, sizes, shadows, typography, and border radius.

Included units

• List: configuration catalog with search, type filter, GEO preview, country scope, active state, content state, set-active, delete, import, and export actions.
• Detail: modal editor for one configuration record or one version of a variable.
• Global Variables: comparison table that shows admin-configured values next to theme default values and export-ready metadata.
• Import History: import-modal section for restore, revert, delete, clear, imported-key inspection, and pre-import version checks.

When operators usually open this module

• a shared design variable needs to be created or changed
• a configuration should apply only to selected countries
• a draft or new version should become the active published value
• the current admin value must be compared with the theme default
• configuration CSV values need to be imported, exported, restored, reverted, or deleted
• a previous import must be inspected before another CSV is applied

Common confusion

• Status and State are different. Status is the row state, active or inactive. State is the content lifecycle, such as draft or published.
• Casino-facing consumers use active and published values. An active row with draft content is still not enough for casino delivery.
• A base variable can have multiple version keys, for example a base key plus __vN suffixes. Operators usually work with the base variable meaning, while the system stores versioned rows.
• Country scope is metadata. Empty countries means the value is global. Country-specific values override the global value for that country when the casino configuration resolver runs.
• The Global Variables tab is a comparison/export helper. It is not a separate persistence source.