Skip to content

Community overview & creating one

The Community module attaches a complete social platform to your project: a member feed, groups, courses, events, and member profiles. It’s the “turn an audience into a membership” piece — your site markets, your community retains.

A community is not pages inside your site — it’s a full standalone portal that runs next to it, on its own address:

Your site links to it (a “Community” button in your nav), visitors click through, sign up, and they’re in.

  1. Open Settings → Modules.
  2. On the Community card, click Add community.
  3. Genesis provisions the community (named after your project) and the card flips to ENABLED with an Open community → link.

If your project already has an active custom domain, Genesis also tries to claim community.<your-domain> for it automatically — so the portal lands on your brand from day one.

That’s the whole creation flow — no forms, no wizard.

Your community comes with the full feature set:

AreaWhat it is
FeedThe member activity stream — posts, reactions, discussion
GroupsTopic spaces within the community
CoursesStructured learning content for members
EventsA calendar with RSVPs
MembersProfiles and the member directory
Direct messagesMember-to-member chat
Access levelsGroups gated by what a member has bought or been granted
ChallengesTime-boxed activities members take part in
Live roomsLive streams and video calls inside the community
GamificationPoints, levels, and badges for participation

The community isn’t only a web portal: members can install a native iOS and Android app for it, with push notifications and deep links straight into a post, a course, a chat, or a live room. The community they join on your domain is the same one they carry on their phone.

Day-to-day administration — privacy, groups, courses, events, member moderation — happens in the community portal itself (the Open community → link), where you’re the admin. That’s also where you brand the emails it sends and set the reply-to address — see Community emails. Genesis manages the connection: activation status and which address it lives on.

  • One community per project. A project maps to exactly one community.
  • Separate sign-in. The community has its own member accounts — signing into the community is separate from anything on your site.
  • The portal isn’t embeddable into site pages — it’s a destination, not a widget. Link to it prominently. If you want the community’s screens inside your own site instead, that’s the Community toolkit, on a Web app project.
Community portalCommunity toolkit
Where it runsIts own address (community.mysite.com)Inside the site Genesis built for you
DesignThe portal’s ownRestyled by the AI to match your brand, screen by screen
RequiresAny projectA Web app project
Members sign inIn the portalThrough a secure Estage login on your site

Don’t create a new one — import your legacy project and Genesis will use the existing community, members and content intact.