Config Defined Admin List #1246
Labels
No labels
Blocked
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
To-Merge
Wont fix
old/ci/cd
old/rust
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity#1246
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Having the server administrator list be defined by those present in a specific room is problematic as:
These two problems can be avoided by having the admin list be defined by config in some way.
I propose the addition of two new config values.
"admins", which is a list of Matrix IDs; any account added to this list will be an admin, regardless of whether they are in the admin room or not.
"admins_from_room" which is a boolean; when true, those in the admin room are granted admin access in addition to the config defined list. When false only the admin list is used.
By default "admins_from_room" is enabled to preserve behavior that everyone has come to expect, and to avoid users getting locked out. However users should be advised to add themself to the admins list, and then disable this option due to the previously mentioned security concern.