help.example.com. Domain setup is separate from publishing your Help Center and its articles.
You need an Owner or Admin role, an eligible paid plan, and access to your domain’s DNS settings. Use a hostname you control. The reserved official Protodesk Help Center hostname is permanently bound and does not offer the normal custom-domain controls.
Connect a hostname
- Open Help Center → Customize → Domain.
- Note your existing Help Center URL so you can still reach the site while setup is in progress.
- Enter the hostname under Custom domain, for example
help.example.com. Enter the hostname, not a full article URL or path. - Select Connect domain.
- Copy the DNS records displayed for this connection into your DNS provider’s settings.
Wait for hostname and certificate readiness
Return to the Domain tab and select Refresh after adding the records. Review both the hostname and certificate statuses. The custom address becomes public only after both are active; creating the connection alone is not enough. Protodesk handles certificate provisioning and renewal, but the required DNS records must be correct. DNS changes and validation are not always immediate. Keep the displayed verification records unless your administrator or Protodesk support confirms that they can be removed. When both statuses are active, open the custom HTTPS address and test an article link. Also confirm that Help Center → Home shows the site as live and that the article is published in the language you are opening.Troubleshoot setup
- No custom-domain controls: check your role, plan, and whether this is the reserved official Help Center.
- Invalid hostname: use a hostname such as
help.example.com, without a protocol, path, or article slug. - Already connected: confirm whether that hostname belongs to another Help Center connection. Do not remove another workspace’s connection to resolve this without its owner’s agreement.
- Hostname or certificate pending: compare every DNS name, type, and value against the displayed records, then refresh. Check for conflicting records with your DNS administrator.
- Provisioning unavailable: retry later or contact Protodesk support. This can require service configuration rather than a content change.
- Certificate warning: stop and resolve the certificate state. Do not ask customers to bypass the warning.
