Project Server - Access Restrictions

[Randy]

We are in an organization that does not have cross
collaboration of projects (i.e. Project "A" stakeholders
and project managers should not see details or summary for
Project "B" or vice versa).

One thought is to create "projects" instead of categories
and assign people to the "project".

Does anyone have experience with this and is this the
correct way to handle this issue? It appears that you
can only identify a project plan in the admin category set-
up.

Thanks!

 

[Kevin Flanagan]

If you set up your RBS to reflect the reporting
structure, then only Project A team will see their
projects and Project B team will see theirs.

 

[Dale Howard]

Randy --

RBS stands for Resource Breakdown Structure. It is a very special custom
enterprise resource outline code field and is used as part of the Project
Server security model. The structure of the outline code in the RBS field
is used to show your company's "org chart" and the value in this field for
each resource identifies where the resource "fits" in the company org chart.

The RBS field is used in conjunction with the "My Projects" and "My
Resources" Categories in PWA, and can be used to control what projects and
what resources a project manager can see in both Microsoft Project 2002 (in
the Team Builder Wizard) and in Project Web Access. Hope this further
explanation helps.