All help articles
Browse help topics
Workspace and Settings

Request a custom domain for share links

Ask HummingDeck Support to configure a branded subdomain for document and Room links, then complete the provided DNS steps.

Updated August 18, 2026

Examples use sample data. Available controls may vary by plan, role, and product version.

A custom domain changes recipient-facing HummingDeck URLs from the standard host to a branded subdomain such as docs.yourcompany.com.

Plan: Business and abovePermission: Workspace owner

Custom domains are currently configured manually by HummingDeck Support. Do not add or change DNS records until Support sends the records for your workspace.

Product exampleBased on the live Support ticket form

Open a support ticket

Tell us which workspace and branded subdomain you want to connect.

What can we help with?
Bug
Question
Billing
Feature request

Include the workspace, preferred subdomain, DNS contact, and timing. Support will reply with the exact records to add.

Choose the subdomain

Use a subdomain that recipients will recognize, such as docs.yourcompany.com or deals.yourcompany.com. Root domains such as yourcompany.com are not supported.

Before requesting setup, confirm:

  • you or a colleague can edit DNS for the parent domain;
  • the preferred subdomain is not already used by another service;
  • your team knows whether any existing branded links need to keep working;
  • a workspace owner can coordinate the request with Support.

Open a support ticket

In HummingDeck, open Support, start a new question, and request custom-domain setup. Include:

  • the HummingDeck workspace name;
  • the preferred subdomain;
  • your DNS provider, if known;
  • the person who will make the DNS change;
  • your preferred setup date;
  • whether this replaces an existing custom domain.

The custom-domain article inside your workspace opens a prefilled ticket so you only need to add these details.

Wait for the DNS instructions

Support checks the workspace and domain, then replies with the exact DNS records required for routing and verification. Add those records with your DNS provider and reply to the same ticket when they are in place.

Do not reconstruct records from another workspace or an older setup. Hostnames and verification values can differ.

Let Support complete the setup

Support verifies the DNS records, completes routing, and provisions SSL. DNS and certificate changes are not always immediate, so wait for confirmation before sharing recipient links on the new domain.

If the records cannot be verified, send Support a screenshot or copied view of the DNS entry. Remove account identifiers, unrelated records, and any secret values before attaching it.

Test the recipient experience

After Support confirms that the domain is active:

  1. Open a document link on the custom domain in a private browser window.
  2. Open a Room link on the custom domain.
  3. Test the access mode you normally use.
  4. Check downloads and any HTML content you plan to share.
  5. Confirm that the browser shows no certificate warning.

Change or remove a domain

Open a Support ticket before changing or removing a custom domain. Existing branded URLs may stop working, so Support can help plan the transition and confirm when replacement links should be sent.