I would like to suggest an option for platform administrators to create a website using a subdomain of a domain that already belongs to another organisation.
A typical example from a managed hosting environment:
- customer-domain.com belongs to Customer A and is hosted as a website in Customer A’s organisation.
- The hosting provider offers an additional centrally managed service, available to the customer at service.customer-domain.com.
- This service is operated and maintained entirely by the hosting provider and should therefore be a website within the hosting provider’s own organisation/subscription.
- The customer’s main website and the managed service may also run on completely different servers in the Enhance cluster.
Currently, Enhance prevents creating service.customer-domain.com in the provider’s organisation with:
Unable to create website outside of the org
I understand the reason for this restriction. A normal customer must obviously not be able to create shop.other-customer.com or any other subdomain of a domain owned by another organisation.
However, as a platform administrator, I think there should be an option to explicitly override this restriction.
There are many possible use cases for this in managed hosting, for example centrally operated:
- consent management systems
- analytics applications
- newsletter systems
- customer portals
- monitoring applications
- other SaaS or managed services
In these cases, assigning the service website to the customer’s organisation is not really appropriate. The service belongs to and is operated by the hosting provider; only its hostname is part of the customer’s domain.
Ideally, this should also retain one of the major advantages of Enhance: automatic DNS management.
For example:
customer-domain.com → Website on Server 1, owned by Customer A
service.customer-domain.com → Website on Server 2, owned by Hosting Provider
If customer-domain.com uses the Enhance nameservers, Enhance could automatically create and maintain the required DNS record for service.customer-domain.com, just as it does for other websites.
The existing restriction could remain unchanged for normal users. I am only suggesting an explicit platform-admin override when creating or assigning such a website.
This would provide a clean separation between domain ownership, website/service ownership and the server hosting the service, while retaining Enhance’s automatic DNS management.
Thanks for considering this.
