Edit history

Earlier versions of Multi-Owner Community Management, newest first.

Current version | Edited by Rex
Changes
[Setting Example](https://feedback.fluxer.com/p/1362#f-1122)Removed: ### ChecksRemoved: Removed: - ☑ I searched existing discussions.Removed:
Show

Multi-Owner Community Management

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
Original by Rex
Show

Multi-Owner Community Management

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

Checks

  • ☑ I searched existing discussions.