Multi-Owner Community Management

(#1362) Feature Open: Under consideration community moderation

Problem

Large communities on many platforms are vulnerable to deletion due to:
  • A single owner having full control.
  • Account compromise or lost credentials.
  • A bad decision or sudden action by the owner.
This creates a single point of failure, risking the loss of valuable communities and destroying the works of many contributors.

Proposal

Implement a multi-owner system where:
  1. Split Ownership
    • Multiple users can be granted owner-level permissions (The Fellowship).
    • All owners share equal control over community settings, moderation, and deletion.
  2. Protected Deletion
    • Deletion requests require approval from multiple owners (e.g., 2/3 owners).
    • Deletion auto-triggers if not declined after X days (to handle inactive owners).
    • When a community has been marked for deletion, notify all existing owners via an In-app pop-up or Direct system message.

Notes

Why This Matters

  • Reduces risk of accidental/hostile deletions.
How this could look like: Memberlist example Setting Example

9 comments

Sign in with Fluxer to comment and vote.
Comment by @snappyapple632
RexSystem 3 votes originally by @snappyapple632 on GitHub 1 reply
On a similar subject, implementing an inheritance system, sort of like how GitHub can transfer repo ownership to another user if the repo owner dies. I don't imagine this being possible on Fluxer since it would require a lawyer or some other parliamentary authority to carry out, but transferring ownership after a set amount of inactivity would definitely be feasible.
Comment by @NanamiTV
RexSystem 1 vote originally by @NanamiTV on GitHub
I support this, i've fallen victim to this ages ago on discord bc the account with ownership got compromised and lost a server with ~10k members.
Comment by @ghost
RexSystem 1 vote originally by @ghost on GitHub
I support this as well, I've fallen victim to losing servers and accounts, and I've started using holding accounts but it wasn't a good idea due to multiple people logging into same account, which would be more of a pain to use.
Comment by @newgeld
RexSystem 1 vote originally by @newgeld on GitHub
I would caveat this with n/x deletion authority can be circumvented if owners can promote straw-man accounts to owner for authorization, or demote existing owners. Likewise, I'd alert owners via email in addition to app notifications. I think there should be a grace period where co-owners can attempt community restoration, but at that point humans from support are involved and arbitration can get tricky.
Comment by @flurbudurbur
RexSystem 1 vote originally by @flurbudurbur on GitHub
I support this. Other than this being a good safetynet, I think that it can serve the platform well to distinguish itself as I believe not many others have this functionality. Additionally, the co-owners would maybe receive an email if any destructive action is taken, seconding Newgeld's idea. Maybe add a banner (like the download one on web, but red) only visible to co-owners if outstanding votes/actions need to be taken.
Comment by Ekki
Ekki 1 vote
This is great, not only against compromised accounts but also against admins with big egos. It happens way too often on Discord, you give an ounce of power online to someone, there's always a chance they become unlikable and start to take solo decisions and ultimately ruin or bring down the community, sometimes with endless drama that could have been avoided.
Comment by Manfre
I like the idea but it could go more in depth. For example, a rogue account with manage channels and ban users permissions can ban everyone and delete all channels, thus achieves the same goal as deleting the community, it just involves more steps. I believe there needs to be a non deletable crown role which always has admin permissions and a hideable crown. Then some sensitive permissions can be enacted with a vote, the sensitive permissions are actions such as deleting, editing or kicking anything. The voting process for each sensitive permission could be:
  • Disabled
  • Half (50 %)
  • Majority (50 % + 1)
  • Supermajority three-fifths (60 %)
  • Supermajority two-thirds (66.67 %)
  • Supermajority three-quarters (75 %)
  • Unanimity (100 %)
Each with a time limit that by default should be declined if no verdict is reached. I consider sensitive the following permissions:
  • Delete community (not part of Fluxer, proposed in this thread)
  • Manage community
  • Manage roles
  • Manage channels
  • Kick members
  • Ban members
  • Manage messages
  • Manage threads
As a bonus, I would suggest naming the owner group «The council» or «The board».