Redirecting Notifications

[Steve Lundwall]

I have a situation I'm sure you can all advise me on. The advice will
probably be - "don't do it!" Unfortunately, I've been given my marching
orders. We have a functioning Project Server 2003 set up and I am the
Project Manager on all projects - except one. We have now bought Project
Professional 2003 for three other people and connected them to the server so
that they can set up and handle one very large project outside of our
division. We have the skeleton of the project set up and they are all able
to set up tasks, publish and such. I am advising them to set up sub-projects
and try not to walk all over each other. However, I need to know something.
Right now all the Project Server notifications are coming to me. For this
one project (or set of sub-projects) I need the notifications to go to
them - and actually to all of them - not just one of them. Any one of the
three should be able to approve task updates, changes, etc.. I simply want
to be able to pull things up to view, review and comment.



So, is this possible?

Is this advisable?

Can I do multiple notifications?

How do I set this up and change the target for the notifications?



Thanks. Your help and advise would be most appreciated.



Steve

 

[Dale Howard [MVP]]

Steve --

You are absolutely correct in advising each PM to set up his/her own
projects as subprojects of the one large program. Concerning the updates
from all team members going to you, refer to the following FAQ for the steps
needed to redirect task updates to the PM of each subproject:

http://www.projectserverexperts.com/Shared Documents/changeprojmgr.htm

Also, the system can only designate one person to be the Manager of tasks in
any project. Therefore, you would need to do one of the following to solve
your who can process task updates situation:

1. Live with the fact that the PM of a subproject is the only one who can
receive and process task updates from team members in that project.

2. Set up a Project Server-authenticated user account into which all three
PM's can log in and process task updates. Because this account would use
Project Server authentication, this means the PM's would not be able to
access the Risks, Issues, and Documents functionality of Project Server
through that account. To access those features, each PM would need to log
into PWA using his/her own account that is authenticated using Windows
Authentication.

Also, I hope you have not published the master project that contains the
individual subprojects. Doing so can lead to duplicate task assignments on
each user's timesheet in PWA. Hope this helps.

 

[Steve Lundwall]

Thank you, Dale. That is very helpful. We are so early on in this bigger
project that the advice can be fully implemented without having to back up
and start over. And no, we don't 'publish' any Master Projects. As a matter
of fact, I have that enterprise option turned off. Thanks again.

Steve

 

[Steve Lundwall]

Dale,

You implied that you can't use Risks, Issues and Documents associated with a
Project unless you are using Windows Authentication. We are a Novell shop
without Active Directory. I have had to set everyone up using Project Server
Authentication. No one is set up with Windows Authentication. (I set
everyone up to have certain rights on the Windows 2003 Server Box that
Project Server is sitting on as well with a separate server logon) We are
using Risks, Issues and Documents with everyone signing on using Project
Server Authentication. Did I misinterpret something in your statement?

Steve

 

[Dale Howard [MVP]]

Steve --

By default, users cannot access Risks, Issues, and Documents in PWA unless
they use Windows Authentication. Anything else would require customization.
That's all. Hope this helps.

 

[Steve Lundwall]

Hence my confusion. We didn't do any customization yet we are using Issues,
Risks and Documents and people are using Project Server Authentication. I
wonder if that is alleviated since they have a second logon to the server
(which they get asked for) when they try to access Documents for example.
Thanks for the help.

Steve

 

[Gary L. Chefetz [MVP]]

Steve:

It is possible to use the SharePoint resources without active directory
using one of two methods:

1) Wide open security, essentially anonymous access to everything
2) Local logons

You have apparently opted for option number two, so you're good to go.