Skip to main content
Answer

Privacy for Project Managers

  • January 26, 2023
  • 3 replies
  • 187 views

lanefarrell
Freshman I

We are trying to find a way to restrict our project managers access so they can only view the jobs they are managing. Right now the only solution proposed is to create a security group, and then name it as that project manager, and whenever a job is set up go to the group and individually add access to that job being set up (in addition to having them listed as the project manager in the project manager field at the job level). 

 

We found this solution very frustrating given that we fill out the project manager field on each job already during job set up. Are we missing a better solution? 

Best answer by aaghaei

Setting default for inquiries is not foolproof as it can be easily bypassed. Setting up the PMAccess is the only reliable method that will mange the access to the source documents like as APBills , Subcontracts, …

I do agree it is frustrating to assign PMs to the Access Groups when you assigned the PM In project setup already. 

What you can do is to add a customization to Project set up to add/remove the project to the user groups automatically which is your PM  instead of manual maintenance. I personally would prefer to setup the projects automatically in PMAccess as groups and add the PM  or other employees as authorized member if I was going to do it through customization project.

 

 

3 replies

ChrisWeidner
Varsity I
Forum|alt.badge.img
  • Varsity I
  • January 26, 2023

@lanefarrell , We dealt with the same issue. As a workaround, we default our views (filters on, Generic Inquiries & Reports) to be PM Specific. The only piece of Row Level Security we use is to omit Employees from seeing others’ reimbursement AP bills (vendor = Employee). 

PM’s either have their own generic inquiry or default filter for inquires/reports. We also send our PM’s reports on a scheduled basis ( PM Specific ).

This is manageable for us, but is not as secure as being able to block access based on PM (on the project level). 


Forum|alt.badge.img
  • Jr Varsity II
  • January 28, 2023

We are also in need of project manager ristriction based on the assign project managers to the project. Row level access is time consuming and we also need project manager to be able to charge to other project they do not manage but work on. With role lever security if you ristric access to project they dont manage it also blocks them from seing the project in the timecard and expense claims to be able to charge for time worked.


aaghaei
Captain II
Forum|alt.badge.img+10
  • Captain II
  • Answer
  • January 29, 2023

Setting default for inquiries is not foolproof as it can be easily bypassed. Setting up the PMAccess is the only reliable method that will mange the access to the source documents like as APBills , Subcontracts, …

I do agree it is frustrating to assign PMs to the Access Groups when you assigned the PM In project setup already. 

What you can do is to add a customization to Project set up to add/remove the project to the user groups automatically which is your PM  instead of manual maintenance. I personally would prefer to setup the projects automatically in PMAccess as groups and add the PM  or other employees as authorized member if I was going to do it through customization project.