Skip to content
Cook
Documentation Browse

Delivering for clients

Use your own domain for your team

Serve the app your team signs into on a domain you own, such as app.yourbrand.com, so invitations and sign-in links carry your name.

What changes for your team

Your team signs in at your address, for example app.yourbrand.com. Invitation emails, password resets and magic links point there. A session belongs to the host it was created on: signing in at app.yourbrand.com keeps you on app.yourbrand.com.

Connect the domain

  1. Open Agency → Sub-account brand and find App domain. (The Agency tab appears when Agency mode is on in the account menu.)
  2. Type the domain, for example app.yourbrand.com, and press Connect.
  3. Add the DNS records shown at your DNS provider, then press Verify domain.
  4. When it reads “Domain verified — your team can sign in on it.”, invite a teammate: the invitation mail links to your domain.

Once verified, the card shows the domain as Active with “Your team signs in at …” and “Checked every day”, with the time of the last check.

The same rules as the portal domain apply: Cloudflare records stay DNS-only, the domain is checked every day, and the setup list shows the last check.

Connections from your domain

Connecting Google Calendar, Slack and the other integrations from your domain returns to your domain with the connection saved. Nothing in that flow shows the platform’s own address.