​ Disable or Enable the Mandatory Profile Modal for Community Members

Adaptive AI now allows Community Admins and Group Owners to control whether new members are required to complete their profile before entering a group.

Using the new Show mandatory profile modal setting, you can choose whether members must upload a

profile picture and bio during onboarding or allow them to access the group immediately.

What Is the Mandatory Profile Modal?

The mandatory profile modal appears when a new member joins a Community group for the first time.

The modal prompts the member to:

• Upload a profile picture
• Add a short bio

When enabled, members must complete or interact with this step before entering the group.

Enable or Disable the Mandatory Profile Modal

You can control this setting individually for each Community group.

1. 1Open the desired Community group
2. 2Choose one of the following:
3. 3Save your changes
4. 4This setting only affects members who join after the change is made.

Important Notes

• The setting is managed per group, not globally
• Existing member profiles are not affected
• Members can still update their profile picture and bio later from their personal settings
• The setting applies across web, iOS, and Android experiences

Frequently Asked Questions

Q: Does disabling the modal remove profile pictures for existing members?

No. Existing member profiles and avatars remain unchanged.

Q: Can members still upload a profile picture later?

Yes. Members can update their profile information anytime from their account settings.

Q: Is this setting applied globally across all communities?

No. The setting is configured individually for each group.

Q: Does this affect the mobile app?

Yes. The setting applies consistently across web, iOS, and Android.

Q: Who can manage this setting?

Only Community Admins and Group Owners can enable or disable the setting.

Before you begin

“​ Disable or Enable the Mandatory Profile Modal for Community Members” is part of the Sites → Websites area in Adaptive AI. Create pages, apply templates and themes, publish, and manage website settings. 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.