Support for proper offboarding of members

Dragan STAMENKOVIC thanks for that!

I've looked at the Delete Account extension you're referring to. It does a great job in that it relates the messages to a 'deleted user' account 👌

However, as far as I understand, this is only available as a self-service. We don't want our members to be able to delete their account; instead, we would like an administrator to initiate the deletion of the account. Or even better, to be able to do so via an API, so that our CRM can control the deletion.

Dragan STAMENKOVIC we plan to use Uncanny Automator to handle this, the same way we do to manage tags in Fluent CRM.

Greg Robins Yes, you can use almost any automation tool that includes an account deletion feature as an action (That is a very common action.) That will better align with what you’re looking for. example : https://automatorwp.com/add-ons/wordpress/

Dragan STAMENKOVIC How can I be sure that the huge number of plugins you’re developing (I assume with heavy use of AI) will continue to be developed and supported in the future? Is this a one-person project, or is there a team behind it? Right now, what’s holding me back is that there are too many plugins, and they’re coming out too quickly, which creates uncertainty.

Itachi Sensei I completely understand your concern, and honestly, it’s a very fair question. Seeing so many plugins come out this quickly can naturally make you wonder if they were just rushed out and whether they’ll still be supported six months from now. Let me give you full transparency on how I work behind the scenes.

First, you’re spot on about AI. I use it heavily, and I think it would be a mistake not to today (even the engineers behind Claude or ChatGPT barely write code by hand anymore). Because my AI agents are deeply trained and configured around my specific workflow, I can move fast. Even though I’m a solo founder, it genuinely feels like having a team of 15 to 20 people working alongside me. That said, AI isn't a magic button that spits out a finished plugin in two minutes. The product vision, the architecture, the creativity, and all the testing behind every single tool still come down to human experience.

As for why there are so many plugins, that’s actually a deliberate design choice. Fluent Community has huge potential, but it’s still missing a lot of features. Even as the official team fills in the gaps, their focus will naturally stay on core LMS and standard community features. Rather than building one massive, bloated "all-in-one" plugin that slows down your site with stuff you don't need, I prefer building lightweight, independent modules. You only install what you actually use. The other big benefit of this approach is maintenance: all my extensions share the exact same technical foundation and rely on Fluent’s native hooks. So if Fluent pushes a major update tomorrow, I can update the entire catalog very quickly without getting overwhelmed.

Finally, on the long-term support side: I’ve been doing this for over 20 years. To me, the service and support behind a product matter just as much as the code itself. In fact, I use Fluent and my own extensions every single day to run my own platforms, so if an update ever breaks something, I’m the first one affected and the first one fixing it! Plus, the great thing about working with a solo dev is that there’s zero bureaucracy. If you ever run into a bug or have a feature idea, you don't get stuck dealing with slow Tier 1 support tickets. You’re talking directly to me.

Of course, no software is perfect on day one, which is why I stay super active in the official community to listen to your feedback and push updates fast. The best way to get peace of mind is to test a few of the extensions yourself and see the care put into them. I hope this answers your questions! See you 👍

Dragan STAMENKOVIC thanks a lot

Dragan STAMENKOVIC you are totally on-point about having AI as a team you can leverage. We build our own plugins using Claude and they have allowed us to add small features and customize our workflow with about two hours of prompting. We hand it off to a human developer to test in a safe environment before we deploy.

My only bit of "advice" is to find your popular products and focus on those, and even charge a small one-time amount to offer support and sustain your operations, or offer a free and pro version.

Looking forward to your add ons!

Greg Robins Thanks so much for your message! The reason I was able to release so many extensions at once is simply because I had already built them all ahead of time behind the scenes, which definitely helps move fast and make a strong impact right from launch. My philosophy is to give away as much value as possible for free, even for extensions I could have easily sold. I do offer premium extensions alongside them, and that balance is working out really well so far. That said, I make zero distinction when it comes to the quality of the work. I pour the exact same passion into a free extension as I do into a paid one. Just because something is free doesn't mean it should be half-baked, even though that's unfortunately what you see most often elsewhere. Since this is still the very beginning of the journey, I'm offering lifetime deals for now, though subscription plans will very likely come later on to ensure the project's long-term sustainability. Either way, there are plenty of great ways to fund what's next, so I'm not worried about it at all, and the goal remains to offer as much as possible.

@all, I have the feeling we're drifting off-topic a bit.
All I'm asking for is a proper offboarding facility controlled by admins or even better: via an API.

I'm looking forward to a response of wpmanageninja or an FC extensions supplier who can offer this :-)

Peter Mienes You were given an answer a bit further up. Use an automation service, and it will work very well.