Feature Request: Inheritance System for Permission Management
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
Currently, permissions in Dokploy must be set manually for each individual service under a project. This process can be time-consuming and inefficient, especially when managing large projects with multiple services or when new services are added to an existing project. Users need a more scalable and automatic way to manage access rights, ensuring that permissions apply consistently across all components of a project, including future services.
Describe the solution you'd like
Implement an inheritance system for permissions where granting access to a project automatically grants access to all services under that project. This system should:
Allow users to inherit access to all existing services when they are granted access to a project.
Automatically apply the same permissions to new services created under that project in the future.
Provide the flexibility to override inherited permissions at the service level, in case specific services require different access controls.
Describe alternatives you've considered
One alternative is to manually update permissions each time a new service is created, but this approach is not scalable for larger projects or organizations with frequent updates. Another option is to create predefined permission templates for services, but this still requires manual assignment for each service and does not solve the issue of applying permissions automatically to future services under a project.
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the existing project and service permission model, then trace how permissions are granted and applied; done means project access covers existing and future services while allowing service-level overrides.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100