# Community on your domain

> Serve your community at community.mysite.com — attach, rename, or detach the community subdomain on any of your custom domains.

Source: https://support.estage.com/community-custom-domain
Part of the ESTAGE Support help center (https://support.estage.com). Full knowledge base: https://support.estage.com/llms-full.txt

---

By default a community lives on a generic address. With a [custom domain](https://support.estage.com/domains) connected
to your project, you can put it on **your** brand, so members see your name in the address bar
from sign-up onwards:

```
community.mysite.com
```

You manage it in Genesis under **Domains → your domain → Connected Projects**.

## Before you start

- A domain that's **added and active** in your workspace
  ([Adding a custom domain](https://support.estage.com/domains)), with its SSL certificate issued.
- The domain **connected to the project** that owns the community
  ([Connecting to a project](https://support.estage.com/domains-connect)).
- The community **activated** on that project.

> **Note**
>
> If the domain was already active when you clicked **Add community**, or the community was already
> activated when you connected the domain to the project, Genesis claims `community.<your-domain>`
> **automatically** — check, it may already be done.

## Attaching manually

1. Open **Domains → your domain → Connected Projects** tab.
2. Find the project's mapping row. Under it, the community line shows its state:
   - **Community not yet activated on this project.** — click **Activate →** to add the
     community first ([Creating a new community](https://support.estage.com/community#creating-a-new-community)).
   - **No community subdomain attached.** — you're ready.
3. Click **Attach community subdomain**. The default prefix is `community`; change it if you
   like (e.g. `members`, `club`).
4. Click **Attach**. 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).

### Naming with multiple sites on one domain

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.

## Renaming and detaching

In the same Community section of the mapping row:

- **Edit** — change the prefix (e.g. `community` → `members`). The new address takes over.
- **Detach** — remove the community from this domain (you confirm it first). The community
  itself keeps running on its default address; nothing inside it is affected.

> **Caution**
>
> Renaming or detaching makes the old address stop working. Links you've shared and members'
> bookmarks that use it no longer reach the community — update them to the new address.

A prefix is 1–32 characters: lowercase letters, digits and `-`, not starting or ending with a
dash. It's checked against your other subdomains — you can't take a name your site already
uses on that domain, or a community address another project on the domain already has.

## Things worth knowing

- A community can be attached to **more than one** of your domains — each attachment is
  managed on its own domain's page.
- **One community address per project per domain.** If the project is mapped to both the
  apex and `www`, the community attaches once; the other row just shows **Community for this
  project:** with the existing address, since `www` redirects to the apex anyway.
- Disconnecting the *site's* domain mapping detaches that domain's community address
  automatically — the community keeps running regardless.
- The community line shows up once the domain has finished setting up, and attaching needs the
  domain active with an issued certificate — finish [domain setup](https://support.estage.com/domains) first.