Skip to content

Community on your domain

By default a community lives on a generic address. With a custom domain connected to your project, you can put it on your brand:

community.mysite.com
  • A domain that’s added and active in your workspace (Adding a custom domain), with its SSL certificate issued.
  • The domain connected to the project that owns the community (Connecting to a project).
  • The community activated on that project.
  1. Open Domains → your domain → Projects tab.
  2. Find the project’s mapping row — it has a Community section showing the activation status.
  3. Click Attach community subdomain. The default prefix is community; change it if you like (e.g. members, club).
  4. Confirm. Genesis creates the address and wires it up — it may take a few minutes to go live globally.

Your community is now at community.mysite.com (HTTPS included — the domain’s certificate covers it).

If the project’s site itself sits on a subdomain (say ai.mycompany.com), the community default becomes community-ai.mycompany.com, so several projects’ communities can coexist on one domain without collisions.

In the same Community section of the mapping row:

  • Edit — change the prefix (e.g. communitymembers). The old address stops working, the new one takes over.
  • Detach — remove the community from this domain. The community itself keeps running on its default address; nothing inside it is affected.

Prefixes are validated against your other subdomains — you can’t take a name your site already uses on that domain.

  • A community can be attached to more than one of your domains — each attachment is managed on its own domain’s page.
  • Disconnecting the site’s domain mapping detaches that domain’s community address automatically — the community keeps running regardless.
  • Attach is disabled until the domain is fully active with an issued certificate — finish domain setup first.