Fix :: #5468 Split permissions for organization projects
Merged
RA
4y ago+520+520+012345678901234567890123456789-304-304-012345678901234567890123456789
PR
- Have you followed the contributing guidelines?
- Have you explained what your changes do, and why they add value?
Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.
Fix :: #5515 (Split Projects Permissions)
Description of change
We split organization projects permissions into 4 type as below.
- ORG_PROJECT_ADD - Users must be able to new projects.
- ORG_PROJECT_VIEW - Users have access to the projects in the UI by reading the projects.
- ORG_PROJECT_EDIT - Users have access to modify existing projects.
- ORG_PROJECT_DELETE - Users have ability to delete projects.
@evereq I would suggest to test this funcationality for now in demo server, if everything is fine we can release these changes.
Note: By default admin have all permissions, but employee have only read, create permissions for project only for new users. For old users we have manually change permissions for employee roles, otherwise they won't be able to retrieve any projects.