Cook.ai
Documentation Browse

Delivering for clients

Use your own domain for the client portal

Serve the client portal on a domain you own, such as portal.yourbrand.com, with the sign-in screen included.

What changes for your clients

Your clients sign in and work at your address, for example portal.yourbrand.com. Invitations, shared deliverables and intake forms link to that address. The sign-in screen shows your logo and product name.

Before you start

  • White-label is on (Settings → General → White-label).
  • You can add DNS records at the company that hosts your domain (your registrar or DNS provider).

Connect the domain

  1. Go to Settings → General → White-label and find Portal domain.
  2. Type the domain you want, for example portal.yourbrand.com, and press Connect.
  3. Two DNS records appear, with Host, Type and Value. Add both at your DNS provider. The first points the domain at Cook; the second proves the domain is yours.
  4. Press Verify domain. New DNS records can take a few minutes to be visible; press it again if the first check fails.
  5. When it reads “Domain verified — your portal is live on it.”, you are done.

Using Cloudflare? Set the record to DNS-only (the grey cloud), not proxied, and do not add an AAAA record.

After it is verified

Cook checks the domain every day and shows the time of the last check. If the records disappear, the portal falls back to its Cook address and the workspace owner is told, so nobody is locked out.

The setup list at the top of the White-label section shows the domain and when it was last checked.