Understand system domains

This reference explains the System Domains (CSV) field shown during server setup. Use it for administration hosts, not for public sites or Storefronts.

In this label, CSV means a comma-separated list of hostnames. The field is not a CSV file upload.

Enter system domains

Enter every hostname that should open the administration interface before a tenant is selected:

text
localhost,workspace.example

Use hostnames only. Omit the scheme, port, path, and trailing slash.

IncorrectCorrect
https://workspace.example/workspace.example
workspace.example/docsworkspace.example
https://workspace.example:443workspace.example

Keep tenant domains separate

A system domain identifies the global administration entry point. A tenant domain belongs to one tenant, is verified through DNS, and can bind to a public site with the cms_public surface.

Host typePurposeConfiguration
System domainAdministration interface before tenant selectionSystem Domains (CSV) during setup; comma-separated hostnames, no file upload
Tenant domainPublic site or Storefront for one tenantTenant-domain registration, DNS TXT verification, and site domain binding

Do not add a Storefront host to System Domains (CSV) as a workaround. For the local Docker path, follow Set up a local storefront domain.

A free Site test address in Workspace Cloud is also a cms_public tenant domain, but Workspace assigns it explicitly from the Site's domain tab. It does not belong in System Domains (CSV). The operator provides the wildcard DNS namespace once; Workspace does not create one DNS record per Site. You do not need to provide a DNS TXT ownership proof for an address assigned this way. The operator declares the owned namespace in the system tenant. Customer-owned domains still require ownership verification. A test address becomes ready only after its route to the assigned server and HTTPS have been checked successfully.

The Docker demo preconfigures its administration URL through NUCLEUS_PUBLIC_URL. You normally do not enter another system-domain list for localhost.alvine.dev during that guided setup.

Verify the result

The configuration is correct when the administration host resolves, its TLS certificate covers the hostname, and Workspace recognizes it as the global administration entry point. Public site hosts remain registered in their business tenants.

For production TLS and proxy configuration, continue with Server installation.