You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, a user can select any provider of their choice and also change the branch. This means a malicious user with access to one service can scrape the repositories of all providers and branches. When working in a team, users need to have access only to the repositories they work with.
Describe the solution you'd like
I'd like to request a feature to manage Git provider permissions, so users can't select any provider or change the repository on my service.
That could consist on a table where we can affect user permissions to use certains provider, repos and branchs.
Describe alternatives you've considered
Currently, I can't share access to the Dokploy service with my team due to security concerns. Users can scrape any repositories, which poses a significant risk. I didn't find any alternatives other than being the only one to access dokploy.
Additional context
No response
Will you send a PR to implement it?
No
The text was updated successfully, but these errors were encountered:
What problem will this feature address?
Currently, a user can select any provider of their choice and also change the branch. This means a malicious user with access to one service can scrape the repositories of all providers and branches. When working in a team, users need to have access only to the repositories they work with.
Describe the solution you'd like
I'd like to request a feature to manage Git provider permissions, so users can't select any provider or change the repository on my service.
That could consist on a table where we can affect user permissions to use certains provider, repos and branchs.
Describe alternatives you've considered
Currently, I can't share access to the Dokploy service with my team due to security concerns. Users can scrape any repositories, which poses a significant risk. I didn't find any alternatives other than being the only one to access dokploy.
Additional context
No response
Will you send a PR to implement it?
No
The text was updated successfully, but these errors were encountered: