Viewing projects/resources of your peers

[Michael Longdin]

Hi,

I hope I have explained the following question well enough for someone
to answer it.

How do I configure PS2003 to allow project managers to access projects
owned by other project managers at the same level in the RBS. The only
way I can see to do this (other than giving them access to everything
which I don't want to do) is to add all the other PM's as resources in
the the project concerned. BUT. How can I do this if the PM cannot see
those other PM's in the Build Team from Enterprise because they are
not below them in the RBS?

e.g. In the following RBS, I want PM2 to be able to access projects
owned by PM1 but not those owned by PM3

* Exec
* Programme Mgr A
* Project Managers Programme A (PM1, PM2)
* Analysts Programme A
* etc....
* Programme Mgr B
* Project Managers Programme B (PM3)

 

[Dale Howard [MVP]]

Michael --

Sadly for you, there is no default method for accomplishing what you wish to
do. The easiest thing to do would be to allow the PM's to see all projects
in the system, which could be accomplished merely by modifying the
Categories section of the Project Managers group.

Since you have very specific project-viewing needs, however, you will need
to use a far more laborious solution, which would be to create a custom
Category and Group for each set of project managers. You would need to add
each set of project managers to each custom Group, and would need to
manually add each set of projects for the group of PM's to each Category,
and include the correct Category with each Group. Every time a project
manager saves a new project in Project Server, you would then need to
manually add this project to the correct Category.

Probably not what you were hoping for, but this would be how to do it. Hope
this helps.

 

[Michael Longdin]

Thanks Dale. I had considered this but the admin involved sort of put
me off - not so much the set up but the bit about updating the
category each time a new project is created. I can't allow the PM's to
see all projects because the sensitive nature of some of them means
that there is no way I am going to be able to allow access outside
certain teams - but within teams it needs to be quite open. I think
I'll go with the idea of the PM adding resources to the project
resource pool each time and find a way for making sure the relevant
resources are available spmehow in 'Build Team from Enterprise'. This
way the emphasis is on the PM's rather than the Administrator i.e. not
me
Michael