@githubsaturn... The multi-user implementation doesn't need to be role based. Everyone can be admin. This is because organisations have users coming in and out.

If one account is used by everyone, then an ex employee will still have admin access to all the organisation's app. To prevent this,
passwords need to change all the time.

@lcx explains it well here: #492 (comment)

This request would be useful just for identification. It does not need to provide roles. The main reason for a multiple users feature is so that organizations can track, who, what and when. The fact that all users have admin access is not as issue, and is assumed to be acknowledged when caprover is installed. Once you have users, it's something you can build features on in the future. As mentioned by @dkyeremeh at the moment, every time a user leaves the organisation or changes jobs in the department, the password would need to be changed. Without being disrespectful, for most organisations this limitation makes it a hobby tool, rather than anything that could be incorporated into a commercial production tool chain.

it would have been really useful to have multi user support, even if it is for planned for enterprise version I ready to go for it.