what is "assigned to a project"?

[Jim Sinclair]

For RBS permission "Allow users in this category to view
all projects assigned to resources that they manage" what
does "assigned" really mean? Is it sufficient for the team
member to be included in the project team (via Build Team)
or must the team member be assigned to a task before their
line manager finds the project is in the category?

I don't have a server right now to check - I'm not being
lazy - I'm sitting writing documentation.

Thanks
Jim

 

[Kevin Flanagan]

It referes to the action of publishing the project plan
and assignments to the server. It is at this point that
the RBS can be used to control which users see what in
regards to the RBS.

Kevin

 

[Daniel Mosmeyer]

How do you set an RBS value for a resource/user?

Daniel

 

[Jim Sinclair]

Thanks for the reply.

Sorry if I'm being think, but do you therefore mean "task"
assignments? If so, and MS are being sloppy with the use of
the word "project" in the permission? - perhaps they should
say "Allow users in this category to view all projects with
tasks assigned to resources that they manage"

Does this mean therefore, by implication, that being
included in the project team via "Build Team" is not enough
to provide access via the relevant category where the box
is checked?

Perhaps I should explain why I'm asking this. It's because
I was thinking that using Build Team and adding resources
to projects without assigning them to tasks means that user
admin can therefore be delegated without giving the "Manage
users and groups" permission to loads of people. I guess a
dummy task against which the resources are assigned is a
workaround but it's not as elegant as just including
resources in the teams.

Thanks
Jim

 

[Brian K - Project MVP]

Thanks for the reply.

Sorry if I'm being think, but do you therefore mean "task"
assignments? If so, and MS are being sloppy with the use of
the word "project" in the permission? - perhaps they should
say "Allow users in this category to view all projects with
tasks assigned to resources that they manage"

Does this mean therefore, by implication, that being
included in the project team via "Build Team" is not enough
to provide access via the relevant category where the box
is checked?

Perhaps I should explain why I'm asking this. It's because
I was thinking that using Build Team and adding resources
to projects without assigning them to tasks means that user
admin can therefore be delegated without giving the "Manage
users and groups" permission to loads of people. I guess a
dummy task against which the resources are assigned is a
workaround but it's not as elegant as just including
resources in the teams.

Thanks
Jim

No, "Assigned to project" means being included in the Resource Sheet
for that project. They would not have to have a task assignment yet to
have this rule apply to them.