Project Server 2007 Security Setting

[Frank J.]

Project Server 2007 w/SP1


The security settings within Project server seems very powerful and very
complex. I have been trying combination to achieve the following... but
haven't gotten the results I need... I'm hoping someone out in etherland can
help.

I would like to set up a scenario were person can do the following via PWA:

All the rights that come with TEAM MEMBER settings
Plus the ability to directly open a project for modification on to their
local machine (you can assume they have ProjectPro 2007 installed locally)

This would allow them to make any changes they required to a project....
however, I do NOT want them to have the ability to PUBLISH. The update
project would need to be "emailed" to the project manager for review before
it (he/she) publishes.

Related question:

Within PWA Team Member have ability to track actual task hours, add hours to
a task, mark a task completed, and even assign a task to another Team member.
Can I give them the ability to do more (like add or delete tasks directly
through PWA???

Thanks

Frankj

 

[Ben Howard]

Hi Frank,

You can certainly give a group rights to open all projects, but the
functionality around "emailing" isn't there. The nearest you'll get to this
without custom code is to save the modified Projects to the drafts DB, and
then have the PM open it up and publish it if they approve. If they don't
approve, then can communicate the alternative changes and get the project
modified to their approval. Once done, the PM can then publish the project.
There is no way to keep the original project though and have the modified one
in the DB at the same time - it would all get too messy renaming projects.
The permissions required to do this are easy enough, I would create a
category call "open and save all projects" and assign check "All future and
current projects in the database", and then create a new group called
"project modifiers" and assign them this category, and check the category
permissions to Open and Save projects (but not publish). They'll need global
perms simililar to the PM group.

As per the 2nd question - they can delete tasks but the PM needs to approve
this, they can create tasks too.

 

[Frank J.]

Thanks Ben.... but that's not quite my question (I always tell people, it's
not what I say, it's what I think ).

The real question is what is the proper settings to allow them to open the
project (again assuming they have Pro on their local PC).... the email would
be a manual process... but your thoughs on storing to draft db sounds
interestings.

Also would like more details on how they can (via PWA) add and delete
tasks... with PM approval.

Thanks

Frankj

 

[Ben Howard]

Hi Frank. The security permissions needed are pretty much detailed in my
response. Regarding adding/deleting tasks, you would do this via the my
Tasks page, so there are a couple of caveats.

1. the person doing it would have to be a team member (I think)
2. the project needs to be published already.

this process would actually be a different one to the "emailing" process
described below, and it's abit of a work-around. PWA isn't designed as an
editing interface to Projects.

 

[Gary L. Chefetz [MVP]]

I would further add a caution about the delete task function. It does not
respect effort-driven scheduling, so it may not be the best feature to use
at the moment.

--

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