Protect libraries from modification
Using RBF, I wish to create a set of libraries which can be used by users in a variety of access groups, but can only be modified by users in an "admin" access group. Is this possible?
If not, then we have the risk that shared libraries can be modified by anyone who can access them.
If not, then we have the risk that shared libraries can be modified by anyone who can access them.
2 answers
Using RBF, I wish to create a set of libraries which can be used by users in a variety of access groups, but can only be modified by users in an "admin" access group. Is this possible?
If not, then we have the risk that shared libraries can be modified by anyone who can access them.
Hi Andrew,
I'm not sure how many things you have tried at this point. There are a set of permissions that you may want to try adjusting on your access groups. If you navigate in the UI to 'Administration -> Permissions', the main permissions in the area of projects/steps to modify are the 'Edit Project Settings', 'Delete Projects', 'Edit Step Settings', and 'Delete Steps'.
Best regards,
Brent Ulbricht
Build Forge Test
Using RBF, I wish to create a set of libraries which can be used by users in a variety of access groups, but can only be modified by users in an "admin" access group. Is this possible?
If not, then we have the risk that shared libraries can be modified by anyone who can access them.
Hi Andrew,
I'm not sure how many things you have tried at this point. There are a set of permissions that you may want to try adjusting on your access groups. If you navigate in the UI to 'Administration -> Permissions', the main permissions in the area of projects/steps to modify are the 'Edit Project Settings', 'Delete Projects', 'Edit Step Settings', and 'Delete Steps'.
Best regards,
Brent Ulbricht
Build Forge Test
Thanks Brent. I have seen these settings, but the problem is that users need these permissions for their own projects, but I do not want them to be able to modify common libraries.