Unlocking TYPO3’s Hidden Gem: The Backend User Section (Doktype 6)

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:

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.

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.

• 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 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.

To solve exactly this pain point, we’ve developed a small, focused extension: EXT: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.

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 to make collaboration seamless.