Skip to main content

Issue with Setting "Pending" Status for New Members via Automation

Hi everyone,

We’ve encountered an issue while trying to configure new member registrations in Fluent-Community. Our goal is to ensure that newly registered members do not automatically gain access to the community but instead have their status set to "Pending (Require Admin Approval)" so that an admin can manually approve them.

To achieve this, we set up an automation with the following steps:

  1. Trigger: "New User Registration" in WordPress.
  2. Action: "Change Space Membership Status" with the status set to "Pending (Require Admin Approval)."

The automation executes without errors; however, the member’s status does not change to "Pending" as intended. Instead, the member gains immediate access to the community after registration, which is not the desired outcome.

Has anyone else experienced this issue or successfully implemented a similar setup? I’d appreciate any insights or suggestions to resolve this problem.

Thank you in advance for your help!

Stuart McKelvie

Rather than allowing them to create a WordPress user account and try to insert a pending status between WordPress and FluentCommunity, it might be easier to set the pending status before the WordPress user account is created. I know this is how BuddyBoss/BuddyPress works, so while I don't know off the top of my head how it's implemented, it's likely a WordPress function/plugin that already exists and is proven to work (this would require admins to have access to the WordPress dashboard to approve users though).