How can allow the people to view the projects in a different RBS l

[GG]

Hi:
I got a question for the access permission. We have some people in QA team
who wants to see the projects in our engineering team. The QA team is in a
different RBS level. I set all the access right related to the
project/project center. But they still cannot see the projects we are working
on. I guess it is because we are in different RBS level. Is there anyway to
grant the access right to people in other RBS level to see the projects?

Thanks
Rock

 

[Dale Howard [MVP]]

GG --

Since you are strictly using RBS to control access to projects, you will
need to create a custom Category and Group that give access to the
engineering projects, and then add the QA users to that Group. You will
find this solution a bit labor intensive, however, since you will need to
manually add the engineering projects to the Category. Every time a new
engineering project is created, you will need to manually add it to the
Category as well. Hope this helps.

 

[GG]

Hi Dale:
Thanks for your answer. I did create a special category and a group for the
people. And in the new category, I set "All current and future projects in
Project Server database". I suppose all the project would be by default added
in the category. But it didn't work.

I notice there are some options I can set:
The User is the Project Owner or the User is the Status Manager on
assignments within that Project
The User is on that project's Project Team
The Project Owner is a descendant of the User via RBS
A resource on the project's Project Team is a descendant of the User via RBS
The Project Owner has the same RBS value as the User

But I don't see they are link to my case.

P.S. I sent my reply to a wrong location...This should be the correct thread

Cheers
Rock

 

[L8rdays]

Hi,
I handled this scenerio a little differently. I had different groups and
some needed to see in other groups, but not all groups. Some groups needed
to see all projects, and some groups just needed to see their groups
projects. Since this crossed over the RBS boundries I did the following and
it is working out.

I created a custom project field based on Division.
I then created groups and categories for each Division.
Then I created views based on the custom project field.
I technically allowed all project view in the permissions, but limited what
they could see with the views based on the custom field. Also with my
settings when they opened up Project Professional they could only see and
open projects they own.

So now:
Group A needs to see all projects
Group B needs to see Group A projects and Group B projects

So the views allows Group A to all current and future projects
Group B is set to all current and furture projects, but has access only to
Group B custom view and Group A custom view.

Just another way to do it.