Master this essential documentation concept
The ability to rebrand a platform with a customer's own domain name and branding, making it appear as the customer's own product to end users.
White-label and custom domain capabilities are essential features for documentation teams that want to deliver a polished, brand-consistent experience to their readers. Instead of directing users to a generic platform URL like yourcompany.platformname.com, teams can configure their documentation to live at a fully branded address such as docs.yourcompany.com or help.yourproduct.com, making the documentation portal feel like a native part of the product ecosystem.
A SaaS company's API documentation was hosted at a platform subdomain (e.g., mycompany.docsplatform.com), causing confusion among developers who questioned the legitimacy of the URL and creating a disconnect from the main product brand.
Implement custom domain configuration to serve all developer documentation at developers.mycompany.com, complete with the company's brand colors, logo, and navigation patterns that match the main product website.
1. Purchase or designate a subdomain (developers.mycompany.com) in your DNS provider. 2. Access the documentation platform's domain settings and enter the custom domain. 3. Copy the provided CNAME record value. 4. Add the CNAME record in your DNS provider pointing to the platform's servers. 5. Wait for DNS propagation (typically 24-48 hours). 6. Enable automatic SSL provisioning in the platform settings. 7. Upload brand assets (logo, favicon) and configure color scheme to match brand guidelines. 8. Remove all platform-specific branding from headers and footers.
Developers consistently trust and bookmark the branded URL, support ticket volume related to 'suspicious links' drops, and the documentation portal achieves higher SEO rankings as content authority consolidates under the company's primary domain.
A technical writing agency manages documentation portals for 10+ enterprise clients, but each client requires their documentation to appear as their own product — not the agency's tooling — for end users and internal stakeholders.
Use the documentation platform's white-label capabilities to create fully isolated, branded portals for each client under their respective custom domains, with each client's branding, domain, and access controls configured independently.
1. Create separate workspace or project environments for each client in the documentation platform. 2. Collect brand assets (logo, color hex codes, font choices) from each client. 3. Configure each client's designated subdomain (e.g., help.clientA.com, docs.clientB.com). 4. Provide DNS configuration instructions to each client's IT team. 5. Apply client-specific brand themes to each portal. 6. Disable or hide all agency and platform branding. 7. Set up client-specific custom email domains for notification emails. 8. Conduct a brand review with each client before go-live.
Each client receives a documentation portal that appears entirely native to their brand, strengthening the agency's value proposition, enabling premium pricing, and allowing clients to present documentation confidently to their own customers.
A large enterprise is migrating their internal knowledge base from a legacy system to a modern documentation platform, but employees are accustomed to the existing internal URL (wiki.company.com) and any URL change would cause widespread confusion and productivity loss.
Configure the new documentation platform to serve content at the existing internal URL (wiki.company.com) using custom domain mapping, ensuring employees experience zero disruption while the backend infrastructure is modernized.
1. Audit all existing bookmarks and internal links pointing to the old URL. 2. Configure the new documentation platform with wiki.company.com as the custom domain. 3. Set up the DNS CNAME record to point to the new platform (coordinate with IT for internal DNS if applicable). 4. Migrate all content to the new platform during a maintenance window. 5. Implement 301 redirects for any content that changed URL structure. 6. Match the visual styling of the previous system as closely as possible during initial rollout. 7. Gradually introduce new UI improvements after employees adjust to the new system.
Employee adoption rates remain high because the familiar URL is preserved, IT help desk tickets related to 'broken bookmarks' are minimized, and the documentation team successfully modernizes infrastructure without organizational disruption.
A corporation with five distinct product brands needs separate documentation portals for each brand, but managing five separate documentation tools is expensive and operationally complex. Users of Brand A should never see Brand B's documentation or branding.
Use a single documentation platform with multi-portal white-label capabilities, creating five fully isolated branded documentation sites (docs.brandA.com through docs.brandE.com) managed from one administrative backend.
1. Evaluate documentation platforms that support multiple custom domains per account. 2. Create five separate documentation spaces or portals within the platform. 3. Configure unique custom domains for each brand's portal. 4. Apply distinct brand themes, logos, and color palettes to each portal. 5. Set up brand-specific navigation structures and content hierarchies. 6. Configure separate analytics tracking IDs per brand for independent reporting. 7. Assign content editors to their respective brand portals with role-based access controls. 8. Establish a governance process to prevent cross-brand content contamination.
The corporation reduces documentation tooling costs by consolidating to one platform, brand integrity is maintained across all five portals, and the documentation team operates more efficiently with unified workflows while users experience fully isolated branded environments.
Establish a clear, memorable subdomain specifically for documentation before launching your portal. Choosing the right subdomain structure early prevents costly URL migrations later and sets clear user expectations about where documentation lives.
SSL certificates on custom domains must be renewed periodically, and an expired certificate will display security warnings to all documentation visitors, severely damaging user trust and potentially blocking access entirely. Proactive certificate management is a critical operational concern.
White-label documentation should feel indistinguishable from the rest of your product and marketing presence. Inconsistent branding — different fonts, off-brand colors, or mismatched logo treatments — signals to users that documentation is an afterthought, reducing perceived product quality.
DNS Time-to-Live (TTL) settings determine how long DNS records are cached globally. Improper TTL management during custom domain setup or migration can result in hours of downtime or inconsistent access experiences for users in different geographic locations.
Documentation portals on custom domains require their own analytics configuration to capture accurate usage data. Without proper setup, documentation traffic may be misattributed, sessions may be broken by cross-domain tracking issues, or valuable user behavior data may be lost entirely.
Join thousands of teams creating outstanding documentation
Book a Demo