Skip to main content
Answer

Acumatica Row Level Security - GL Account Access Issue

  • June 18, 2024
  • 3 replies
  • 182 views

Acumatica Row Level Security on the GL Account seems to work fine when you are trying to remove the account from selection when creating a new Journal Entry.  However, any released Journal Entry, as well as a number of the GL Register and Edit Reports include these transaction lines for all users, as long as they have the right to open the Journal Entry or Register report.  If the purpose of the Restriction Group is implied to:

“your organization may have sensitive or confidential accounts and subaccounts which must be invisible for majority of users. You can control the visibility of these accounts and subaccounts for users (that is, -which users can view the accounts and subaccounts) by using restriction groups.”

Wouldn’t you want the transaction rows to be suppressed in the report/entry screen as well.

 

Does this match with what others have found when using the Account restrictions?

 

Thank you.

 

Bryan 

 

Best answer by Kandy Beatty

HI @bryanhinkle35 

From my experience, the user will still be able to see the reports, just not use that account. 

Here is the help article you can review:

https://help.acumatica.com/(W(2))/Help?ScreenId=ShowWiki&pageid=7f4d2128-5ca0-4f40-84e1-11b0d51603de

3 replies

nhatnghetinh
Captain II
Forum|alt.badge.img+11

Hi @bryanhinkle35 

Currently, Restriction Groups in Acumatica will block restricted features on all screens and reports for restricted Users.

We have a problem with the Restriction Groups: we only want to restrict Users to the screen and reports are not restricted, but the reports are blocked.

 

Best Regards,

NNT


Kandy Beatty
Captain II
Forum|alt.badge.img+17
  • Captain II
  • Answer
  • June 20, 2024

HI @bryanhinkle35 

From my experience, the user will still be able to see the reports, just not use that account. 

Here is the help article you can review:

https://help.acumatica.com/(W(2))/Help?ScreenId=ShowWiki&pageid=7f4d2128-5ca0-4f40-84e1-11b0d51603de


Forum|alt.badge.img
  • Freshman I
  • June 18, 2025

From the referenced article above 

Shows that row level security is not respected in ARM reports or Non GI inquiry screens. Major security problemo