Dokploy / Dokploy/dokploy

Allow creating users via API without invitation (service users)

Open
#3,358 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

Dokploy has a solid API for automating infrastructure and application provisioning, but currently user creation is invitation-only. This creates a hard blocker for fully automated, multi-tenant integrations (e.g. WHMCS, SaaS platforms, internal PaaS offerings).

For API-driven platforms, invitations introduce human interaction into flows that must be fully automated:

  1. Cannot silently provision isolated tenants
  2. Cannot create per-organization service users
  3. Cannot generate per-tenant API keys programmatically
  4. Forces operators to reuse a global admin API key, increasing blast radius and security risk
  5. This makes Dokploy difficult to use as a backend for hosting providers and SaaS platforms.
Describe the solution you'd like

Proposed solution
Introduce API-based user creation without invitations, specifically for service / automation users.

Example
POST /api/users { "email": "service-client-123@internal", "name": "Client 123 Service User", "organization_id": "org_xxx", "role": "developer", "type": "service", "skip_invite": true }

Describe alternatives you've considered

We can't move on an build a solid integration.
No alternatives found.

Additional context

No response

Will you send a PR to implement it?

No

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing POST /api/users endpoint and its invitation flow. Review how organization_id, role, type, and API keys are handled, then define the service-user path so automated creation works without an invitation while preserving tenant isolation and limiting security risk.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, authentication, authorization, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.