We are using Project Server 2010, with RBS for our Enterprise Resource/user reporting, and Microsoft Project Professional 2010.
We create projects with generic resources and then the various team leads are suppose to go in and assign actual resources to the tasks. If this process is done using PWA enabled for editing, the limitation of only seeing resources that are decendants for
your RBS works fine. A team lead cannot assign a resource from another team.
HOWEVER, since making mass changes etc is so much easier in MS Project 2010, the team leads prefer to use this method to replace the generic resource with someone from their team. BUT here comes the problem. The team lead opens MS Project 2010 with a default
profile connecting them to Project server . The Open the project via the Enterprise Projects stored on Project Server 2010, They get a "message" that lists resources assigned to the project that do not report to this team lead which they acknowledge. However,
when they get to the task that they are going to update, the WHOLE project team is shown and the Lead is able to select resources that do not report to him. Not error message or restriction occurs.
We have had individuals select names from the list who do not report to them and after they save > publish > closed; the task has two direct reports and a person not on their team (call this person not on team, Recource D). How can I stop leads from
selecting people not on their team? Eventually when Resource D tries to look at their tasks, an "unkown error" occurs because the Resource D (selected via MS Project 2010) is not considered a "true" Enterprise Resource by Project Server 2010.
