Study guide · Backend Users and TSconfig

Who may do what in the backend? Users, permissions, TSconfig and editorial tools

As of November 15, 2026 · TYPO3 14.3 LTS · about 23 min read

A good backend shows each person exactly what they need and protects the rest. You set up the editorial team of a music school: groups, page permissions, mounts and user TSconfig. After that you get to know the team's tools: the rich text editor, the page tree, the dashboard and internal notes.

The example: Lindenau Music School

The integrator Mara builds the website of Lindenau Music School with TYPO3 14.3. Its site package is called lindenau_site. Mara herself is an administrator. These people will also work in the backend:

  • The office maintains all pages, the news and the events.
  • The teachers maintain only the pages of their department, such as piano or strings.
  • The school management should see everything, but nobody except Mara gets admin rights.

All configuration that can live in a file goes into the site package, and so into Git.

Users, groups and administrators

This page is only about backend users, not about the frontend users of the website.

You manage backend users and groups in the module Administration > Users. Up to TYPO3 13 it was called “System > Backend Users”. There you list, filter, create and edit users and groups. With “Switch to user” you log in as another user for testing. Only administrators can open this module.

The records live at the top level of the page tree, the root node with the ID 0. Only administrators may edit records there.

Permissions belong on groups. A backend group bundles what its members may do. A new user then only needs their groups. If you change a group, the change applies to all members at once.

Several groups add up. If a user belongs to several groups, they get the permissions of all groups combined. One group cannot take permissions away from another. If someone should not do something, you simply never grant that permission.

Subgroups help you bundle permissions. On the General tab of a group, you add other groups under “Inherit settings from groups”. The group inherits their permissions and can add its own. Mara creates a base group “Basic rights” this way, which both the office and the teachers include.

Comparing: In the Users module you mark two or more users or groups and compare them side by side. You see permissions, mounts and TSconfig at a glance. This shows why one teacher may do something and her colleague may not.

Administrators may do everything in the backend. Groups, page permissions and mounts do not apply to them. They see all modules, all fields and the whole page tree.

What a group can allow

TYPO3 has four tools for backend permissions: access lists, mounts, page permissions and user TSconfig. You set all of them on groups, and all of them add up across several groups.

In TYPO3 14 the group form spreads the access lists over two tabs. The Record Permissions tab contains:

  • Under “Table permissions” you choose, for each table, no access, read, or read and write.
  • Under “Allowed fields” you allow exclude fields. These are fields marked as exclude in TCA. Non-admins only see them after this permission. The list used to be called “Allowed excludefields”.
  • Under “Allowed page types” you define which page types the group may create. Without “Standard”, the group cannot create normal pages.
  • Under “Explicitly allow field values” you allow, for example, single content types.
  • Under “Limit to languages” you restrict the group to certain languages.

The Module Permissions tab holds the “Allowed modules”, that is the backend modules the group sees. It also holds the “Allowed dashboard widgets” and further module options. Backend colors or servers are not controlled by the access lists.

Page permissions

Every page has three parties with their own permissions, similar to files on Unix:

  • the owner, a backend user,
  • the group, a backend group,
  • and everybody else among the backend users.

Each of the three can get five permissions: show page, edit page, delete page, create new subpages and edit content. Translating or hiding a page in the frontend are not page permissions. Language permissions and the page fields handle those.

You set page permissions in the module Administration > Permissions, which was “System > Permissions” up to TYPO3 13. It shows owner, group and permissions for each page. Using the depth selector, you also change them recursively for whole branches. This module is also for administrators only.

For new pages, page TSconfig offers TCEMAIN.permissions. With it you define the owner, the group and their permissions for every newly created page.

TCEMAIN.permissions {
  groupid = 3
  user = show, edit, delete, new, editcontent
  group = show, edit, new, editcontent
  everybody = show
}
Page TSconfig in the site package. New pages belong to the group with the ID 3, which is the office group. The owner gets all five permissions, the group may show, edit, create subpages and edit content, and everybody else may only show the page.

Without this setting, a new page belongs to the user who creates it and to their first group. By default the group may then do everything except delete.

DB mounts: which part of the tree is visible

A DB mount is a starting point in the page tree. The user sees only this page and its subpages, and the rest stays hidden. In the group form the field sits on the Mounts tab, and in TYPO3 14 it is labelled “Page Tree Entry Points” there. Without at least one DB mount, a user cannot work with any page.

