Set up a community product
Community products give buyers access to a private group, forum, or membership community. Delivery is usually a community invite link, external platform access, or members area integration.
Use this guide when you sell access to Discord, Circle, Telegram, WhatsApp groups, or a hosted community experience.
When a community product fits
| Use a community product when | Use another product type when |
|---|---|
| The buyer joins a group or community | The offer is 1:1 coaching. See mentorship product setup. |
| Access is ongoing membership or community entry | Delivery is a downloadable ebook. See ebook delivery. |
| You need labeled invite or access URLs | Content is structured lessons. See course product setup. |
Full setup workflow
- Confirm you are in the correct business workspace.
[Screenshot: App header showing the active business name and workspace switcher.]
- Open Products and start a New product.
[Screenshot: Products list page with New product button visible.]
- On What will you sell?, select Community.
[Screenshot: Product type selector — Community tile selected; subtitle reads "User community."]
- Complete product details: name, description, category, and sales page URL.
[Screenshot: Community product details form — name, description, category, and sales page URL.]
- Configure how buyers enter the community after payment.
[Screenshot: Community delivery settings — link delivery or external members area options.]
- Add delivery links with clear labels (for example
Discord invite,Circle access,Community rules).
[Screenshot: Delivery links list for community — labeled invite URLs saved on the product.]
- If the community is provisioned through an external members platform, add the callback URL when required.
[Screenshot: External members callback URL field for community access automation.]
- Save the product and complete product approval details.
[Screenshot: Product approval section describing the community offer and access method.]
- Create the plan and offer. Communities are often subscription-based.
[Screenshot: Subscription plan form attached to the community product.]
- Create a checkout link.
[Screenshot: Checkout link for the community product with copy button.]
- In the checkout builder, state how and when buyers receive community access.
[Screenshot: Checkout preview with community access instructions and published status.]
- Run a test purchase and confirm approved status in Sales.
[Screenshot: Approved community test sale in Sales.]
- Confirm the buyer can open the invite link or receive automated access.
[Screenshot: Post-purchase screen or community platform showing test buyer access.]
- Define support steps for expired invites, wrong email, or subscription cancelation.
[Screenshot: Support playbook — community invite and subscription cancelation steps.]
Delivery options for communities
| Option | Use it when |
|---|---|
| Link delivery | Buyers join via invite URL after payment |
| External members area | Access is created automatically in a third-party platform |
| MemberKit or similar | Community and content share one external members stack |
What to verify before launch
| Check | Why it matters |
|---|---|
| Invite links are not single-use unless intended | Broken invites block many buyers at once |
| Checkout matches community platform (Discord vs Circle, etc.) | Reduces confusion and refunds |
| Subscription cancelation policy is clear | Community access often depends on active billing |
| Links work on mobile | Many buyers join from phones |
Best practices
- Regenerate or audit invite links before major launches.
- Separate
Main community accessfrom bonus resource links. - Test cancelation and subscription overdue behavior if access should pause.
- Document moderation and support ownership for community issues.
Common mistakes
- Using expired or revoked community invite URLs in a live product.
- Promising instant access when payment can remain pending on some methods.
- Mixing community access with unrelated product types in one checkout promise.
- Forgetting to update links when the community platform changes.
FAQ
Should community products use subscription pricing?
Often yes, when access should continue while the buyer pays. Define what happens when billing fails or the subscription is canceled.
Can I use multiple community links?
Yes. Use link delivery with clear labels for main access, rules, and bonus channels.
What if the invite link stops working?
Update the URL in the product, notify support, and review whether existing buyers need a new invite. See buyer access troubleshooting.