Study guide · Backend account and permissions

Your backend account, secure passwords and user permissions

As of November 17, 2026 · TYPO3 14.3 LTS · about 21 min read

Before you edit a single page in TYPO3, you log in with your own account. On this page we follow Lena, an editor at the Weidenau City Library, and Tom, who looks after the website as its administrator. You learn how to log in and out safely, what helps when something goes wrong, what a good password looks like and how the second factor works. Afterwards you understand why Lena sees different modules and folders than her colleagues.

Logging in to the backend

The backend is the administration interface of TYPO3. Lena usually reaches it at the address of the website followed by typo3, for example weidenau-library.org/typo3. This path can be changed. If it does not work, Tom tells her the correct address.

Access is protected by a login with username and password. If Lena has set up multi-factor authentication, TYPO3 then asks for a second factor, such as a one-time code. Neither the administrator's email address nor a page ID opens the backend.

For the login to work, JavaScript must be enabled in the browser, and TYPO3 needs cookies for the session. If the login box keeps reloading without an error message, broken cookies are often the cause. Deleting the browser cookies then helps.

LOGGING IN TO THE BACKEND 1 · Login form Username and password 2 · Too many failures? 5 within 15 minutes Locked per IP wait until the time no yes 3 · Second factor only if MFA is active TOTP code or recovery code TOTP: 6 digits, new every 30 s Recovery: one use 4 · Backend opens the start module
The way from the login form into the backend.

Too many failed attempts. If Lena mistypes her password too often, TYPO3 locks the login for a while. By default the backend allows 5 failed logins within 15 minutes. For the frontend login the default is 10. Tom can change both values. Lena then sees a message that starts with “The login is locked until”. A date and time follow, and then “due to too many failed login attempts from your IP address”.

The lock applies to her IP address and ends at the time shown. So the account has not been deleted, and the password has not expired. Lena waits and then tries again. Neither a password reset nor deleting the cookies lifts the lock any sooner. Using a colleague's account is no solution either. It breaks the security rules, and nobody can tell any more who changed what.

Maintenance mode. Sometimes the login page says that TYPO3 is in maintenance mode. Then Tom has locked the backend on purpose, for example during an update. As an editor, Lena cannot get around this, not even through a login in the frontend. She asks Tom when she can work again.

Forgotten password

For forgotten passwords the login page offers the link “Forgot your password?”. Creating a new account with the same name or guessing does not help.

  1. Lena selects “Forgot your password?” on the login page.
  2. She enters the email address stored in her account.
  3. She opens the email from TYPO3 and follows the link in it.
  4. She sets a new password that meets the rules of the installation.

She does not need the old password for this. If no email arrives, she first checks her spam folder and the address she typed. If it still does not work, Tom can check three things:

  • The password reset feature is enabled.
  • The account has a valid email address.
  • The TYPO3 installation can send emails.

Whether the website has visible pages or Lena has an avatar image does not matter here.

Logging out safely

TYPO3 keeps the session open as long as Lena is working. Only after a longer period of inactivity, eight hours by default, does TYPO3 end it on its own. So closing the browser tab does not end the session. Reloading or minimising the window does not help either.

This is how to log out properly: Lena clicks her name in the top right corner of the top bar and selects “Logout”. The session ends straight away, and she is back on the login page. This matters most on shared computers, such as the one at the library's issue desk. That way nobody after her can keep using the account.

Secure passwords

The security of the whole website depends on good passwords. A secure password is long and random. It mixes upper case letters, lower case letters, digits and special characters. Names, birthdays and dictionary words, on the other hand, are guessed quickly. A password made of your first name, your year of birth and an exclamation mark is therefore weak.

Well-known patterns are weak too, even when they contain digits and special characters. One example is Summer2026 with an exclamation mark: season, year and punctuation are what attackers try first. A password policy checks length and character types, but not whether a password is random. That part is your own job.

A separate password for every account. When a password is stolen from one service, attackers try it on other services as well. If Lena uses the same password for her mailbox and for TYPO3, a single data leak puts both accounts at risk.

Nobody can remember lots of long passwords. That is what a password manager is for. It stores the passwords encrypted and fills them in when needed. Anyone who gets to your desk can read a sticky note on the screen, a text file on the desktop or an email to yourself.

Passwords are personal. If a colleague asks for Lena's password, she does not hand it over, neither by email nor out loud. Anyone who needs access gets their own account from Tom, with suitable permissions.

The TYPO3 password policy

TYPO3 checks new passwords against a policy. The default policy requires the following:

  • The password has at least 8 characters.
  • It contains at least one upper case and one lower case letter.
  • It contains at least one digit and one special character.
  • It is not the current password.