Mara gives the group “Piano teachers” a DB mount on the page “Piano department”. The piano teachers now see a small tree instead of the whole website.

You usually maintain DB mounts on the group. You can add further mounts on the user. Whether the user also gets the mounts of their groups is controlled by the option “Mount from groups” on the user. It exists separately for DB mounts and file mounts. If it is off, only the mounts on the user record apply.

A mount alone is not security. It simplifies the tree, but it does not decide what someone may do. In addition, the page permission “show page” must be present. Without it, the page does not appear in the tree despite the mount. That is why the security guidelines recommend always setting page permissions properly as well.

May the teacher edit content here? 1 DB mount Page lies in her part of the tree missing not in tree yes 2 Page permission “Show page” missing invisible yes 3 Page permission “Edit content” missing view only yes 4 Table permission tt_content Read and write missing view only yes Edit content Admins need none of these steps.
Only all four conditions together allow editing content.

User TSconfig: adapting the backend per user

User TSconfig uses the same syntax as TypoScript. However, it does not control the frontend, but the backend of a user or a group: options, defaults and allowed functions. Frontend users have no user TSconfig.

Where it lives: The record of a group or user has a field TSconfig on the Options tab. What you enter there on a group applies to all members. Better than a long text in the field is importing a file from the site package.

@import 'EXT:lindenau_site/Configuration/TsConfig/User/sekretariat.tsconfig'
Content of the TSconfig field of the office group. A single import line loads the file sekretariat.tsconfig from the site package lindenau_site.

Since TYPO3 14.2 you can do without the import line. An extension registers prepared files in the TCA overrides through the class ExtensionManagementUtility. The method registerUserTSConfigFile() is for users, and registerUserGroupTSConfigFile() is for groups. The files then appear for selection on the Options tab under “Include static TSconfig”.

For all users, TYPO3 has automatically loaded the file user.tsconfig in the Configuration folder of every extension since version 13. Mara puts defaults there, which groups and users adjust further.

The order decides who wins:

  1. First come the user.tsconfig files of the extensions.
  2. Then come the groups, in the order in which they are listed in the Group field of the user, from top to bottom.
  3. Last comes the TSconfig on the user record itself.

Later values override earlier ones. So a group further down beats a group further up, and the user beats all groups.

Who wins in user TSconfig? Extensions Configuration/user.tsconfig Group A listed first on the user = 1 Group B listed below it = 5 User TSconfig field of the user later ones override Result: 5, the last value wins
User TSconfig is evaluated from top to bottom, and the last value wins.

The most important top-level objects in user TSconfig are:

  • With options you control backend features, such as the page tree or the search.
  • With setup you preset or lock values of the user settings.
  • With admPanel you configure the Admin Panel.
  • With auth you control the login, for example making multi-factor authentication mandatory.
  • With page you override values from page TSconfig.
  • With TCAdefaults you set default values for new records.

The names config and plugin, on the other hand, belong to frontend TypoScript.

Overriding page TSconfig per group: A property with the prefix page and a dot replaces the value from page TSconfig. This way only the teachers group creates new pages as hidden:

page.TCAdefaults.pages.hidden = 1
User TSconfig of the teachers group. Under page, the default value of the hidden field for new pages is set to 1. So new pages of this group start out hidden, whatever the page TSconfig says.

This way you reach everything in page TSconfig, such as page.TCEFORM or page.mod. You can only replace values here, not extend them.

Checking: The final user TSconfig of the logged-in user is shown in the module System > Configuration from the extension lowlevel. Only admins can use this module. Combined with “Switch to user”, Mara checks the TSconfig of a teacher this way.

User settings and live search

Every backend user has personal user settings, such as language or start module. The top-level object setup lets you step in:

  • With setup.default you set defaults that the user may change.
  • With setup.override you enforce a value that the user cannot change.
  • With setup.fields you hide or lock single fields of the user settings.
setup.default.startModule = dashboard
setup.override.emailMeAtLogin = 1
User TSconfig. The first line suggests the dashboard as start module. The second line enforces that the user gets an email on every login.

Both have a catch: the values end up in the stored user settings.

setup.default only works on empty settings. TYPO3 only applies the defaults when a user has no settings yet, that is, at their first login. So existing teachers will not notice a new start module set with setup.default. Mara reaches them with setup.override or by resetting the settings, in the Install Tool under Maintenance with “Reset Backend User Preferences”.

