Currently permissions are per content type and are checked in the list-view endpoints (projects/, deployments/, jobs/ etc).
Consider moving these to one place under the current user object. This should work for content-type level permissions like "project_create", however I am not sure how to handle object-level permissions like "project_update".
Reminder to consider adding an Organization entity for which users belong to and inherit permissions from. Multiple projects belong to an Org. Users can modify any project in org by default.
Currently permissions are per content type and are checked in the list-view endpoints (projects/, deployments/, jobs/ etc).
Consider moving these to one place under the current user object. This should work for content-type level permissions like "project_create", however I am not sure how to handle object-level permissions like "project_update".
Reminder to consider adding an Organization entity for which users belong to and inherit permissions from. Multiple projects belong to an Org. Users can modify any project in org by default.
Consider looking at https://github.com/keycloak/keycloak