Use your own domain for the client portal

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

• Your plan includes white-label (the first row of the White-label setup list).
• You can add DNS records at the company that hosts your domain (your registrar or DNS provider).

Connect the domain

1. Open Agency → Portal white-label and find Portal domain. (The Agency tab appears when Agency mode is on in the account menu.)
2. Type the domain you want, for example portal.yourbrand.com, and press Connect.
3. Two DNS records appear, with Type, Host and Value: an A record and a TXT record. Add both at your DNS provider. The A record points the domain at Cook; the TXT record proves the domain is yours. There is no CNAME.
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

The card reads “Your portal is live at … — new invites use it automatically.” 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 Portal white-label shows the domain and when it was last checked.