setup

With this property you can set default values. In case a backend user may override these settings using its User Settings module the default settings will be overridden for this specific backend user. To change the defaults for users with this property only affects new users who did not login yet. It is usually not possible to set new defaults for users who already logged in, at least once. The only way to apply new defaults to existing users is by Reset Backend User Preferences in the Admin tools > Maintenance section of the install tool.

This forces values for the properties of the list below, a user can not override these setting in its User settings module. So, overriding values will be impossible for the user to change himself and no matter what the current value is, the overriding value will overrule it.

On top of being able to set default values or override them, it is also possible to hide fields in the User Settings module, using setup.fields.[fieldName].disabled = 1. You can find the names of the fields in the Configuration module by browsing the "User Settings" array, example:

# Do not show the 'emailMeAtLogin' field to the user in "User Settings" module
setup.fields.emailMeAtLogin.disabled = 1

# And force the value of this field to be set to 1
setup.override.emailMeAtLogin = 1

Format of window title in backend. Possible values:

titleFirst

[title] · [sitename]

sitenameFirst

[sitename] · [title]

Recursive Copy: Enter the number of page sub-levels to include, when a page is copied

Allow file upload directly from file reference fields within backend forms.

Enable Rich Text Editor

Notify me by email, when somebody logs into my account

One of the language keys. For current options see Supported languages, for example dk, de, es etc.

If set, then the hideAtCopy feature for records in TCE will not be used.

Name of the module that is called when the user logs into the backend, for example web_layout, web_list, web_view, web_info, web_ts etc.

Maximum length of rendered record titles in the backend interface. It is used in several places: page tree, edit masks, workspace module, etc.