Server-level access control / RBAC #8086
Replies: 2 comments
-
|
That's already possible through Teams. If you create two teams, give one team access to the production server while the other gets development, you can start assigning users to each team depending wg t access level you want them to have. |
Beta Was this translation helpful? Give feedback.
-
|
I had somewhat similar requirements, and did a PR on coolify which was rejected saying it is for v5... So I created my own project and fixed the issue. Have a look here and hopefully this would be useful for you. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey 👋
I was wondering why Coolify doesn’t currently support access roles scoped at the server level, especially in the cloud-hosted version.
For example, if I have two servers:
It would be great to be able to completely isolate access so that some users can only see and deploy to the dev server, with zero visibility or access to production.
Right now, access control seems to be more workspace-oriented, but in practice, server-level isolation is a pretty important security and workflow boundary.
Is something like this planned for v5?
I think this would be a huge improvement for teams and a real game changer for managing multi-environment setups (dev/staging/prod) safely.
Beta Was this translation helpful? Give feedback.
All reactions