Client Project Separation

[Open mind, Firm decisiions brings peace]

Hello,

We want to use Project Server 2007 and PWA in order to easily discriminate
clients via the user PWA Home Page.

By this I mean that we want to have a client list on the home page, and upon
clicking on a client link, we want to see the client's list of projects in
their workspace. In this workspace, each client project workspace can be
accessible, via a suitably filtered "Project Workspace" webpart.

I can fudge a manual way by creating sites, (although I cannot do this for
the "Project Workspace" webpart) but I'd hoped that this would be a native
feature of project. Is this something that Project Portfolio is for?

Thanks for your help.

Jahveen

 

[Paul Conroy]

have you thought of creating a separate project server instance for each
client ?

Alternatively you can create a category for each client if you want to
report across all the clients portoflios.

hth

Paul

 

[Open mind, Firm decisiions brings peace]

Hello Paul,

We would certainly want to report across the client portfolios and we have
dozens of clients, so it would be impractical for us to create a separate
project server instance for each one.

Giving each client a different category puzzles me though because it only
appears to be a form of access control.

One article that has helped me in my research was the following:

http://www.sharepoint-tips.com/2006/07/modifying-wss3-tree-navigation-control.html

It helped me to create a more visible way of navigating through client areas
and their projects.

If I try to perform this on the PWA home page, I receive a "The
enablesessionstate attribute on the page directive is not allowed in this
page" error - and then I have to restore pwa from backup.

Is it possible to edit the PWA home page named "default.master" - or is it
possible for me to create a replacement one?

 

[Gary L. Chefetz [MVP]]

Jahveen:

One way to accomplish this is to set your project workspace creation to
manual. Create a Master Project for each client (Could be an empty file
simply used as a placeholder), and extend a Project Workspace for each
client master. After creating a master workspace for each client, provision
all project workspaces for that each client's projects under the master
site.

The Project Workspace webpart is a bit underwhelming in its flexibility, so
you might want to simply display a link list in a standard web part on the
home page containing links only to the master sites.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


"Open mind, Firm decisiions brings peace"

 

[Paul Conroy]

The functionality of webparts improves when deploying project server with
MOSS as you're then able to make use of targeted audiences which will give
you what you need. The down side is the extra licencing costs

 

[Open mind, Firm decisiions brings peace]

Hello,

Thank you for your help.

Do you know of any books or online case studies which have shown how "client
oriented" project server 2007 implementations like the one I want to create
have been constructed?