amplication / amplication/amplication
Server/Client: Role based Object ownership and CRUD permissions
- Lenguaje dominante
- TypeScript
- Estrellas
- 16k
- Forks
- 1.5k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
**Is your feature request related to a problem? Please describe.**
When setting permission roles, we could do with the concept of a ownership domain as well as the existing granularity
**Describe the solution you'd like**
It would be great if you could set the CRUD operations for the role in one of the following domains.
- Objects in Model the User has created
- Objects in Model created by any User with the same Role
- Objects in Model created by any User for a specific Role
- All Objects in Model
I would be even better if these were additive so I could have a user that could manage Objects they had created but also manage those for a different Role too.
** Implementation Requirements **
I would imagine that the base object model would need to include a Created By property for all Objects as a minimum
** Example **
- Basic App User - can only CRUD objects they have created
- Manager User - can CRUD all objects created by Basic App Users (or those in their Role)
- Super Admin - can CRUD all objects
Guía de contribución
Evaluación
Este issue todavía no se ha evaluado.