Multi Server Permission Model

[ErSauravAdhikari]

What problem will this feature address?

It'd be great if we could select which servers a given user can deploy to from the permission settings.

Describe the solution you'd like

On the user permission page, we add in (Similar to projects selection list), a server selection list. So that the user can only add a new project or service to a given server.

Describe alternatives you've considered

Multiple deployments on multiple server does solve the issue, but the user experience can indeed be improved.

Additional context

No response

Will you send a PR to implement it?

No

[vishalkadam47]

so you mean the user should not have server access by default, instead a new user should be like a GUEST just a dashboard and profile with no server access, no project and no service until assigned from the permission settings.

[ErSauravAdhikari]

Basically what I was talking about was similar to this.

A user can only use a subset of connected servers. So the dokploy instance acts as a unified interface to connect to multiple servers, say S.A, S.B and S.C where the users U.A can access and deploy to only S.A after the permission has been configured, but not to S.B and S.C. But if they are allowed to access the server (by admin) then they can.

[vishalkadam47]

I'm working on the Teams management system #882 will plan an option to assign a server within the permissions system similar to projects and services.
let me know your feedback