Skip to main content
An already verified domain can be attached to another eligible workspace owned through the same Biqli account. This is an attachment, not a second DNS connection. Biqli checks existing ownership before attaching it. Because the domain is already verified, the DNS records and certificate stay in place, and no new setup email is sent. If the domain belongs to another account, Biqli treats it as unavailable. Contact support if ownership legitimately needs to move between accounts.

​
Attach the verified domain

  1. Switch to the destination workspace.
  2. Start the custom domain connection flow with the same hostname.
  3. Biqli checks existing verified ownership on your account.
  4. Confirm the workspace attachment when offered.
  5. Verify that the domain appears as active and can be selected for a test resource.
Because DNS and the certificate already exist, this flow does not generate a second setup email. Do not change DNS simply because the domain now appears in another workspace.

​
Workspace boundaries still apply

Attaching the hostname does not share links, Biolinks, members, folders, API keys, or analytics between workspaces. Each new resource still belongs to the workspace where it is created, and aliases must remain valid on the hostname. Coordinate alias ownership across workspaces to avoid naming conflicts.

​
Frequently asked questions

​
Does each workspace receive a DNS email?

No. Reattaching an already verified same-account domain does not repeat initial DNS setup.

​
Can another Biqli account attach it?

Not through the reuse flow. Existing ownership must be reviewed before a domain can move between accounts.

​
Are aliases shared?

The hostname must still resolve aliases unambiguously. Coordinate public paths across every workspace using the domain.