setup.override sticks. TYPO3 writes the enforced value into the user settings. If Mara removes the line again, the value stays there. It only changes when the user changes it or the settings are reset.

The live search at the top of the backend finds pages and records. Since TYPO3 14.2 you define with options.liveSearch.actions what a click on a result does. The allowed values are edit for the edit form, layout for the Layout module, list for the record list and preview for the frontend preview. The action layout only exists for pages and tt_content.

options.liveSearch.actions.tt_content.default = layout
User TSconfig. A search result for a content element, that is the table tt_content, opens the Layout module by default instead of the edit form.

The rich text editor

In TYPO3 14 the standard editor for formatted text is CKEditor 5, integrated by the system extension rte_ckeditor. Its configuration lives in YAML files, the presets.

The configuration has three layers, which work independently of each other.

Three layers of the rich text editor 1 Editor YAML preset toolbar, plugins, allowed HTML 2 Saving transformation cleans HTML on its way to the database 3 Output parseFunc renders in the frontend, keeps stored HTML unchanged Backend: layers 1 and 2. Frontend: layer 3.
Three layers: what the editor allows, what is stored and how it is rendered.
  • The editor shows the toolbar and plugins and only allows certain content. The YAML preset controls this.
  • The transformations are part of the TYPO3 Core. They clean the HTML when saving to the database and when loading it into the editor.
  • The output in the frontend is controlled by the TypoScript function parseFunc. It does not change the stored HTML.

When the editor appears: A text field only gets the editor if the option enableRichtext is set to true in its TCA. The field name does not matter.

Presets: TYPO3 ships the presets default, minimal and full. Your own preset is a YAML file that you register under a name. You do this in the file ext_localconf.php of the site package:

$GLOBALS['TYPO3_CONF_VARS']['RTE']['Presets']['lindenau']
    = 'EXT:lindenau_site/Configuration/RTE/Lindenau.yaml';
PHP in ext_localconf.php. The preset lindenau is registered among the RTE presets of the global configuration. It points to the file Lindenau.yaml in the folder Configuration RTE of the site package.

Choosing a preset works with page TSconfig. RTE.default.preset applies to all fields that do not set their own preset in TCA. With RTE.config plus table and field, you choose a preset for a single field. With the addition types and the content type, you choose it for one type only. The more specific value wins.

RTE.default.preset = minimal
RTE.config.tt_content.bodytext.preset = lindenau
RTE.config.tt_content.bodytext.types.textmedia.preset = full
Page TSconfig with three levels. First line: all fields use the preset minimal. Second line: the field bodytext of tt_content uses the preset lindenau. Third line: only in the content type textmedia does bodytext get the preset full.

Custom plugins: CKEditor 5 plugins are JavaScript modules. The preset loads them in the list importModules. After that you add their tools to the toolbar.

editor:
  config:
    importModules:
      - { module: '@lindenau/site/notenzeichen.js', exports: ['Notenzeichen'] }
    toolbar:
      items: [bold, italic, link, '|', notenzeichen]
Excerpt from Lindenau.yaml. Under editor, config and importModules, the preset loads the JavaScript module notenzeichen from the site package. After that, the button notenzeichen appears in the toolbar.

The page tree

The page tree on the left of the backend shows the structure of all pages. The frontend menus usually come from this structure too: the MenuProcessor or the TypoScript object HMENU reads pages and their order from the tree. Pages with the option “Hide in menu” are left out.

In the tree you work like this:

  • Context menu: A click on the icon of a page, or a right-click, opens the context menu. There you find, for example, edit, copy, hide or the history.
  • New page: Above the tree there is a bar with page types. You drag a type with the mouse to the desired place in the tree.
  • Moving and copying: You also drag existing pages to a new position with drag and drop.
  • Filter: The search field filters the tree by title, navigation title or page ID.

Since TYPO3 14.1 the filter also finds pages through their translations. If the office searches for the English title “Piano lessons”, the tree shows the German page “Klavierunterricht”. With the user TSconfig option options.pageTree.searchInTranslatedPages you switch this off for single groups.

The dashboard

The dashboard is a backend module made of widgets, small tiles with information. Examples are security notes, recently changed pages or news from an RSS feed. It is the first module in the menu, so it opens after login if no other start module is chosen.

