You could tell from the topic that I’m fairly new to ProjectLink…
I’ve read the old doc (we’re on 10.2 M030) “Integral Operations Between Windchill PDMLink and Windchill ProjectLink”, ploughed through topics on this forum, tested ACL, but it all don’t quite come together.
The scenario is not new. There’s a requirement that external designers (contractors) access CAD-data and Parts via ProjectLink. To make it more simple for own users we’re going to have only one product context in PDMLink. Some of the externals should be limited with what they see in PDMLink, others probably could see all. If possible, externals could be allowed to work on Released / Approved content ie. revise, but since Modify rights are required in PDMLink to be able to work on items shared to ProjectLink this does not seem like an option.
How do you set it all up? How to limit what they see in PDMLink?
Solved! Go to Solution.
Actually, all the work is done in the Project on the ProjectLink side of Windchill. (See screenshot.)
This way the external team members can only see what has been shared to the folder they have access.
For Supplier A and Supplier B access being different, you would have to have separate roles and folders. Or separate Projects. Having separate projects might be easier to administer, because once you had the roles and folder and security set up and working, you could use that as a template for the additional projects and just put different people in those roles.
-marc
You can use the role based domain policy in your product context.
The way we have handled this situation is to have a role(s) on the team for the external team members. In our case, there are two, Customer and Supplier. We give them limited access to one folder each, a Customer folder and a Supplier folder.
Process:
-marc
CAD / PLM Systems Manager
TriMark Corporation, New Hampton, Iowa
By default all context roles assigned to the group "Team members" and have all permissions.
You must delete permissions for the "Team members" and make the separated permissions for the customers and for the suppliers by policy administration utility.
The suppliers can have permissions only for specific state of your lifecycle.
For example:
First a big thank you for the replies! These communities are just great.
Marc, let me get this right.
What are the details in Policy Admin regarding product context folders? You have deleted everything related to Participants “All” and “Team Members” (as Sergey suggests regarding the EPM docs and Parts which makes sense and we have in place already) regarding object type “SubFolder” and manage folders entirely via “Manage Security”?
This could be laborious with several folders, but the idea I read somewhere that you create folder domains in Policy Admin sounds possibly worse.
Also, do you ever need to manage situations where supplier A should not see the same content as supplier B? This would mean separate roles, separate folders..
Actually, all the work is done in the Project on the ProjectLink side of Windchill. (See screenshot.)
This way the external team members can only see what has been shared to the folder they have access.
For Supplier A and Supplier B access being different, you would have to have separate roles and folders. Or separate Projects. Having separate projects might be easier to administer, because once you had the roles and folder and security set up and working, you could use that as a template for the additional projects and just put different people in those roles.
-marc
Coming back to this after a while...
Thanks a heap for the answers! You've pushed us in the right direction.
Unfortunately can vote only one as Correct answer
Thank you for returning and posting that Janne.
Best,
Toby