Turning off certain priviledges for very limited PM capability

[anovaktx]

We have a situation here where there are a handful of functional
people out in the business units we're going to turn loose on MS
Project Pro 2003 (against Project Server). The sole purpose is for
these people to manually update progress directly in the project plans
each week for a specific project (ERP Major Upgrade).

This is just temporary and I've checked off some things I plan to turn
off for them that PMs usually can do (using a custom group and
category for these folks). We don't want them adding people to
project teams, creating new plans, etc. Just update existing plans
that they are responsible for and save (no baselining).

Please scan these and let me know if there are any I need to leave on
for basic functionality (I wasn't sure about Manage Task Changes, Go
Offline from Project Web Access, and Read Enterprise Global). I'm
assuming turning off Set Resource Notifications will still allow you
to setup your own personal notifications.

Thanks ahead of time for your input!

Turning Off:
--------------------
Build Team on Project
Delete Project
See Enterprise Resource Data
Assign Resource to Project Team
Assign To-Do List Tasks
Build Team On New Project
Create Accounts (all that apply)
Create and Manage To-Do List
Delegate Task
Go Offline from Project Web Access???
Hide Task from Timesheet
Integration with External Timesheet System
Manage Rules
Manage Status Report Request
Manage Task Changes???
New Project
Open Project Template
Publish To-Do List to All Users
Read Enterprise Global???
Save Baseline
Save Project Template
Set Resource Notifications

Thanks,
Andy Novak
University of North Texas

 

[Dale Howard [MVP]]

Andy --

I don't have the time to test all of your settings, but there is one setting
is clearly going to trip up everyone who is in that custom Group. You must
set the Read Enterprise Global permission to Allow, or none of them will be
able to log into Project Server through Microsoft Project Professional.
Hope this helps.

 

[anovak]

Andy --

I don't have the time to test all of your settings, but there is one setting
is clearly going to trip up everyone who is in that custom Group. You must
set the Read Enterprise Global permission to Allow, or none of them will be
able to log into Project Server through Microsoft Project Professional.
Hope this helps.

Thanks Dale. I DO remember turning that off one time while testing
the permissions in general and I couldn't login to Project Server.
Hopefully, that's the only one that would give us a great deal of
trouble.

I tell you, if it wasn't for your books, I would be having a more
difficult time indeed. Thanks again for a great job on those.

Andy

 

[Dale Howard [MVP]]

Andy --

You are more than welcome for the help. Thanks for your kind comments on
our books. We are making excellent progress on our 2007 books.

 

[Gary L. Chefetz [MVP]]

Andy:

When you get your copy of the new 2007 book, you'll find that the first
chapter contains four classically bad reasons to implement Project Server,
one of which is "one big project."

--


Gary L. Chefetz, MVP
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
For Project Server Books: http://www.projectserverbooks.com
For Project Server Training: http://www.projectservertraining.com
For Project FAQS: http://www.mvps.org/project