Eight Years For Free. Not Even A Goodbye.
Somehow I feel like a jilted lover who, after a long relationship just found they no longer pick up the phone or a husband who arrives home one night to discover the locks have been changed.

20 November 2026. This is my firsthand account, not independently verified reporting. The events, eight years of service, approximately 149,000 members and team of around eight to ten fellow moderators described here come from my own experience. The conclusions are mine too.
For eight years, I helped look after Elementor’s official Global Community Facebook Group. Today, Elementor removed our entire volunteer admin team. Not simply our admin and moderator privileges. They removed us from the group itself. No warning. No discussion. After eight years, not even a goodbye.
I have been trying to find a polite way to write that last sentence. There isn’t one that improves it. There are corporate words that could make it sound less ugly, but I have spent quite enough of my own time making Elementor’s decisions sound better than they were.
This is not a story about employees being dismissed. We were volunteers. We worked for free. A tight group of us, myself and around eight to ten fellow moderators, gave our time to a community of approximately 149,000 members. We helped keep it running smoothly because we believed it was worth doing. Because, for a long time, it was.
And that is the part I do not want buried under the anger. We built something I was proud of. They have removed us from it. They do not get to remove the pride as well.
We were not just keeping the chairs straight
“Moderation” is a miserable little word for the work that holds a large community together. It makes the job sound like moving a few posts into the correct drawer. Our work involved rules, judgement, consistency and conversations between people who cared enough to disagree about getting it right. We met regularly online to discuss the group’s rules. We worked together to foster the kind of community people could actually use, not merely join.
A membership count is a number. A community is what happens between the people represented by that number. It is the difference between a room full of customers and a place where those customers feel somebody is listening. Keeping that difference alive takes work. Not particularly glamorous work. The sort that rarely earns a launch announcement and is noticed most clearly when nobody is doing it.
We did it in our own time. The meetings, the discussions, the judgement calls, the effort to keep things moving: none of it stopped the rest of our lives needing attention. Free is a description of what Elementor paid for it. It is not a description of what it cost us.
I am proud of how we worked together. Not because we were flawless, or because every decision pleased everybody. A group that size will not produce unanimous approval of the weather, never mind moderation. I am proud because we cared about the place, and we kept showing up.
Today the admin team is made up of Elementor staff. Our whole volunteer admin team is gone. A tidy change if your only measure is the list of names with access. Rather less tidy if you remember there were human beings attached to the names.
The painful part: they really did listen
It would be easier to write this if I could say the relationship had always been a sham. I could wrap eight years in a neat warning about corporations and volunteers, sharpen the headline and be done. But it would not be true to my experience.
Elementor listened in the earlier years. We fed back on product plans and new developments. Some were in alpha, some in beta. We attended online meetings with product development and marketing teams, in our own time. I am not going to disclose private details or pretend access to a meeting gave us ownership of a roadmap. It gave us something simpler: the feeling that our experience mattered.
We were proud to be an unofficial voice of the customer within the official community. People who understood the product, understood its users, and could help carry one side’s experience to the other. That position was useful precisely because we were not reading from a company script. We wanted Elementor to succeed, and we wanted it to hear what success required.
That was a relationship worth giving time to. It is also why this hurts. You cannot betray a connection that never existed. I am not angry because a company failed to live up to an imaginary relationship I invented yesterday. I am angry because I remember when there was a real one.
When a company has never listened, you learn not to expect it. When it once did, you keep recognising the company it used to be in the one standing in front of you. Sometimes that recognition becomes an expensive habit.
Yes, I defended the indefensible
We helped guide Elementor through what I remember as the version 3 debacle and other blunders over the years. We fed back. We spoke up. We defended Elementor in online communities. And sometimes we defended actions that were indefensible.
I am not going to decorate that admission with invented examples or turn it into a performance of heroic suffering. It is uncomfortable enough without assistance. There were times when loyalty got ahead of judgement. I can see that. I could see some of it then. Yet I still wanted the company to get it right.
When you know the product, know the people using it and have a history of being heard, you give the benefit of the doubt more readily. You can understand why a decision was difficult without agreeing with it. You can distinguish a bad launch from a bad intention. Those are useful instincts. They can also become the mechanism by which you explain away one disappointment too many.
I do not regret trying to help users, or bringing feedback to people who could act on it. I do regret any occasion when defending the brand became more important than asking whether the defence was deserved. That is my responsibility. Today does not absolve me of it. It does, however, make me rather less inclined to volunteer for the next round.
A company does not have to demand your loyalty to benefit from it. Sometimes you provide it so reliably that everyone, including you, starts treating it as part of the furniture. Then the furniture is removed, and you discover who thought it belonged to whom.
They can change the team. That is not the argument.
Let us remove the easiest distraction. Elementor can choose to have its staff moderate its official group. I am not claiming that eight years of volunteering buys a permanent office, a veto over staffing or perpetual ownership of a Facebook community. We were not employees demanding employment rights. We were volunteers asking, in effect, to be treated like people.
A staff-led transition could have been explained. The outgoing team could have been told before it happened. There could have been a discussion about handing over responsibilities and recognising the contribution. Those are possibilities, not accounts of messages that were sent. According to what I experienced today, there was no warning and no discussion.
And this was not merely “thank you, we are taking over moderation”. Our whole volunteer admin team was removed from group membership. That distinction matters. Losing a responsibility is one thing. Being put outside the community you helped care for is another. I will not have the second softened into the first because it makes the paragraph easier to read.
I did not need a medal. I did not need a ceremony in which somebody from marketing pronounced “community” with sufficient reverence. I would have settled for the sort of basic courtesy most people manage when someone has helped them carry a sofa upstairs. Eight years is a considerably longer staircase.
This is why “it is their group” is not an answer to the grievance. Ownership explains who can make the decision. It does not explain why the decision had to be carried out this way. You can have every right to close a door and still behave appallingly in how you close it.
Institutional memory does not appear on an access list
What a long-serving volunteer team accumulates is not just familiarity with settings. It is memory. How rules developed. Why particular compromises were made. How to work together when judgement is not obvious. The difference between a member with a genuine concern and a discussion that needs steering back towards usefulness. I am describing the kind of knowledge built through years of participation, not claiming we alone possessed it.
Staff can be capable moderators. They may bring resources we did not have. I have no basis for saying they will do a bad job, and I am not going to invent one. But a replacement team does not automatically inherit eight years of shared context simply by receiving the same permissions. The little badge transfers. The history does not.
A respectful handover is one way to preserve that history. It is also a way to acknowledge the humans who hold it. When there is no warning or discussion, an organisation chooses not to use that opportunity. Whatever the reasons behind the decision, that is the experience left with the people outside the door.
There is a special corporate economy in which years of unpaid care are useful right up to the moment basic courtesy would cost five minutes. I cannot tell you what Elementor’s internal calculation was. I can tell you how the outcome felt from this side of it: our contribution had been welcome; our continued presence apparently was not.
Customer advocacy is not the same thing as company messaging
The independence of a volunteer team is imperfect. We were loyal. I have already admitted where that loyalty went too far. But we were customers and practitioners giving our own time, not staff responsible for representing the company as part of a paid role. That difference mattered to me.
Moving to a staff-led team raises a reasonable question: where does the unofficial voice of the customer go now? How will challenging feedback be carried into the company? Who will have room to tell the organisation something it would rather not hear? Those are questions about the shape of the relationship, not allegations about what the new moderators have done.
I do not know that staff will censor criticism. I am not claiming they have. Nor am I claiming that volunteers are automatically independent saints and employees are corporate puppets. The issue is whether a community remains a place where the company encounters its customers, or increasingly becomes a place where the company presents itself to them. The two can look remarkably similar in a screenshot.
Earlier this year I wrote about Elementor’s MCP adapters and the danger of mistaking a clever commercial bridge for meaningful progress. This is not further proof of every technical criticism in that article. It is a different kind of question about what a company chooses to preserve. A product can acquire another interface. A relationship cannot be repaired by adding a panel.
Community is not a product feature you can switch on when the roadmap needs customer feedback and switch off when the customer feedback becomes administratively inconvenient. That is my view of what the word ought to mean. I do not know why today’s decision was made. I do know it leaves that word sounding rather hollow.
And yes, people trust this company with their websites
This is the company people are trusting their websites with. I say that as someone who has spent years inside its community, not as a person who discovered Elementor this morning and immediately developed a comprehensive theory of its downfall.
Does the treatment of volunteers prove that the software is insecure? No. Does it prove a client’s site will fail, or an update will break, or the staff now running the group are incompetent? No. An ugly community transition is not a technical audit, and I will not pretend otherwise.
It does give me a reason to reassess vendor trust. When you depend on a company, you depend on more than its current list of features. You depend on how it communicates change, how it deals with people who have invested in the relationship, and whether it recognises that a decision can be technically within its control while still deserving an explanation.
If this is how a long-standing volunteer relationship ends, what should a customer expect when their needs no longer fit the company’s priorities? That is an inference I am entitled to consider, not a prediction I can prove. I would ask it of any vendor. Today I have a particularly personal reason to ask it of this one.
I am not telling website owners to wreck working sites in solidarity. Clients are not props in my disappointment. Make sober decisions about your dependencies, your options and the companies you want to rely on. But do not confuse a familiar logo with a relationship that can never change. I did, for longer than I should have.
I do not need to invent a motive for it to hurt
There will be explanations people can imagine. A new strategy. A desire for closer oversight. Some internal decision none of us was part of. I could write an entertaining paragraph assigning motives and give it the satisfying certainty of an autopsy. I am not going to. I do not know what was said inside Elementor, and the lack of discussion with us is part of the point.
I do not need a secret plan to describe the action. Our volunteer admin team was removed from the group. We had no warning and no discussion. After eight years of my involvement, that was how the relationship ended from where I stood. The facts of my experience are sufficient. They do not become more persuasive if I garnish them with things I cannot know.
Nor do I want individual staff members turned into targets. I am criticising the action and the way the transition was handled. I do not know which person made which decision. Ordinary employees should not have to absorb abuse because a company has left people hurt. Contempt for a decision does not require contempt for every human being behind a logo.
That restraint is not forgiveness. It is the difference between making an argument and throwing furniture. I would like the argument to remain standing after the first surge of anger passes.
What they have not taken
They have not taken the years we gave. They have not taken the fact that we worked together, listened, argued about rules because rules mattered, and helped foster a community worth being proud of. They can remove our memberships. They cannot retrospectively make our contribution meaningless.
To my fellow volunteers: thank you. For the time, the judgement, the meetings and the stubborn belief that the place was worth looking after. We did that together. I will not let the manner of our removal become the definition of our eight years.
To the ordinary members: thank you too. A community of that size is not made by moderators alone, and it certainly is not made by a company’s membership counter. It is made by people participating, helping, asking and returning. We helped look after the space. You gave the space its reason to exist.
I am hurt because I cared. I am angry because I remember the relationship at its best. And I am proud because, whatever happened today, the work was real. Those feelings can coexist. They do not require me to turn eight years into a mistake, or to soften the contempt I have for the way it ended.
Elementor has its staff-led group now. That is its choice. I have the memory of a team that gave eight years for free, of a community we were proud of, and of a company that once listened. I know which part of that history I intend to keep.
Eight years. Not a demand for ownership. Not a claim on anybody’s job. Just eight years of showing up, followed by a door closing without a conversation. I thought we had earned a goodbye. Apparently even that was outside the free plan.
Found this useful? Argue with it.
More Heresies →