S
Steven Douglass
Project Pro 2007 | Project Server 2007
I'm experiencing some unusual behavior when using the Build Team feature of
PPro 2007 and the resulting permissions in the Project Workspace.
When I initially create the project plan, I use the Build Team feature to
include resources that initially do not need to have anything other than read
rights. I publish and then see that they have Readers (Microsoft Office
Project Server) rights, which makes sense.
When I assign one of those resources to a task in said project, I would
expect that the rights would change to Team members (Microsoft Office Project
Server), unfortunately, they remain as Readers (Microsoft Office Project
Server) which means they cannot contribute to any workspaces.
To deal with this, I have determined that if the user is first removed from
the team, the project plan published, then the user added added again AND
assigned a task, then the project published again, they end up with the
expected rights (Team members (Microsoft Office Project Server)) and all
project resources have received 2 e-mail notifications...
Does anyone have a SOLUTION that provides the expected automated (and
correct) updating of user rights when the resource becomes tasked?
Note: While this is considered a workaround, the number of workarounds I'm
needing to manage projects & resources in PS2007 is becoming overwhelming.
Thanks,
- Steven Douglass
I'm experiencing some unusual behavior when using the Build Team feature of
PPro 2007 and the resulting permissions in the Project Workspace.
When I initially create the project plan, I use the Build Team feature to
include resources that initially do not need to have anything other than read
rights. I publish and then see that they have Readers (Microsoft Office
Project Server) rights, which makes sense.
When I assign one of those resources to a task in said project, I would
expect that the rights would change to Team members (Microsoft Office Project
Server), unfortunately, they remain as Readers (Microsoft Office Project
Server) which means they cannot contribute to any workspaces.
To deal with this, I have determined that if the user is first removed from
the team, the project plan published, then the user added added again AND
assigned a task, then the project published again, they end up with the
expected rights (Team members (Microsoft Office Project Server)) and all
project resources have received 2 e-mail notifications...
Does anyone have a SOLUTION that provides the expected automated (and
correct) updating of user rights when the resource becomes tasked?
Note: While this is considered a workaround, the number of workarounds I'm
needing to manage projects & resources in PS2007 is becoming overwhelming.
Thanks,
- Steven Douglass