Skip to main content
Solved

Project users can view projects outside of their branch restriction?

  • 29 November 2022
  • 4 replies
  • 426 views

Forum|alt.badge.img

We have “restriction groups by branch” in place.  We have the “access role” configured on our branches.  And yet, all our users can see projects for all branches.  This is not the case in other modules.  I see another similar post here, and it doesn’t look like it was resolved there either.  Is this a known bug?  

Acumatica 2021 R2
Build 21.215.0016

Best answer by BenjaminCrisman

Hi @MarciaW! Restriction groups by branch only work for Subaccounts and GL Accounts, otherwise if only access roles are used then this will not be enough to stop all projects coming in.

Your options would be to either create actual restriction groups on Projects using the Project Restriction Group:

Another option would be to customize the GI so that the user branch populates as a parameter and then have a condition which specifies that the default branch on the project must match the branch parameter.

You can first add the GLHistoryEnqFilter (which populates the current logged in branch by default)

Then set the following parameter:

Then set the following condition:

Now the branch which populates by default will be the one the user is logged into and so only projects associated to this branch should show. It’s not a perfect workaround, but we have a process to limit projects specifically, so that would be the best option.

View original
Did this topic help you find an answer to your question?

4 replies

BenjaminCrisman
Acumatica Employee
Forum|alt.badge.img+4
  • Acumatica Support Team
  • 631 replies
  • Answer
  • December 2, 2022

Hi @MarciaW! Restriction groups by branch only work for Subaccounts and GL Accounts, otherwise if only access roles are used then this will not be enough to stop all projects coming in.

Your options would be to either create actual restriction groups on Projects using the Project Restriction Group:

Another option would be to customize the GI so that the user branch populates as a parameter and then have a condition which specifies that the default branch on the project must match the branch parameter.

You can first add the GLHistoryEnqFilter (which populates the current logged in branch by default)

Then set the following parameter:

Then set the following condition:

Now the branch which populates by default will be the one the user is logged into and so only projects associated to this branch should show. It’s not a perfect workaround, but we have a process to limit projects specifically, so that would be the best option.


Forum|alt.badge.img
  • Author
  • Varsity I
  • 67 replies
  • March 1, 2023

@BenjaminCrisman thank you for your reply!  I’m unsure about how restriction groups by branch relates to GL?  We are not restricting GL or Sub Accounts in this case, only the branches.  

 

I guess I’m just confused about why it doesn’t work for projects but does work in every other module?


Laura02
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3135 replies
  • March 1, 2023

Forum|alt.badge.img
  • Author
  • Varsity I
  • 67 replies
  • March 2, 2023

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings