Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.This project is not covered by Drupal’s security advisory policy.
Ever wanted to separate the editorial and admin experience to its own domain (or subdomain)? Then this module is for you.
Planned Features
- Supports two domains: One for editing and managing your site, one for viewing
- Permission added to determine which roles are allowed to access the backend domain
- Allow assigning routes to specific domains, and setting a fallback (default) domain for the rest
- Drupal will handle building links based on these routing rules to provide seamless handoffs between management and public-facing domains
Additional Requirements
Supported domains will likely need to be listed in trusted_host_patterns in your settings.php file.
Differences
This module is different from other domain-handling modules in that it does not provide complex separation between content created in either domain. This is intended to provide a way to split the front and backend of a site for the purposes of:
- Security. Protect your management domain behind a VPN or firewall.
- Decoupling. Allow the front end application to exist and take over the display route. But still allow Drupal to handle the content management.
- Cross-site linking. Since Drupal is aware of the routing configuration, any links generated using Drupal's routing system (in views, menus, contextual links, etc) will immediately make use of this structure and switch between the management and public-facing URL structure.
Supporting organizations:
Initial development & ongoing maintenance
Project information
- Project categories: Access control, Content editing experience, Decoupled
- Created by merauluka on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
