We want to allow certain users (=identity) to modify parts of our AF structure.
For example we have a structure Elements\Wärmetauscher\Anlage1 with several heat exchangers (=Wärmetauscher) as child elements.
Now one special user should be able to add, modify and delete heat exchangers from "Anlage1".
Currently we have to give his identity the right to modify "Anlage1". Unfortunately in this way he also has the right to modify Anlage1 itself and not only the right to modify (and add and delete) the childs of Anlage1.
So we think there should be a seperate right to modify child elements of an element.
ADMIN RESPONSE
Aug 19, 2022
It is currently not possible to allow add/delete of child elements, but not allow modifying the parent element. We current have no plans to add this capability.
We would like to be able to take certain parts of the hierarchy and carve out areas so that certain groups have write access to the areas of the plants they are responsible for. After discussions with OSI it seems this can only be done at the database level. It would be valuable to allow the right people with applicable technical skills/area ownership write access to their area while limiting it to read access only in other areas.
In response to Matt Clark, "We would like to be able to take certain..."
New child elements inherit their security from their parent element. So you can create separate parts of the hierarchy and set the security on the parent element of that part and then any new elements created under that part of the hierarchy will inherit the security of that parent element.
