Clarity

We need to prevent resource manager from other department to see allocation of resources from not his department.

They have Global right Resource view all

There is used Resource Requisitions to allocate resources.

so they need Global right.

Project - Attach Requisitions Entry Resources - All

Project - View Requisitions - All

Via OBS they have

Resource - View book

Resource - Hard Book

But when Resource manager looking into for example Resource Workload portlet he can see Allocation for all resources not only on those where he has right View book.

Any Idea?

Vit

Don't give out "Global right Resource view all" - give the "resource view" right out at OBS level (same level as the book rights)

if they dont needed they will not have this global right. but for other purposes they need this view all. But question is about allocation not view resource as resource

Hi Vit_Posel - We're you ever able to figure this one out? Thanks! Chris

not yet ... seems that user requirements are going in oposition. They want to see all resources but want to limit view on allocation.

I just realized that this is the same problem that I have: https://communities.ca.com/thread/241795297-resource-view-permission

Viewing resources is ok (not confidential) and needed, but viewing all of their allocations is a confidentiality issue.
A solution would be to separate that and introduce a "Resource - View Allocations" permission.

BR David

Agree

Vit

If using Risk/Issue management, check to see if CA has yet fixed the bug in the "Assigned To" field.  Without the Global-Resource-View All right, the list is blank, even with view rights granted via OBS.

We ended up customizing the lookup, removing the security rights - user can now assign a risk or issue to any active user, without gaining access to view everything about those users.

Yes - customized, not configured.  We must remove this before each upgrade/patch install and put it back in afterwards. 

Here's the problem:  https://communities.ca.com/thread/241697491

Here's the idea:  https://communities.ca.com/ideas/235716584

Problem was originally raised on 12.1 - we finally gave up waiting on CA to fix this and customized the lookup. 

Still on 14.2.  Planning to go to 15.1 2017Q1 - will see if the problem has been resolved, there, or not.