Feature Request: Customizable Pending, Under Review and Blocked Member ~~Pages~~
Hi Shahjahan Jewel and team,
I would like to suggest an improvement to FluentCommunity’s member access management.
FluentCommunity already supports Active, Pending and Blocked member statuses. However, the access pages shown to Pending and Blocked members currently use fixed generic messages.
This becomes especially important when an account is temporarily restricted because of suspicious activity or a manual security review. In that situation, the member should see a clear, branded and reassuring explanation, together with a safe way to contact support. The current generic “Access denied” message does not explain what has happened or what the member should do next.
Would you consider adding:
• A dedicated “Under Review” status, separate from “Pending” and “Blocked”.
• Separate customizable page templates for Pending, Under Review and Blocked members.
• Custom title and rich-text description for each status.
• Custom primary button text and URL, for example “Contact Support” or “Open a Support Ticket”.
• An optional secondary action for logging out or resetting the password.
• The option to select an existing WordPress page or enter a custom redirect URL.
• Automatic use of the community’s logo, colors and general branding.
• Developer filters for the page title, message, buttons and redirect URL.
Ideally, placing a member Under Review or Blocked would restrict access without removing their profile, course enrolments, purchases or membership history.
A dedicated Under Review status would also help distinguish a temporary security or account verification process from a permanent block.
I believe this would improve both security workflows and the member experience, especially for communities that manage paid courses or sensitive account information.
Would you consider adding this?
Thank you!
Jorge de los Reyes Thanks for taking the time to put this together! 😊
This is a very thoughtful suggestion. I'll pass this along to our product team as a feature request for consideration. We can't promise an ETA, but thanks again for sharing such a clear use case!
Farjana Rahman Appreciate it so much Farjana! Let me know in case you need feedback or context use cases :)