Why we built Managing Editor: TYPO3’s missing user management layer

Each ticket represented the same frustrating bottleneck: TYPO3’s all-or-nothing approach to user permissions. You’re either an administrator with system-wide control or an editor with limited access. There’s nothing in between.

The obvious inefficiency for our client highlighted a deeper gap in TYPO3’s architecture that affects teams everywhere.

A missing feature that should be core

User management sits at the top of the list of features TYPO3 really ought to have. As b13’s new Head of Product Development, I’ve been giving some thought to fundamental gaps we might bridge. Other content management systems solved this years ago with role-based hierarchies that let senior editors manage their teams independently.

But Open Source is not about getting everything you want. Core teams have to balance priorities, weigh community opinions, and much of the work happens in people’s free time. As a result, important features can easily be delayed—or disappear altogether.

So we made a decision. If TYPO3 core isn’t going to build the tools teams need, we will. Managing Editor became our first product following this philosophy, addressing real workflow problems while hopefully showing the community what’s possible.

Real teams, real scenarios

Let me walk you through how Managing Editor changes four scenarios that play out constantly in TYPO3 teams.

Built-in guardrails keep everyone safe

The biggest concern we heard from IT departments: “We don’t want to give managing editors access to everything.” They’re absolutely right.

Managing Editor operates within carefully defined boundaries. System administrators determine which user groups become “manageable”—perhaps the News Editor group and Landing Page Editor group, but never the Administrator group. Managing editors can only manage users within these approved groups.

File access works the same way. Administrators define which directories managing editors can assign to new users. The marketing folder might be available, but the system configuration directory can remain off-limits.

Most importantly, managing editors cannot delete user accounts. They can deactivate them, preventing login access while preserving account data, but permanent deletion requires administrator privileges. This prevents accidental data loss while still enabling day-to-day user management.

The user switching feature provides an additional safety check. Before giving someone new permissions, you can switch to their account view and see exactly what they’ll be able to access. Too much? Adjust the user groups. Too little? Add the necessary permissions and verify the setup before it goes live.

A better way forward

Managing Editor addresses the core tension in user management: Teams need flexibility, but systems need security. It provides both by creating a controlled middle layer that empowers editorial teams without compromising administrative oversight.

That client who generated 38 user management tickets last year? Their content managers now independently handle routine user changes. Our agency time gets spent on valuable development work instead of administrative tasks. Their teams work faster, and their IT department focuses on strategic infrastructure instead of password resets.

This is what TYPO3 should offer natively. Until it does, Managing Editor bridges that gap.

If your team struggles with user management bottlenecks,or if you’re tired of turning simple access changes into complex approval processes, Managing Editor might be the solution you've been waiting for.