-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
Please verify that this feature request has NOT been suggested before.
- I checked and didn't find a similar feature request
Problem statement
Hello,
We are using InvenTree in a quite big team by now and that causes a bit of friction with the user permissions. There is very different kinds of components tracked in our system from various groups which should not mess or sometimes even see the things the other groups do. Currently this seems not to be possible, so we limited the right to delete things to a select few individuals which then get bothered by everyone else if they create a faulty entry, but this is a very limited workaround and does not prevent other mistakes which could lead to losing information.
Suggested solution
Add a more granulate approach to user permissions based on part categories/stock locations and or project codes. A similar but not fully comparable access management is done in gitlab for reference. Like this you can give everyone only access to the information they need to see and a very detailed management on what can be edited by whom.
Describe alternatives you've considered
The only alternative I can think of would be creating multiple instances, each for the different group. however this obviously would have a lot of in regards to maintenance, interfaces between the groups, crossovers etc.
Examples of other systems
gitlab uses a project based user management system, where you can set the rights either for individual projects (the inventree equivalent would be parts) or project groups where the access right then go down in any involved subgroup and project (Inventree equivalent would be Part Categories/stock locations and parts/stock items)
Do you want to develop this?
- I want to develop this.