Project and Portfolio Management Practitioners Forum
cancel

Restricting views of project/request based on field value

Highlighted
Andy McMahon_1
Super Contributor.

Restricting views of project/request based on field value

Hey guys,

 

I am in the final stages of developing a solution.  Today I was told that they wanted to restrict views of a project/proposal based on two things.

 

Division Field and If a user is listed anywhere in the project fields. 

I am sure there's a way to do this, what's the recommended way to do it from here?

8 REPLIES
Utkarsh_Mishra
Acclaimed Contributor.

Re: Restricting views of project/request based on field value

Do you want to restrict view on Project/Proposal request fields...

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
Andy McMahon_1
Super Contributor.

Re: Restricting views of project/request based on field value

Not entirely sure what you mean.  

 

I want certain projects/proposals to not be visible to people who are not in the same division as specified in the project..... 

The more I hash this out, the more I Think I painted myself into a corner.- 

Utkarsh_Mishra
Acclaimed Contributor.

Re: Restricting views of project/request based on field value

Ok... Got it..

 

You can do this by

 

  1. Open the "Proposal/Project" Request type
  2. Go to "User Access" section
  3. Remove/Un-check VIEW and EDIT (and others) for "All Users"
  4. Then ADD security by Add "User define token" and select "Security Type" as username/user-id
    ---- These user define token would be your fields in Proposal/Project
  5. Give the appropirate privelages i.e. view or edit....

 

Add such security for all the required fields. 

 

In this way only those User can view the request whose values are in the Proposal/Project.

 

 

I hope I am able to explain you....

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
Andy McMahon_1
Super Contributor.

Re: Restricting views of project/request based on field value

So, that's part one. 


Now is there a way to break out security based on their "Division"?  So, bob belongs to division A, he shouldn't be able to see any projects that are associated with Division B.  There's no way to do that is there? 

Utkarsh_Mishra
Acclaimed Contributor.

Re: Restricting views of project/request based on field value

I dont think this would be possible.... the only possibility would be to create a clone request for Division A and B...

 

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
Erik Cole
Acclaimed Contributor.

Re: Restricting views of project/request based on field value

Make a security group for each division, corresponding to the division names, and make the requests only visible to each respective group via the method from the other thread...use the token of the Division field, or create another hidden field/rule trigger to contain the security group you wish to have access...

Utkarsh_Mishra
Acclaimed Contributor.

Re: Restricting views of project/request based on field value

Hey Erik, thanks for the information... I was not aware of it... :smileyhappy:

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
Andy McMahon_1
Super Contributor.

Re: Restricting views of project/request based on field value

Ah. I think this one actually makes sense.... I'm going to hold off on questions so I can pretend I follow for a few minutes. :) :smileyvery-happy: