@LM_Silva wrote:
Version: Windchill 12.1
Use Case: Hello everyone, I'm seeking insights and real-world examples on the use of Shared Teams versus Team Members within the Windchill ProjectLink module.
Description:
Can anyone share scenarios where you found it beneficial to use a shared team instead of adding individual team members?
Why does the assignment of a shared team override the "Private Access" setting?
What are some best practices for deciding when to use shared teams versus individual team members?
Looking forward to your insights and experiences!
Best regards,
Hello, @LM_Silva
When considering the use of shared teams versus individual team members in Windchill ProjectLink, several factors come into play. Shared teams offer efficiency and consistency by allowing a collection of roles and associated participants to be used across various application contexts. Any changes made to a shared team immediately apply wherever it’s used. This minimizes user administration and ensures uniformity. However, shared teams override the “Private Access” setting because they are designed for broader access control. When deciding between shared teams and individual team members, consider context-dependent needs. If roles and participants remain consistent across multiple contexts, shared teams simplify management. For specific access control scenarios, individual teams may be more appropriate.
Remember to optimize team structures and categorize permission requirements based on context independence.
I hope this info is helpful to you.
Best Regard,
Gregory Chavez
