SecurityCustom Domains

Custom Domains

Paid workspaces can connect a workspace-owned subdomain to internalpage viewer links. This lets your team open pages from a familiar URL such as https://docs.example.com/runbook instead of only using the default https://view.internalpage.com/w/example/p/runbook URL.

The default internalpage viewer URL remains available after a custom domain is active. Custom domains change the preferred link that internalpage shows and copies for pages in that workspace.

Requirements

  • The workspace must be on the Founding Team plan.
  • Use a subdomain that you control, such as docs.example.com or internal.example.com.
  • Add the domain in workspace settings before creating the DNS record.
  • The DNS record must point to customers.internalpage.com.

internalpage currently supports exact subdomains. Apex domains and wildcard domains are not supported.

Set up DNS

  1. Open workspace settings.
  2. Add the full subdomain you want to use.
  3. Create a DNS CNAME record for that subdomain.
Type: CNAME
Name: docs
Target: customers.internalpage.com

For docs.example.com, the Name value is usually docs. Some DNS providers ask for the full hostname instead.

After the DNS record resolves, internalpage verifies the hostname and marks it active. Verification can take a few minutes depending on DNS propagation.

When the custom domain is active, page links shown in the dashboard prefer the custom domain:

https://docs.example.com/runbook

The original internalpage viewer URL still works:

https://view.internalpage.com/w/example/p/runbook

The same workspace sharing rules apply on both URLs. Custom domains do not make private pages public, and viewer access is still checked before page content is served.