When a workshop is shared, production recipes (and therefore batches and controls) and Equipments may shared or PRIVATE to a group of users.
We propose to add a "owner" field to recipes and to components (places, equipments, containers):
a Group of Users (functions) may be specified in this field and will list all users "owning" the recipe or the component
any sub-recipe and their linked batches or controls will be accessible (read and write) only within the owning group (and by the site admins)
the components information may be seen (or not: boolean field) by non-owners (so they now they exists) but they cannot be used by them.
Implementation: we suggest to extend / rename / improve the "isActive" function so it does not give access to non owned data: "isUsable(current user)" and "isReadable(current user)" ? About 6 hours job...
When a workshop is shared, production recipes (and therefore batches and controls) and Equipments may shared or PRIVATE to a group of users. We propose to add a "owner" field to recipes and to components (places, equipments, containers):