---
title: "Feature: #104794 - Introduce Site Settings Editor"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:feature-104794-1725980585"
source: "Changelog/13.3/Feature-104794-IntroduceSiteSettingsEditor.rst"
typo3-version: "13.3"
typo3-major: 13
type: "feature"
issue: 104794
forge: "https://forge.typo3.org/issues/104794"
tags: ["Backend", "Frontend", "YAML", "ext:backend"]
rendered: "2026-09-25T23:17:45+00:00"
---

# Feature: #104794 - Introduce Site Settings Editor {#feature-104794-1725980585}

See [forge#104794](https://forge.typo3.org/issues/104794)

## Description {#description}

A new Site Settings editor has been introduced that allows to configure per-site
settings in file:`config/sites/*/settings.yaml`.

The new backend module **Site Management > Settings**
provides an overview of sites which offer configurable settings and makes
them editable based on
[Site Set provided Settings Definitions](https://docs.typo3.org/permalink/changelog:feature-103437-1712062105).

The editor shows a list of settings categories and respective settings. It will
persist all settings into `config/sites/*/settings.yaml`. The module will
only persist settings that deviate from the site-scoped default value. That
means it will only change the minimal difference to the settings set defined
by the active sets for the respective site.

The backend module is currently available for administrators only, but will
likely be extended to be made available for editors in future.

Anonymous (undefined) site settings – as supported since TYPO3 v10 –
will not be made editable, but will be preserved as-is when persisting changes
through the settings editor.

### Categorization {#categorization}

Sets can define categories and settings definitions can reference the category
by ID in order to assign a setting to a specific category.
These definitions are placed in `settings.definitions.yaml`
next to the site set file `config.yaml`.

**EXT:my_extension/Configuration/Sets/MySet/settings.definitions.yaml**

```yaml
categories:
  myCategory:
    label: 'My Category'

settings:
  my.example.setting:
    label: 'My example setting'
    category: myCategory
    type: string
    default: ''

  my.seoRelevantSetting:
    label: 'My SEO relevant setting'
    # show in EXT:seo provided category "seo"
    category: seo
    type: int
    default: 5
```

The settings ordering is defined through the loading order of extensions and by
the order of categories. Uncategorized settings will be grouped into a virtual
"Other" category and shown at the end of the list of available settings.

### Readonly {#readonly}

Site settings can be made readonly. They can be overridden only by editing
the `config/sites/my-site/settings.yaml` but not from within the editor.

The value of the field is displayed in a readonly field in the settings editor.

**EXT:my_extension/Configuration/Sets/MySet/settings.definitions.yaml**

```yaml
settings:
  my.readonlySetting:
    label: 'My readonly setting'
    type: int
    default: 5
    readonly: true
```

### Enumeration of strings {#enumeration-of-strings}

Site settings can provide possible options via the `enum` specifier, that will
be selectable in the editor GUI:

**EXT:my_extension/Configuration/Sets/MySet/settings.definitions.yaml**

```yaml
settings:
  my.enumSetting:
    label: 'My setting with options'
    type: string
    enum:
      valueA: 'Label of value A'
      valueB: 'Label of value B'
```

## Impact {#impact}

Site-scoped settings will most likely be the place to configure site-wide
configuration, which was previously only possible to modify via Constant Editor,
modifying TypoScript constants.

It is recommended to use site-sets and their UI configuration in favor of
TypoScript Constants in the future.