PWA Resource/Admin Access

J

Jim Raynor

Hi,

I am new to project server 2007 and I have a few questions. Regarding
resources for a project, what is the difference from selecting "building a
team" and "creating a resouce plan?" They both appear to be able to
create/add users as resources, so are they just the same?

My other question regards team and project manager permissions. For example,
I set a user as a team member, and then I create a new project and assign
them the administrator of the project. They are not able to publish the
project or do anything (I suppose this is normal since they are only
members?). But if another user with project manager privileges is a resource
of a project, they seem to be able to edit the project. I do not want this to
happen, so is there anything I can do?

Basically, I have a team of users, and would like to set permissions so that
they are all just "members", yet can have "manager" privileges (i.e.
approviing changes) for a specific project, while only "member" for other
projects being worked on simultaneously?

I assume this may relate to setting permissions. To edit a user's settings,
is it sufficent to set the security group they belong to, or should I only
set their global permissons, or both? Thanks in advance for your help.
 
D

Dale Howard [MVP]

Jim --

When a PM builds a team of resources for a project, he/she must then assign
the resources to tasks. A Resource Plan is a way of "reserving" resources
for specific time periods in a future project without actually assigning
resources to tasks.

People who are team members only do not need Microsoft Project Professional
2007 and you should not be setting them as the administrator (?) of a
project. I have no idea what you mean by administrator. Owner? Manager?
What?

If a team member is also a project manager in your system, you can limit
permissions to allow each PM to only open and edit his/her own projects by
doing the following:

1. Log into PWA with administrator permissions.
2. Click Server Settings - Manage Categories.
3. Click the My Projects category to open it in editing mode.
4. In the Projects section of the page, deselect the second and fourth
checkboxes that are currently selected.
5. Click the Save button.

Hope this helps.
 
J

Jim Raynor

Hey,

Thanks for the clarification on the resources. By administrator I meant
project owner. I followed your steps to set PM permissions limiting, however
I do not think its working exactly how I want to. The PM's are only able to
edit projects they manage (what I want), but they can't see any other
projects that they've been put in as a team. If I assign a task to them, they
are able to see the task and change the status of that task specifically, but
cannot access or even view the project at all (I don't want this). Is this
normal? If so, is it possible to set it so that they can access project's
that arn't theirs, but still view them? Thanks again.
 
D

Dale Howard [MVP]

Jim --

This is easier than you will ever believe. Do the following:

1. Log into PWA with administrator permissions.
2. Click Server Settings - Manage Groups.
3. Click the Project Managers group to open it in editing mode.
4. In the Categories section, add the My Tasks category.
5. In the Permissions for My Tasks permissions grid, set the following
permissions to Allow:

Open Project
View Project Details in Project Center
View Project Summary in Project Center

NOTE: The first permission will allow your PM's to see and open Read-Only
any project in which they are team members only. The other two permissions
will allow them to see the projects in the Project Center page.

6. Click the Save button.

Hope this helps.
 
J

Jim Raynor

Well after playing around for a bit, I finally got it to work like you said.

Thanks Dale. Really appreciate it!
 
D

Dale Howard [MVP]

Jim --

Way to go, my friend! You are more than welcome for the help. Remember:
KISS is the key to managing Project Server 2007 security! :)
 
Top