# Community toolkit — your community inside your own site

> Render your ESTAGE community inside a site Genesis built for you — feed, courses, live and more, restyled to your brand and managed from Genesis.

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

---

The [community portal](https://support.estage.com/community) is a destination on its own address. The **Community toolkit**
is the other option: it renders your **existing ESTAGE community inside a site Genesis built for
you**, screen by screen, in your own design.

Use it when you want members to stay on your own site — same header, same design — rather than
moving to a separate portal. You set it up in Genesis under your project's
**Settings → Community**.

## Before you start

- The project is a [Web app](https://support.estage.com/platform-web-apps). The toolkit needs a server, so it's available on
  Web app projects; a website that already had it set up keeps the tab.
- You need to be the **project owner** — only the owner can set it up.
- If your community already lives on the classic platform,
  [import the legacy project](https://support.estage.com/community-legacy-import) first.

## What you get

Every community screen, as part of your site:

| Area | What's there |
| --- | --- |
| **Feed & posts** | The activity stream, posting, and discussion |
| **Member profiles** | Who's in the community, and their profile pages |
| **Courses** | Courses with their lessons and downloadable resources |
| **Challenges** | Time-boxed activities members take part in |
| **Video library** | The community's videos |
| **Live broadcasts** | Live rooms with chat alongside them |
| **Stories** | Short-form updates |
| **Events & leaderboard** | Upcoming events and who's most active |
| **Moderation queues** | The queues where you approve or reject what members post |
| **Badges & gamification** | Points, levels, and badges |

## Sign-in is handled by ESTAGE

Members sign in through a **secure ESTAGE login**. Their credentials never touch your site's
code — your build renders the community, it doesn't hold the passwords.

## It looks like your site, not like a template

The AI **restyles every community screen to match your brand** — the same way it styles the rest of
your site. Ask for changes to a community screen in chat, exactly as you would for any other page.

## Setting it up

The toolkit lives in your project's **Settings → Community** tab.

1. Click **Set up community**. One click creates this project's community if it doesn't exist yet
   and connects it to the site. If your community already lives on the classic platform,
   [import the legacy project](https://support.estage.com/community-legacy-import) first — that's what binds the builder to
   the right community, members and content.
2. The tab shows **Connected** and the community it serves. The community appears on your site at
   `/social`.
3. Click **Ask AI to style it** for a first pass: one prompt matches the community to your site's
   style, wires the nav link and login state into your header, and polishes cards and profiles.

## Managing the community from Genesis

Below the setup, **Community settings** lets you run the community without leaving Genesis:
**General**, **Access & membership**, **Behavior**, **Members**, **Post Moderation**, **Levels**,
**Point Rewards**, **Badges**, **Community Rules**, **Channels**, **Channel Settings**, **Topics**,
**Custom Emojis** and **Amplify**. Changes apply to the community itself — everywhere it renders,
including its own portal. Each one is explained in the community pages of this guide, starting with
[General settings](https://support.estage.com/community-general-settings).

## Updating and disconnecting

- **Rebuild interface** ("Community interface out of date?") updates the community screens in your
  site to the latest version, so you pick up fixes and features released after your setup. Members,
  posts and courses are untouched.
  On a website set up with the earlier version of the toolkit, there's no rebuild: the components
  were installed once and are yours to edit in chat.
- **Disconnect** (under **Connection**) takes the community off the site.
  The screens stay in the project and nothing on ESTAGE is deleted — members, posts and courses
  are safe. You can reconnect any time.

> **Caution**
>
> **Rebuild interface** replaces your own edits to the community screens, and this can't be undone.
> Members, posts and courses are not affected.

## Things worth knowing

- **Each app has its own setup.** In a project with several apps, setting the toolkit up in one
  doesn't touch the others.
- **The binding doesn't follow a re-bind.** It's one of the few things that **doesn't move** when you
  [re-bind a project](https://support.estage.com/project-settings-general#re-bind-to-another-estage-project) to a different
  ESTAGE project — set it up again on the new one.