--- title: "TYPO3 user management solution: Managing Editor by b13" url: "https://b13.com/knowledge/typo3-user-management-solution-managing-editor-by-b13" description: "TYPO3’s biggest workflow killer: waiting days for simple user account changes. Managing Editor fixes this by giving editorial teams controlled user management powers. No more IT tickets for basic access changes!" image: "https://b13.com/fileadmin/_processed_/c/5/csm_ManagingEditor_Sharing_4799adada3.png" date: 2025-09-11 modified: 2026-08-19 lastUpdated: 2026-08-19 --- # TYPO3 user management solution: Managing Editor by b13 [ TYPO3 ](https://b13.com/knowledge/typo3) [ Products ](https://b13.com/knowledge/products) Why we built Managing Editor: TYPO3’s missing user management layer ===================================================================== ![](https://b13.com/fileadmin/_processed_/b/8/csm_florian_ddfab4eb90.jpg)Florian “Flix” Keitgen 11 September 2025 [ RSS Feed ](https://b13.com/rss.xml) Last year, I closed 38 tickets from a single client. Not complex development work or intricate integrations—just user management requests. *Can you create a new user for our intern? Can you change access rights for our content manager? Someone left last month. Can you disable their account?* Every single request had to flow through either their IT department or agency (us). **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. ### The new intern It’s Monday morning. Your content team just hired an intern for the summer, who needs access to create landing pages without touching the news section or main navigation. Start a ticket, email IT, explain the requirements, wait for implementation. Best case? You lose a day. Worst case? The intern sits idle for a week or more while approvals move through bureaucratic channels. **With Managing Editor, your intern starts working immediately**. Your chief editor opens TYPO3, clicks “New Editor,” assigns the appropriate user group, sets file access permissions, and sends login credentials. Total time: five minutes. ### The departing employee Someone gives notice. They’ll finish their projects through month-end, but security protocols require access termination on their last day. Previously, this meant remembering to submit a ticket, hoping IT processes it promptly so the request doesn’t get lost in rotation. **Managing Editor lets you set automatic deactivation dates.** Schedule the account to disable itself when employment ends. No manual follow-up required, no security gaps, no forgotten accounts lingering in the system. ### The permission evolution Your part-time editor started out handling only product pages, but they’ve proven capable of managing news content. You want to expand their responsibilities without creating security risks. The traditional approach involves explaining current permissions, detailing desired changes, and waiting for implementation. **With Managing Editor, you modify their user group assignments directly.** Add the news user group, verify their new access, and they’re ready to get back to work.. ### The oversight problem How many editors does your team actually have? Who has access to what? When did Sarah leave, and does she still have system access? Without centralized visibility, these questions require admin intervention or guesswork. **Managing Editor provides a complete dashboard of your team’s user accounts.** See active editors, review permissions, identify time-limited accounts, and spot security gaps. The visibility alone prevents most access-related problems before they occur. 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. More Info ----------- *Managing Editor is available for TYPO3 v12 and v13 for €999 (excluding VAT).* [ Learn more about features, implementation, and pricing ](https://b13.com/products/managing-editor-for-typo3) ### Written by: ![Bild von Florian Keitgen](https://b13.com/fileadmin/_processed_/b/8/csm_florian_fc8286b2b4.webp) Head of Product Development Florian (aka Flix) drives projects and products forward – precisely, reliably and always with a dash of dry humour. Florian “Flix” Keitgen Head of Product Development [ more from Florian “Flix” Keitgen ](https://b13.com/team/florian-keitgen) Related Articles ------------------ - ![Cartoon trophy character surrounded by hands giving thumbs up and a heart gesture, set against a gear-patterned background.](https://b13.com/fileadmin/_processed_/f/7/csm_T3ppy_Design_Kit_Headerbild_b51eb9dc31.webp) ### T3ppy Gives TYPO3 a Friendly Face 06 August 2026 | Florian “Flix” Keitgen TYPO3 is powerful—but it doesn’t have to feel impersonal. Meet T3ppy, our friendly companion for the backend. [ Read more: T3ppy Gives TYPO3 a Friendly Face ](https://b13.com/knowledge/t3ppy-design-kit) - ![Gavel labeled "AI" on a circuit-patterned background with yellow stars, symbolizing regulation or legislation related to artificial intelligence in the EU.](https://b13.com/fileadmin/_processed_/1/0/csm_EUAIAct_Headerbild_510724b3de.webp) ### AI Content in TYPO3: Labelling Needs Accountability 02 August 2026 | Benni Mack The EU AI Act brings the origins of AI-generated content into focus. AI Label marks AI-generated and AI-edited content in TYPO3 and records who signed off the published version—for… [ Read more: AI Content in TYPO3: Labelling Needs Accountability ](https://b13.com/knowledge/ai-content-in-typo3-labelling-needs-accountability) - ![A series of stylized figures in various poses, each with a distinctive orange hat, depict a progression from walking to standing still while looking at a phone, set against a purple grid background.](https://b13.com/fileadmin/_processed_/d/7/csm_QueuesDDEV_Headerbild_f640931350.webp) ### Better scalability with decoupled queues: How to set up RabbitMQ with TYPO3 10 April 2024 | Jochen Roth When built-in message transports hit their limits, RabbitMQ can provide TYPO3 with a scalable, robust message queue. [ Read more: Better scalability with decoupled queues: How to set up RabbitMQ with TYPO3 ](https://b13.com/knowledge/better-scalability-with-decoupled-queues-how-to-set-up-rabbitmq-with-typo3) - ![A cartoon character resembling a shield gives a thumbs up in front of a computer interface with various menu options.](https://b13.com/fileadmin/_processed_/e/6/csm_Header_cda1f80173.webp) ### Meet T3ppy: A New Era for Editorial Work in TYPO3 01 April 2026 | Florian “Flix” Keitgen T3ppy and the AiM extension bring AI directly into the TYPO3 backend—enhancing SEO, content quality, and workflows with centralized control. [ Read more: Meet T3ppy: A New Era for Editorial Work in TYPO3 ](https://b13.com/knowledge/meet-t3ppy-a-new-era-for-editorial-work-in-typo3) - ![Retro microphone illustration with a shopping cart icon in the background, symbolizing e-commerce or online shopping.](https://b13.com/fileadmin/_processed_/f/8/csm_Marketplace_Headerbild_ee1575614c.webp) ### Why TYPO3 Needs a Marketplace for Products 25 March 2026 | Florian “Flix” Keitgen A marketplace would make TYPO3 products more discoverable, easier to compare, and benefit both agencies and clients alike. [ Read more: Why TYPO3 Needs a Marketplace for Products ](https://b13.com/knowledge/why-typo3-needs-a-marketplace-for-products) - ![A hand holding a magnifying glass over a laptop screen displaying a webpage with an image and text elements.](https://b13.com/fileadmin/_processed_/e/5/csm_BackendUserSection_Headerbild_6093c842fd.webp) ### Unlocking TYPO3’s Hidden Gem: The Backend User Section (Doktype 6) 05 March 2026 | David Steeb Discover TYPO3’s underrated doktype 6 (Backend User Section) for secure internal previews, editor training, and prototyping. Learn real use cases, common pitfalls like 403 errors… [ Read more: Unlocking TYPO3’s Hidden Gem: The Backend User Section (Doktype 6) ](https://b13.com/knowledge/backend-user-section-in-typo3-uses-pitfalls-helper) - ![Multiple hands hold QR codes while one hand uses a magnifying glass to examine a larger QR code in the center.](https://b13.com/fileadmin/_processed_/0/1/csm_QRcodeManagement_Headerbild_5d9ec54194.webp) ### Why we built QR codes into TYPO3: Bringing print campaigns under CMS control 12 February 2026 | Jochen Roth QR codes generated outside your CMS break when pages move. TYPO3 v14.1 brings QR code management into the backend. Create, track, and retarget from one place. [ Read more: Why we built QR codes into TYPO3: Bringing print campaigns under CMS control ](https://b13.com/knowledge/qr-codes-in-typo3-bringing-print-campaigns-under-cms-control) - ![Two stylized web page designs featuring a user profile, image placeholders, and text sections, set against a light blue background.](https://b13.com/fileadmin/_processed_/2/0/csm_BackendPreview_Headerbild_b4c5799cfa.webp) ### Backend Previews With a System—Why We Built EXT:backendpreviews 09 February 2026 | David Steeb EXT:backendpreviews brings structure and consistency to content previews in the TYPO3 backend using Fluid templates, layouts, and partials. [ Read more: Backend Previews With a System—Why We Built EXT:backendpreviews ](https://b13.com/knowledge/backend-previews-with-a-system-why-we-built-extbackendpreviews) - ![A human hand shakes a robotic hand against a purple background with heart patterns, symbolizing collaboration between humans and technology.](https://b13.com/fileadmin/_processed_/6/2/csm_AIbotsLoveMarkdown_Headerbild_72fe5820d6.webp) ### The Internet Is No Longer Just for Humans—AI Bots Love Markdown 28 January 2026 | Benni Mack Discover why most web traffic is now automated and how TYPO3’s structured content model prepares websites for humans, editors, and AI systems. [ Read more: The Internet Is No Longer Just for Humans—AI Bots Love Markdown ](https://b13.com/knowledge/the-internet-is-no-longer-just-for-humans-ai-bots-love-markdown) - ![Several colorful web page mockups stacked together, showcasing different layouts and design elements against a purple background.](https://b13.com/fileadmin/_processed_/e/3/csm_CaminoTheme_Headerbild_d082598009.webp) ### Camino—The Need for a Default Theme in TYPO3 Is Real 27 January 2026 | Benni Mack With TYPO3 v14, Camino introduces a default theme that removes friction from first installs. Why this matters—and how TYPO3 laid the groundwork. [ Read more: Camino—The Need for a Default Theme in TYPO3 Is Real ](https://b13.com/core-insights/blog/camino-the-need-for-a-default-theme-in-typo3-is-real)