PS2007 -Project Owner Can't See New Resources!

[Rick F.]

They are members of a project Team on a project owned by the Can someone
please give me some feedback on what would be causing the Project Owner to
not be able to see resource information in the follwing setup?

For security reasons (folks only allowed access to certain programs), this
project has its own PM group and category. The category tied to the PM group
is set as follows:

- Projects: Project Owner can only see the specific project in question.
- Resources: Set to Only the resources indicated

User is the Resource
They are members of a Project Team on a project owned by the User
They are descendants of the User via RBS
They have the same RBS value as the User

Team members have their own group and category. The category tied to the PM
group is set as follows:
- Projects: Project Owner can only see the specific project in question.
- Resources: Set to Only the resources indicated. None checked

Two new resources were requested to be added to the program. They were added
to the Team Member group and added to the project as resources by the admin.
Note: these resources are also used on another program at the same level in
the RBS structure, so one level up so they can see both programs (the Project
Owner not allowed to see both programs)

The Project Owner now gets a message when he opens the project that he is
not authorized to view these resources. If they are assigned to the project
and in the correct group/category, why does he get this message and how do we
fix? Note: I setup a test resource and assigned to this same PM group and can
see the resource no problem. This is very puzzling.

Any help on what may be set wrong and how to correct is greatly appreciated.

Thanks

 

[Gary Chefetz]

Rick:

When the admin added the resource to the project, did the Admin publish the
changes? Only the publish job would kickoff the permissions synchronization
job necessary to propagate the new permissions in the system. Simply saving
the project would not.

 

[Rick F.]

Ah... good call. Let me go check that.

Rick:

When the admin added the resource to the project, did the Admin publish the
changes? Only the publish job would kickoff the permissions synchronization
job necessary to propagate the new permissions in the system. Simply saving
the project would not.

 

[Rick F.]

Thanks Gary, that was the problem. It was saved, but not published. The
Project Owner published and now he can see the info.

 

[Gary Chefetz]

Glad it was something easy.