Add administrator features #72

New issue

Open

opened 2026-05-12 22:27:00 +00:00 by luca0N · 1 comment

luca0N commented

2026-05-12 22:27:00 +00:00

Owner

The current database schema allows the assignment of administrative privileges to user accounts. Administrators should have access to administrative tools, which have not been developed yet.

Instance overview (list of accounts, uptime, etc.)
Creation of user accounts (useful for instances with user registration disabled)
Removal of user accounts
Assignment of user accounts as administrator

This list should suffice for now. Changing server settings via the web UI is not possible in the current state, as all server settings are stored on disk, and not on the database.

The current database schema allows the assignment of administrative privileges to user accounts. Administrators should have access to administrative tools, which have not been developed yet. - [ ] Instance overview (list of accounts, uptime, etc.) - [ ] Creation of user accounts (useful for instances with user registration disabled) - [ ] Removal of user accounts - [ ] Assignment of user accounts as administrator This list should suffice for now. Changing server settings via the web UI is not possible in the current state, as all server settings are stored on disk, and not on the database.

luca0N added the

Kind/Feature

label

2026-05-12 22:27:00 +00:00

luca0N added this to the v1.0.0 project

2026-05-12 22:27:00 +00:00

luca0N commented

2026-05-12 22:31:45 +00:00

Author

Owner

To counter this, I believe the best solution is to disallow administrator accounts from removing administrator privileges from other accounts or deleting them (and show a warning in the web app about the consequences of giving another user such privileges). Instead, the removal or demoting of administrator accounts should be done from the server via the command line, either as a special command or command line argument to the server, or by invoking a new separate program which does the work. Of course, it would be possible for instance owners to modify everything manually in the database, but this would result in poor UX, plus, the command line solution could be expanded in the future to accommodate new features.

A feature that allows administrators to give administrator privileges to other user accounts is tricky, since the current account privilege system in Lanbassador is primitive. For instance, a compromised administrator account could remove administrator privileges from another administrator accounts, and wreak havoc on the server. To counter this, I believe the best solution is to disallow administrator accounts from removing administrator privileges from other accounts or deleting them (and show a warning in the web app about the consequences of giving another user such privileges). Instead, the removal or demoting of administrator accounts should be done from the server via the command line, either as a special command or command line argument to the server, or by invoking a new separate program which does the work. Of course, it would be possible for instance owners to modify everything manually in the database, but this would result in poor UX, plus, the command line solution could be expanded in the future to accommodate new features.