Replies: 2 comments 1 reply
-
This is out of scope due to its subtle complexities. It requires everything on CapRover to be namespaced. Even then, if an application binds to A more enterprise version of this might be added as a premium feature in the future with auditing and etc. But for CapRover as it stands, it's out of scope. As mentioned in the scope:
|
Beta Was this translation helpful? Give feedback.
-
@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, @lcx explains it well here: #492 (comment) |
Beta Was this translation helpful? Give feedback.
-
It would be very interesting to be able to create multiple users, and each one has only access to some apps, to change its settings and for deployment.
Beta Was this translation helpful? Give feedback.
All reactions