--- title: "Unlock TYPO3 Doktype 6: Backend User Sections Made Easy + Our New Extension" url: "https://b13.com/knowledge/backend-user-section-in-typo3-uses-pitfalls-helper" description: "TYPO3’s Backend User Section (doktype 6) is perfect for hidden previews and internal examples—but sharing links often fails with 403 errors. See practical use cases from b13 and how EXT:backend_user_section_login turns frustration into seamless collaboration." image: "https://b13.com/fileadmin/_processed_/f/b/csm_BackendUserSection_Sharing_654da1fbc2.png" date: 2026-02-12 modified: 2026-08-19 lastUpdated: 2026-08-19 --- # Unlock TYPO3 Doktype 6: Backend User Sections Made Easy + Our New Extension [ TYPO3 ](https://b13.com/knowledge/typo3) [ Tool-Tip ](https://b13.com/knowledge/tool-tip) Unlocking TYPO3’s Hidden Gem: The Backend User Section (Doktype 6) ==================================================================== ![](https://b13.com/fileadmin/_processed_/a/d/csm_david_5ce18d41e2.jpg)David Steeb 05 March 2026 [ RSS Feed ](https://b13.com/rss.xml) ![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_6317d795f5.webp) In the vast TYPO3 page tree, some features quietly exist for years, waiting for the right moment to shine. One such underrated tool is the page type **“Backend User Section”** (doktype 6). Introduced early in TYPO3’s history and still fully supported today, it offers a clean, secure way to host content that’s meant exclusively for backend users—without cluttering your public site structure or requiring complex workarounds like frontend logins or hidden subtrees. What Exactly Is a Backend User Section Page? ---------------------------------------------- In TYPO3, every page has a **doktype** that defines its behavior. The most common is doktype 1 (Standard page), which renders publicly. Doktype 6, however, is different: - It renders **only for authenticated backend users** with the necessary permissions. - Direct frontend access (even with the exact URL) returns a **403 Forbidden** error. - The page behaves like a normal content page in the backend—you can add content elements, use backend layouts, Fluid templates, TypoScript conditions, and extensions as usual. - Previewing works via the familiar “View” or “Preview” button in the page module, showing the full frontend-styled output. For quick comparison: | **Doktype** | **Name** | **Frontend Accessibility** | **Typical Use** | |---|---|---|---| | 1 | Standard | Public | Main website content | | 3 | Link | Redirects | External linking | | 4 | Shortcut | Redirects | Internal linking | | 6 | Backend User Section | Backend users only (preview) | Internal examples, prototypes, training | | 7 | Mount Point | Depends on mounted page | Tree restructuring | | 199 | Divider | No frontend rendering | Used to add separation for menus for example | | 254 | Folder (Sysfolder) | No frontend rendering | Data storage (records, not pages) | | 255 | Recycler (deprecated) | Migrated to doktype 6 | Was: soft-deleted content | In short: doktype 6 gives you a full frontend-rendered page that’s **secure by default**—perfect when you want the look and feel of the live site without any risk of public exposure. Real-World Use Cases We Love at b13 ------------------------------------- Here are practical scenarios where doktype 6 pages save time and reduce complexity: 1. **Editor Training & Living Style Guides** Create a small subtree of doktype 6 pages under your root to showcase content elements in action: a teaser carousel here, an accordion there, a custom plugin demo on another. Editors can explore real frontend output without touching live pages or needing a separate staging environment. 2. **Component & Layout Prototyping** Developers and designers prototype new sections, A/B variants, or responsive behaviors. Because the pages render with your full TypoScript and templates, you see exactly what the production version would look like—without indexing or caching side effects. 3. **Internal Documentation & Cheat Sheets** Render help pages, onboarding guides, or brand guideline examples using the same design system as the live site. Team members access them via backend preview, keeping everything consistent and up-to-date. 4. **Safe Testing Grounds** Test new extensions, content blocks, or integrations on isolated pages that won’t affect SEO, performance, or visitor experience. 5. **Archived / Review Content** Post-v13, use doktype 6 naturally for reviewing migrated recycler content or keeping old campaign pages available for internal reference. These cases avoid the overhead of separate page trees behind FE logins or sysfolders that don’t render frontend output. Day-to-Day Tips for Working with Doktype 6 -------------------------------------------- - Organize them in a dedicated subtree (e.g., “Internal / Examples”) to keep the main tree clean. - Use Page TSconfig to customize: restrict editing to certain groups, change icons, or auto-apply backend layouts. - Combine with workspaces for versioned internal changes. - Grant granular permissions via backend user groups—editors see only what they need. - No SEO or performance impact: these pages are excluded from routing, sitemaps, and search engine indexing by default. The Annoying Pitfall Everyone Hits (and How We Fixed It) ---------------------------------------------------------- The biggest frustration? **Sharing links**. You create a beautiful example page, copy the preview URL, send it to a colleague in a Jira ticket, email, or chat—and they hit a plain 403 error page with no context or next steps. The only workaround is to: 1. Open the TYPO3 backend separately. 2. Navigate the page tree to find the page. 3. Click “Preview” or “View”. This breaks quick feedback loops, especially in distributed teams or when onboarding new editors. Doktype 6 enforces this strict check intentionally (great for security), but it creates friction in daily collaboration. We’ve seen teams fall back to less secure alternatives (hidden standard pages, FE-group protected trees) just to avoid this hassle. Our Solution: EXT:backend\_user\_section\_login ------------------------------------------------- To solve exactly this pain point, we’ve developed a small, focused extension:[ **EXT:backend\_user\_section\_login**](https://github.com/b13/backend-user-section-login). When a visitor requests a doktype 6 page (or any page in its subtree) without an active backend session, the extension intercepts the request before TYPO3 throws the 403. Instead of an error, it displays a **login prompt that mirrors your TYPO3 backend login screen**—including your custom logo, highlight color, background image, footnote, and any custom stylesheets (even those from` $GLOBALS[‘TYPO3_CONF_VARS’][‘BE’][‘stylesheets’]` or `ext_tables.php` registrations). The prompt feels familiar and trustworthy (no scam-like “log in here” vibes). It links directly to the TYPO3 backend login (`/TYPO3/`). After successful authentication (including MFA and rate limiting), a visibilitychange listener automatically reloads the original page. The `be_typo_user `session cookie is now present, so TYPO3 renders the content normally—no manual navigation needed. **Key technical highlights:** - Uses a PSR-15 middleware that runs after backend authentication checks but before page access denial. - Checks the page rootline for doktype 6. - Reuses TYPO3’s built-in `BackendUserAuthenticator`—no custom auth logic. - Loads backend CSS (backend.css, webfonts.css) and customizations during frontend requests. **Requirements** TYPO3 v13 LTS or v14 (tested and developed in 2026 environments). **Installation** `composer req b13/backend-user-section-login` That’s it. No further configuration required—it activates automatically for all doktype 6 pages. Final Thoughts ---------------- Doktype 6 isn’t flashy, but it’s one of those TYPO3 features that quietly solves real problems once you understand it. Whether you’re building editor training materials, prototyping safely, or just need internal pages that feel like the real frontend, Backend User Sections deserve a spot in your toolkit. Give it a try on your next project: create a doktype 6 page, add some content, preview it—and feel the difference. And if the sharing hurdle annoys you, install [EXT:backend\_user\_section\_login](https://github.com/b13/backend-user-section-login) to make collaboration seamless. **What’s your experience?** Have you used doktype 6 creatively? Or run into other doktype quirks? Contact us—we’d love to hear your experiences and ideas! [ Let’s connect ](https://b13.com/lets-connect) [ Go to GitHub ](https://github.com/b13/backend-user-section-login) ### Written by: ![Bild von David Steeb](https://b13.com/fileadmin/_processed_/a/d/csm_david_cf042ebb7f.webp) b13 Founder and CEO, David, is someone you’ll meet if you’re thinking about working with our agency. He is constantly learning new skills and is an influential part of our cutting-edge frontend practice. David Steeb CEO [ more from David Steeb ](https://b13.com/team/david-steeb) 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) - ![Four file folders displaying a bar graph with orange bars, set against a light blue background with abstract document outlines.](https://b13.com/fileadmin/_processed_/7/2/csm_PageInfoTabs_Headerbild_1e3eda44e5.webp) ### Taming the Page Module Header—Why We Built EXT:page\_info\_tabs 31 March 2026 | David Steeb When multiple TYPO3 extensions add content to the page module header, things quickly become messy. EXT:page\_info\_tabs structures everything into clean Bootstrap tabs, with zero… [ Read more: Taming the Page Module Header—Why We Built EXT:page\_info\_tabs ](https://b13.com/knowledge/taming-the-page-module-header-why-we-built-extpage-info-tabs) - ![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) - ![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) - ![Two interlocking gears with a disconnected electrical plug and a tag labeled "v13" on a purple background.](https://b13.com/fileadmin/_processed_/0/7/csm_TYPO3v13_Headerbild_14eb602ce4.webp) ### What’s New in TYPO3 v13? 20 January 2026 | Desirée Lochner TYPO3 v13 marks the beginning of a new era of user-friendliness. The version impresses with a modern, fresh, and incredibly high-performance user interface—developed for anyone who… [ Read more: What’s New in TYPO3 v13? ](https://b13.com/solutions/typo3/whats-new-in-typo3-v13)