The policy does not ask for umlauts or spaces. Tom can set stricter rules for the installation.

The last rule applies when you change your password. If Lena enters her current password again as the new one, TYPO3 rejects it. So a change really has to result in a new password.

Spaces when pasting. Since TYPO3 14, the login page warns you when a pasted password has spaces at the beginning or the end. Such spaces easily slip in when you copy from the clipboard. They would then become part of the password. Spaces are not forbidden as such, but an unnoticed space leads to a different password than you intended.

No shared accounts. An agency suggests that all five editors of the library share one account called “redaktion”. Tom advises against it. Changes can then no longer be traced to a person. The shared password spreads widely, and because a change affects everyone, it often does not happen. Personal accounts also allow individual permissions, and extra accounts cost nothing in TYPO3.

The second factor

With multi-factor authentication, MFA for short, Lena needs two proofs when she logs in. She needs something she knows, namely the password. On top of that comes something she owns, for example an app on her smartphone. A stolen password on its own is then no longer enough.

You set up MFA in the user settings on the “Account security” tab. There you find the link “Setup multi-factor authentication”. TYPO3 ships with two methods:

  • TOTP stands for time-based one-time passwords. Lena scans a QR code with an authenticator app, such as Google Authenticator, Microsoft Authenticator or 1Password. The app shows a new six-digit code every 30 seconds. Lena enters this code after her password.
  • Recovery codes are backup codes for emergencies. By default TYPO3 creates eight codes with eight characters each. Each code works only once and does not expire after 30 seconds. Recovery codes can only be activated when another method such as TOTP is already active.

Warning by email. Since TYPO3 14 the backend sends an email when an MFA check for your account fails. This requires active MFA and a valid email address in the account. The second step only comes after the correct password. If Lena gets such an email although she was not working, someone probably knows her password and only failed at the second factor. She changes her password straight away and tells Tom.

The user settings

Lena maintains her own account herself. She clicks her name in the top right corner of the top bar and selects “User Settings”. The user settings have four tabs: Personal Data, Account security, Backend appearance and Personalization. All settings only apply to Lena's own backend. Colleagues do not see any of it, and the frontend of the website stays untouched.

The “Personal Data” tab holds her profile details:

  • Name is the full name shown in the backend.
  • TYPO3 uses the email address for system notifications and for password resets. Without a valid address, “Forgot your password?” does not work.
  • The option “Notify me by email when somebody logs in from my account” sends an email every time somebody logs in with Lena's account. That way she notices if someone else is using it.
  • The avatar is the picture next to Lena's name in the top bar.
  • Under Language Lena picks the language of the backend interface.

Lena cannot change her username here. Tom does that if needed. She cannot choose her groups herself either.

Backend language. Only languages whose language pack is installed are offered. A colleague misses “Polski” in the list. Then the Polish language pack is missing, and Tom has to install it. Whether Polish is a language of the website does not matter here. The site configuration defines the website languages, while each user picks the interface language for themselves.

On the “Account security” tab Lena changes her password and sets up MFA, as described above.

Adjusting look and behaviour

The “Backend appearance” tab controls how the backend looks:

  • Under Color scheme Lena chooses between “Light mode”, “Dark mode” and “Auto detect”. Auto detect follows the setting of the operating system.
  • Under Theme, TYPO3 14 offers the themes Fresh, Modern and Classic. Fresh has been the default since TYPO3 14. A theme only changes the look, not where functions are.
  • “Start up in the following module” sets which module appears after login, for example the dashboard, the Layout module or Media.
  • Here Lena also sets the format of the window title and the first day of the week in calendars.

The “Personalization” tab controls behaviour:

  • “Maximum length of displayed labels”, that is the length of shown titles, sets after how many characters titles in lists are shortened. Allowed values are 10 to 255 characters, and the default is 50. The stored titles stay unchanged.
  • “Allow to directly upload files when editing or creating records” shows a drop zone and a separate upload button in file fields. Lena can then upload an image right while editing, instead of first putting it into the Media module.
  • “Use quick editing for records in the Layout module” is on by default. Since TYPO3 14.2 the Layout module then opens content elements in a side panel. If Lena switches the option off, the full editing form opens instead.
  • “Show hidden files and folders in the Media module” additionally shows files and folders that TYPO3 normally hides. It does not restrict anything.
  • “Recursive copy” sets how many sublevels come along when a page is copied. The default is 0, which copies only the page itself.

Backend users, groups and admins

TYPO3 separates two kinds of users. Website users log in on the frontend, for example for a protected area. Backend users are editors and administrators. Both have their own, separate groups. So a website user group does not grant any rights in the backend.

Not everybody sees the same modules, because Tom grants modules on purpose. That way everyone can focus on the functions they need. Tom usually does not assign permissions one by one, but through backend user groups. When something changes, he adjusts the group once instead of every account.

