[Bug] Git Providers are not shared between Dokploy instance members

[EliasBorrajo]

To Reproduce

1. Have a Dokploy instance with at least 2 users (one owner, one member)
2. As the owner, go to Settings → Git Providers and create a GitHub provider linked to a GitHub App installed on a GitHub Organization
3. Log in as the member user
4. Go to Settings → Git Providers
5. Observe that the provider created by the owner is not visible at all
6. When creating an application and selecting the GitHub source, the member sees: "This application is connected to a github repository through a git provider that you don't have access to." and cannot modify the configuration

Current vs. Expected behavior

Current behavior

Git Providers appear to be scoped to the user who created them. Other members of the same Dokploy instance cannot see or use them, even if they belong to the same GitHub Organization.

The root cause is visible in the source (as identified in Discussion #2912): apps/dokploy/server/api/routers/git-provider.ts lines 9–23

The getAll query filters by both userId and organizationId, meaning providers are scoped to their creator and never shared across members of the same Dokploy org.

Is this behavior intentional? It appears that provider visibility is restricted at the Dokploy layer before GitHub permissions are even considered. If so, granting additional GitHub org rights to the member would never help, since the permission check request never reaches GitHub.

Expected behavior

Git Providers should either be shareable across instance members, or there should be an explicit mechanism for an owner to grant access to a provider — similar to how projects and services are already shared.

Provide environment information

- Dokploy version: v0.28.6
- Traefik version: v3.6.7 (deployed by Dokploy)
- OS: Ubuntu 24.04
- VPS Provider: Infomaniak

Which area(s) are affected? (Select all that apply)

Installation, Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

• Similar issues reported in Issue #2912 and Issue #3489.
• The workaround of reusing another user's GitHub App URL does not work — it authenticates with the current user's personal GitHub account and returns their personal repos instead of the organization's repos.
• Note: in the GitHub Provider modal, clicking "Unsure if you already have an app?" with an org name returns a 404. This is expected GitHub behavior — the installations settings page requires org admin rights — not a Dokploy bug.

In the meantime, I will be trying one of the following workarounds:

• Use a Git via SSH provider instead of the GitHub App
• Use a shared Dokploy account (e.g. a dedicated "admin" user) to manage GitHub connections, so all members deploy through the same provider.

This issue makes it difficult for teams to collaborate on deployments, since it seems only the original creator of the provider can manage or modify applications connected to it.

Will you send a PR to fix it?

No

[Darkbound]

Agree, this is really an issue for us as well, we have to set up apps for every user, and when someone deploys with their GH App, only they can manage the deployment afterwards, not even me (Owner) can do anything in the Deployment config.

[EliasBorrajo]

Since I wrote this issue, our workaround is just to use a shared Dokploy account "admin" to manage GitHub connections.

Seems to work well in the meantime.

[Siumauricio]

@dosubot review

[dosubot]

Great bug report! Your analysis is accurate.

Good news: There's already an open PR #3509 that addresses this exact issue by removing the userId filtering, which would enable organization-wide Git Provider sharing.

Your report correctly identifies the root cause in git-provider.ts — the dual userId + organizationId filtering makes this a user-scoped resource when it should follow the organization-scoped pattern used by projects and other resources.

This issue was previously discussed in #2912, where maintainers acknowledged Dokploy wasn't initially designed for organization-level provider sharing but are open to fixing it. You may want to check PR #3509's status or add a comment there to help get it merged.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.