Can available resources for assignment be restricted?

[NW]

Hi,

We are working towards a shared MSPS installation across orgs. A few orgs do
not want their resources to be in the Build Team list for all PMs to assign.
Is there a way I can restrict that? Custom programming is an option.

Thanks.
NW

 

[John]

Hi,

We are working towards a shared MSPS installation across orgs. A few orgs do
not want their resources to be in the Build Team list for all PMs to assign.
Is there a way I can restrict that? Custom programming is an option.

Thanks.
NW

NW,
One simple approach that comes to mind is a common shared resource pool
for sharable resources and entries on the Resource Sheet of each project
for non-sharable resources. However you need to be careful that resource
names are not duplicated in the common pool and individual files. In
other words, if you have a "Painter" set of resources in the pool, then
don't also have a "Painter" set in any separate file.

John
Project MVP

 

[Dale Howard [MVP]]

NW --

Since you are using Project Server, you have a couple of options:

1. Create a separate Project Server instance for each organization that
does not want anyone else to see their resources (or projects). You would
need to use a third party application such as Crystal Reports or SQL
Reporting Services to report across the multiple Project Server instances.

2. Use a single instance of Project Server, but use custom Groups and
Categories to controll everyone's access to resources and projects.
WARNING: This approach is very labor intensive for the Project Server
administrator, since it requires him/her to manually add resources and
projects to each Category.

Just a couple of ideas. Hope this helps.