Security profiles define project access based on classes and metric values associated with a project and a user. The class and metric value settings assigned to a project must match those assigned in the profile that is assigned to a user for the user to have access to the project information. Two users in the same access group can have access to separate sets of projects in that group using two different security profiles.  

a.        Limiting the classes and Models I see when I click ‘Add New’ – I should only see my GBU’s Models listed

b.        Limiting my view to the non-export control projects if I don’t have access to those projects that are flagged.

c.        Giving access to the WEGO1 archive of projects which contains both the migrated and previously closed projects.

If a User need to have access to a shared    pipe,   for example an R&I user working with many GBUs you have 2 options :

1. Give that User an additional security profile for the GBU he or she is working with.  This will give access to all the projects in that GBU related to the Access Group
   
2.  Make that User a Team Member of the individual shared  pipe  project.  This will give access to just that one project and to not other projects from the GBU