Permissions add up. A user can belong to several groups at the same time. They then inherit all permissions from all of these groups. No group takes priority, and it is not only the shared permissions that count.

BASE GROUP Base Page tree, dashboard include GROUPS Editorial Pages, content Images folder Events Event records Lena gets the sum of all Page tree, dashboard, pages, content, Images folder, events
Permissions from several groups add up.

Groups within groups. A group can include other groups and take over their permissions. There is often a base group with shared permissions that more specific groups include. Included permissions can only be extended, not reduced.

Administrators. An administrator, admin for short, has unrestricted access to all functions. Groups do not limit an admin's permissions. All other backend users only have the permissions of their groups and of their own account. Only the admin manages groups. Lena cannot change her groups herself.

Nobody should use an admin account for everyday editing. An admin may also change system-wide settings, so mistakes have a wide effect. If the password is stolen, the damage is bigger too. An account with only the permissions you need limits both. If Lena, as an editor, sees the sections Administration or System in the module menu, she has too many permissions and should tell Tom.

What groups grant

In a backend group Tom defines what its members may do. Frontend design and search engine rankings are not part of it. The most important permissions are these:

  • Modules: which modules appear in the module menu.
  • Tables and fields: which kinds of records someone may read or edit, and which fields they see.
  • Element types: which kinds of content elements are allowed.
  • Page mounts: which parts of the page tree someone sees. Since TYPO3 14 the field in the form is called “Page Tree Entry Points”.
  • File mounts: which file areas someone sees in the Media module and in file selectors.
  • Languages: in which languages someone may edit content. The field is called “Limit to languages”.

Language permissions. The library also has English pages. A translator should see all pages but only edit English content. Tom sets up a group with a page mount on the home page and limits it to the language English. An admin account would be too much. A website user group only applies in the frontend. And the backend language in the user settings only changes the interface, not the editing permissions.

The missing pencil. Sometimes Lena sees a content element, but the buttons for editing, hiding and deleting are missing. Then she lacks permissions. Possible reasons are:

  • The element type is not allowed for her group.
  • The element is locked with “Restrict editing by non-Admins”. Then only admins may change it.
  • The right to edit the content of a page belongs to the page. Each page defines what its owner, one group and all other users may do. The owner is usually the person who created the page. If Lena has no content right there, she cannot change anything.

Tom finds out the exact reason.

Key points

  • You log in with username and password, and with MFA also with a second factor.
  • After 5 failed attempts within 15 minutes TYPO3 locks the backend login for your IP address. You wait until the time shown.
  • Forgotten password: “Forgot your password?”, enter your email address, open the link in the email, set a new password.
  • Log out via your name in the top bar and “Logout”. Closing the tab is not enough.
  • The default policy requires at least 8 characters, upper and lower case letters, a digit, a special character and a password other than the current one.
  • TOTP codes change every 30 seconds. The eight recovery codes work once each and only together with another method.
  • You open the user settings via your name. They only apply to your own backend.
  • Permissions from several groups add up. Groups can include other groups.
  • Admins may do everything. For daily work you use an account with only the permissions you need.

Terms

Backend
The administration interface of TYPO3 where editors work on content.
Top bar
The bar at the top of the backend with search, bookmarks and the user menu.
MFA
Multi-factor authentication, a second proof at login next to the password.
TOTP
A time-based one-time password, a six-digit code from an authenticator app that changes every 30 seconds.
Recovery code
A backup code for emergencies that works exactly once.
Password policy
The rules TYPO3 checks for every new password.
Phishing
A fake message that tries to lure you to a foreign site to steal your credentials.
Backend user group
A set of permissions that applies to all its members.
Administrator
A backend user with unrestricted access whose permissions no group limits.
Page mount
The part of the page tree a user may see and edit.
File mount
A file area a user may access in the Media module.
Language pack
The translation of the backend interface into one language, installed by the administrator.

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

Sources:

  • TYPO3 Editors Guide 14.3, chapters Login, User Settings and Logout
  • TYPO3 Explained 14.3, chapters Multi-factor authentication, Security guidelines and Password policies
  • TYPO3 Getting Started 14.3, chapters Backend users and Backend user groups
  • TYPO3 14 changelog (Fresh theme, email on failed MFA attempts, warning about spaces in pasted passwords, quick editing in the Layout module)
  • Source code TYPO3 14.3 (typo3/cms-core, cms-backend, cms-beuser), checked for the password policy, login lock, session length, MFA, user settings and group fields
  • Learning objectives TYPO3 CMS Certified Editor 14 LTS, skills Backend account, Choosing a secure password and About backend users and backend user groups

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