Your own dashboards: Every user can have several dashboards. They create a new one with the plus sign and choose a preset, that is a template with predefined widgets. They switch between dashboards with tabs.

Which widgets are allowed: Administrators have access to all widgets. Other users only see the widgets that one of their groups allows on the Module Permissions tab under “Allowed dashboard widgets”. Some widgets, such as the latest backend logins, are reserved for admins entirely.

Dashboards for new users: Which dashboards a new user gets when first opening the module is set in user TSconfig. The option names one or more preset identifiers. Without a value, the preset default applies.

options.dashboard.dashboardPresetsForNewUsers = default, lindenauLehrkraefte
User TSconfig of the teachers group. New users in this group get two dashboards from the presets default and lindenauLehrkraefte.

Widgets for developers: Widgets are registered as services in YAML, in the service configuration of an extension. It holds the identifier, title, widget group, size and options. This lets developers provide their own widgets.

Since TYPO3 14, widgets can also have their own settings per instance. A cog icon on the widget opens them. This way Mara adds the same RSS widget twice, once with the feed of the music association and once with the feed of the town.

Internal notes

The system extension sys_note lets backend users write internal notes. With it, Mara leaves a hint for the office on the page “Registration”, for example. Website visitors never see these notes.

  • Category and color: Every note has a category: Default, Instructions, Template, Notes or To-do. Depending on the category, it appears in a different color.
  • Personal: Without this option, all backend users with access to the page see the note. With the option, only the author sees it.
  • Position: You choose whether the note appears at the top or the bottom of the content area, for example in the Layout module.
  • Widget: sys_note brings a dashboard widget. It lists pages with internal notes and can be limited to one category.

Key points

  • You manage users and groups in Administration > Users. Permissions belong on groups and add up, and no group takes permissions away.
  • Non-admins only see exclude fields after they are allowed under “Allowed fields”.
  • Page permissions exist for owner, group and everybody, set in Administration > Permissions. TCEMAIN.permissions sets the defaults for new pages.
  • A DB mount makes part of the tree visible. Without the page permission “show page”, the page still stays invisible.
  • User TSconfig applies in the order extensions, groups from top to bottom, user. The last value wins.
  • With page and a dot, user TSconfig overrides page TSconfig. System > Configuration shows the result.
  • setup.default only works on empty user settings, and setup.override stays stored after you remove it.
  • CKEditor 5 has three layers: YAML preset, transformation, parseFunc. The more specific preset value in page TSconfig wins.
  • Widgets need permission in the group, and since TYPO3 14 they have their own settings.

Terms

Backend user group
A record that bundles permissions for its members and can inherit other groups as subgroups.
Access lists
The permissions of a group for modules, tables, fields, page types, field values, languages and widgets.
Exclude field
A field marked as exclude in TCA, which non-admins only see after it is allowed.
DB mount
A starting point in the page tree from which a user sees pages.
User TSconfig
Configuration in TypoScript syntax that controls the backend for users and groups.
Preset
A named YAML configuration for the rich text editor.
Widget
A tile with information on the dashboard, registered as a service.
Internal note
A note from the extension sys_note that only backend users see.

As of: November 15, 2026 (TYPO3 14.3 LTS)

Sources:

  • TYPO3 Explained 14.3, chapters Backend user management, Setting up user group permissions and Page permissions
  • TSconfig Reference 14.3, chapters Setting user TSconfig and User TSconfig reference
  • TYPO3 Explained 14.3, chapter Rich Text Editor
  • Documentation of the system extensions dashboard and sys_note, TYPO3 14.3
  • Changelog TYPO3 13 and 14 (Features 101807, 105833, 107036, 107961, 78412, 106828, 107628)
  • Source code TYPO3 14.3 (cms-core, cms-backend, cms-beuser, cms-dashboard, cms-sys-note, cms-rte-ckeditor, cms-lowlevel), checked for the be_groups form fields, the order of user TSconfig, setup.default and setup.override, RTE preset selection and widget permissions
  • Learning objectives TYPO3 CMS Certified Integrator 14 LTS, area Backend Users and TSconfig

This study guide was written with AI and checked against the sources.

Certifications & exams

Which exam comes next?

You can already practise for 51 exams, and 16 are up for a vote. See all certifications with their official information, cast your vote or suggest your exam.

See all certifications