Server collective ownership

The essence of the problem being solved: The arbitrariness on the part of the server owner’s account and the inability to influence this in any way. The ability to remove the server in a couple of clicks, drive out unwanted users.

If the server was created not by one user, for personal use, but by the team, this can become a problem.

Proposed solution to the problem:
The option of collective ownership and management is added to the server, which does not allow ONE owner to do whatever he wants.

Mechanics:
A new option appears in the server options in which collective ownership settings are made. Any change to these settings requires a vote (which should also be customizable)

The following items need to be configured:
1. The list of owners;
2. Setting voting by owners (this setting is necessary to prevent situations when one owner wants to dictate terms to another. This determines the number of votes needed to make a decision, the weight of votes of different owners, owners with the right to veto, which will remove the issue of accepting the change from the agenda);
3. Adding/Removing the owner (this item should also be made optional. For example, allow someone who wants to be removed from the owners to vote, or if he has a veto, remove this issue from the agenda)
4. Configuring owner permissions (limiting the ability to change server settings. Changing each setting item has its own individual restriction for changes.

Example:
The function of changing participants, User1 can change without the demand of other owners/the change is put to the vote, in which two votes are needed/the change is put to the vote, in which all votes are needed, etc.)