-
-
Notifications
You must be signed in to change notification settings - Fork 414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent the initial admin user from being deleted #204
Comments
good request, we can add this in the next major release edit in the
|
Thanks for the quick response! The code did not work but gave me a way to modify it enough to make me happy:
For a more future-proof implementation, it should be whatever first user created from the setup script. But since someone might create a silly initial name or one with a typo, maybe an even more stable implementation would be to create a user automatically, call it "rmmadmin", "tactical", or something else, and just prompt for a password from the user. That "rmmadmin" or "tactical" user can't be removed or disabled from the GUI, unless we have back-end access. This could be a good way to introduce some permission levels while we wait for the full-featured release with users and groups (1 user that cannot be deleted, a super-user, to manage the other users if anything goes wrong). Btw, can I ask if you have a Patreon or a way to support this project? My company is really impressed. |
Did you delete the initial user from django admin or some other way? Cuz But anyway what i'll do is add an optional setting in No Patreon but have added a sponsor button on the projects page :) |
Added in release v0.2.17 |
It seems that anyone can add/delete any user, so if I share access to Tactical RMM to a colleague, he can remove my access then I would be locked out.
It would be great if the first user created from the setup script was the official admin user and was greyed out, unable to be removed. Similar to the root user on Linux. If I give access to somebody, I can be sure that I will never be locked out, as I'm the primary maintainer of the tool.
Is there a way to achieve that right now?
The text was updated successfully, but these errors were encountered: