1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
We are automotive and my role is solution Architect & Implementation Specialist.
2. What product and version are you currently running?
Windchill RV&S. Soon going on 12.5
3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
Currently when we break permission inheritance tree on child project we can provide any groups which should be having access to this project. But it doesn't help if any user doesn't have permission of it's parent. Then this break permission is not adding any value because we always have to give parent permission.
E.g. /ABC - Parent or Main Project
Now DOC is child of ABC so structure is :- /ABC/DOC.
Now if below group DOC Administrator, DOC ReadOnly and DOC Team has no access of /ABC they can't access DOC also. Then this restriction is not helpful.
Wish is if specific group is selected and permission inheritance is broken then it shouldn't be mandatory to have parent project access, instead this child project should work independent of main project now.
PS: This was also an use case during PTC Work Group meeting.
Vielen Dank / Many Thanks,
Kapil Jain
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.