Skip to main content

Subdomain Management

Host Admin

DataCentral's multi-tenant architecture allows each Tenant to access the platform through a unique, branded URL. This is critical for providing a seamless, white-labeled experience for your customers or internal business units.

This guide explains how Host Administrators manage subdomains for their Tenants.

1. How Subdomains Work​

When a Host Instance is deployed, it is typically bound to a primary root domain (e.g., datacentral.ai or reports.yourcompany.com).

Every Tenant created within that Instance is then assigned a unique subdomain prefix.

For example, if your root domain is datacentral.ai:

  • Tenant A (Acme Corp) might be assigned acme.datacentral.ai
  • Tenant B (Globex) might be assigned globex.datacentral.ai

When a user navigates to acme.datacentral.ai, DataCentral automatically identifies the Tenant based on the URL, loads Acme Corp's specific branding (logo, colors), and routes the user to Acme Corp's isolated login screen.

2. Assigning a Subdomain​

Subdomains are assigned during the Tenant provisioning process.

  1. In the Host Administration portal, click Add Tenant.
  2. Enter the desired prefix in the Subdomain field (e.g., acme).
  3. The system will verify that the subdomain is unique within your Instance.
  4. Complete the provisioning process.

Note: Subdomains should be short, memorable, and contain only lowercase letters, numbers, and hyphens. Spaces and special characters are not allowed.

3. Changing a Subdomain​

If a Tenant undergoes a rebranding or requests a different URL, a Host Administrator can change their subdomain.

  1. Navigate to Tenants in the Host Administration portal.
  2. Select the Tenant you wish to modify.
  3. Click Edit Tenant.
  4. Update the Subdomain field to the new prefix.
  5. Click Save.

Important Considerations When Changing Subdomains:

  • Broken Links: Any existing links to reports, slideshows, or the login page that use the old subdomain will immediately break.
  • User Communication: You must notify all users in that Tenant of the new URL so they can update their bookmarks.
  • API Integrations: If the Tenant is using the DataCentral REST API, any hardcoded URLs in their applications must be updated to reflect the new subdomain.

4. Custom Domains (Enterprise Only)​

While standard subdomains (e.g., client.yourcompany.com) are sufficient for most use cases, some Enterprise customers or SaaS providers require their Tenants to use completely custom root domains (e.g., analytics.clientcompany.com).

DataCentral supports custom domains, but this requires additional configuration outside of the DataCentral application.

Infrastructure Requirements​

To route a custom domain to a DataCentral Tenant, you must configure your organization's DNS and reverse proxy infrastructure (such as Azure Front Door, Cloudflare, or Nginx).

  1. The Tenant must create a CNAME record in their DNS settings pointing analytics.clientcompany.com to your DataCentral Host Instance (e.g., reports.yourcompany.com).
  2. Your reverse proxy must be configured to accept traffic for analytics.clientcompany.com, terminate the SSL/TLS certificate for that custom domain, and route the request to the DataCentral application servers.
  3. The DataCentral Host Administrator must map the custom domain to the correct Tenant ID in the Host Administration portal.

Note: Managing SSL certificates for hundreds of custom domains can be complex. We recommend using a managed service like Azure Front Door to automate certificate provisioning and renewal.