-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Multi tenancy #77
Comments
It's partly - if not entirely - implemented in v2. You could have separation by teams on the UI and docker network on the docker/server levels. Environments like prod/staging would be implemented later, but it needs to be figured out how. 😄 |
Hi @andrasbacsai Loving Coolify. One detail: If I have registration closed, I cannot invite new members to teams. From a management point of view, I would like to create my teams (as I am the server admin) and then invite people to specific teams. Is that possible? |
Thanks! Yes, it will be possible if I add SMTP integration. |
I'm closing this issue, because tracking features will be moved to GitHub discussions. Github issues will be only for bugs. Version 4 is in full focus. v3 related issues will be closed, if it is not a critical bug. Thanks for your understanding. |
Background
The current platform allows for one single "namespace" / "project"; however this should be extended to allow for multiple projects with their own collection of apps / services (see - #75). Additionally the concept of Organisations could be introduced (teams, if you will) - allowing for multiple users to view and manage these resources, with a roles system.
Use case
There are multiple use cases, but one that stands out the most is allowing for the orchestration of multiple projects from one Coolify instance, such as in an enterprise environment where multiple teams need access to different resources or perhaps a "production/staging" environment separate.
Notes
The text was updated successfully, but these errors were encountered: