Paid Groups

In This Article

Private and Public Groups

From the "Settings" button within a Community, admins and owners can choose whether they want to set up their group as Public / Private.

One-Time Payment

One-time payment type will give members an unlimited access of the group after the payment and once they have group access. To set up one-time payment follow the below steps:

• Log into the Community
• Go to "Settings" > "Subscriptions"
• Click "Add" and then "Save" to create the paid group with One-time Payment
• Once saved, the group description will reflect the same information to members who want to join

Recurring Subscription

Recurring subscription type will give members a limited access of the group after the payment and once they have group access. To set up the recurring subscription, follow the below steps:

• Log into the Community
• Go to "Settings" > "Subscriptions"
• Click "Add" and then "Save" to create the paid group with Recurring Subscription
• Additionally, to test a payment, turn on the
• Once saved, the group description will reflect the same information to members who want to join

Taxes

Learn more: Tax Support in Communities Payments.

Group Access

To grant access after receiving the payment:

• All admins and owners receive email notification about the payment made by a user with all the details, to join the group and subsequently to request membership (as per group type)
• Similarly, the users also receive a payment confirmation with all the details about their payment
• Once their membership is approved by admin or owner. They are further notified about their membership and access of the group
• Members can get their refunds from both Stripe or Adaptive AI Payment

Before you begin

“Paid Groups” is part of the Memberships → Communities area in Adaptive AI. Manage groups, members, posts, channels, comments, and community access. Course and community settings affect what members can access, when content unlocks, and which notifications they receive. Always test from a member account as well as the administrator view. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Confirm the course, offer, group, category, lesson, price, and access rule belong to the intended member experience.
• Use a separate test member account that does not already have broad administrator or legacy access.
• Review publish status, visibility, drip timing, time zone, prerequisites, and notification settings.
• Prepare final lesson content, downloads, thumbnails, links, and any payment or enrollment automation used to grant access.
• Define what should happen when access is purchased, granted manually, completed, canceled, or removed.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Grant or purchase access with the test member and confirm the correct course, group, category, and lesson become visible.
2. 2Verify locked, scheduled, or prerequisite content remains unavailable until its intended condition is met.
3. 3Test video, downloads, comments, assignments, quizzes, links, progress tracking, and mobile layout where applicable.
4. 4Confirm welcome, unlock, comment, completion, and payment notifications reach the intended person only once.
5. 5Remove or cancel test access and verify the member experience and related automation update correctly.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Check the member's exact offer, product, group, role, and access status when content is missing or unexpectedly visible.
• Compare publish status, drip schedule, account time zone, prerequisites, and completion state for locked content.
• Test with a true member account because administrators can see content that ordinary members cannot.
• Review payment and enrollment workflow history when access should have been granted automatically.
• Confirm notification preferences and event conditions when access works but the expected message does not arrive.

Best practices

• Organize content in a predictable progression and give every lesson or group a clear outcome.
• Keep member-facing names, thumbnails, descriptions, pricing, and support instructions consistent across offers and portals.
• Use drip and notification settings intentionally so members receive guidance without unnecessary message volume.
• Test onboarding and cancellation paths whenever offers, payment settings, or access automations change.
• Review member feedback and completion data to improve unclear lessons, dead links, and common support gaps.