6. You’ll See… The access Control difference between Intralink 3.4 & Windchill How to reproduce Intralink 3.4 access control out-of-the-box in Windchill (hint: lots of clicks, headaches & indigestion) How Fishbowl Solutions’ linkSecurityautomates the access control administration process so you can stop popping the antacids.
7. So, #1… What’s The Difference between Access Control In Intralink 3.4 and Windchill?
8. Intralink 3.4 has a “rigid” access control structure implemented within a single interface
9. Windchill has “flexible” access control configured in multiple interfaces & used in a variety of ways
10. Windchill Access Control Challenges Objects do not simply inherit folder permissions in the expected manner Team roles apply to the entire context. This yields large numbers of Products and admin overhead in order to maintain the access control granularity desired by many companies. Ad Hoc policies have unexpected behaviors – they remain in effect after an object is promoted. Visibility is challenging - making them difficult to remove when done. Configuration is complicated due to multiple interfaces. The administrator must decide how the components work together.
11. Components of Windchill Access Control Windchill Domains A Product/Library has a single “Default” domain OOTB The domain contains the access control rules Domains can be assigned to one or more specific folders Domains inherit access control rules of parent domains
13. Components of Windchill Access Control Access Control Rules Each rule applies to a hierarchical object type Each rule can be applied to either a specific lifecycle state or across all lifecycles Each rule applies to a user, group, organization, or role Each rule contains permissions that either allow or deny operations such as Read, Create, Modify, Revise, etc…
15. Components of Windchill Access Control Team Page Each Product/Library has a team page where users and groups are assigned to one or more roles The roles may be global or local to the specific Product/Library Note: Shared teams may be leveraged if you have common teams that apply across multiple Products or Libraries
16. Components of Windchill Access Control Folder Properties Allows a folder to be assigned to a non-Default domain The preference: Security; Default Folder Domains; must be enabled to make this functionality available.
17. Ok. #2. By now you’re probably asking yourself… “So how do I regain my Intralink 3.4 folder access control using these components?”
18.
19. Hierarchical structure must be mimicked to supply expected rights inheritance. Example: an individual who has rights to modify in the Interior folder would expect rights to modify in Dashboard folder as well. If Dashboard domain was not a child of Interior this would not happen.
24. Complexity - The Policy Administrator tool can be complex for casual users to learn. Product and Library Managers need to be familiar it to be effective
25.
26. Fishbowl Solutions linkSecurity Folder Access Control Implemented within a single simplified user interface Never go into the Policy Administrator tool.
31. The familiar Team tool is still utilized to assign users and groups to folders. You get the benefit of automation without the learning curve.Features & Value Quality LinkSecurity insures that domains, teams, folders, and access control rules are correctly configured. Compatibility LinkSecurity automates the removal of domains and teams when folder access control is no longer desired on a particular folder.
32. linkSecurityConclusions linkSecurityprovides a simplified user interface that allows a company to regain the folder access control that they were accustomed to in Intralink 3.4 linkSecurityhas been used to automate configuring folder access control on as many as 1,200 folders on a single system - with no performance degradation (validated using Fishbowl Solutions LinkTuner product.)