Missing ACLs on initial Compliance Management Workspace setup

[MichaelR8625215]

Hi,

I am setting up the Compliance Management workspace for the first time on Yokohama and am having errors while navigating the workspace.

The type of error I am receiving is 'Part of the query on sn_grc_profile has been ignored because of insufficient access for 'query_range' operation on sn_grc_profile.compliance_score’'. I am seeing this across 7 tables so far.

I am trying to understand if there is a step I've missed during setup or is setting up the ACLs something which is needed as part of configuring the Compliance Management Workspace.

I have:

• Installed version 20.1.2 of GRC: Compliance Management Workspace 
• Installed version 20.2.0 of GRC: Policy and Compliance Management 
• Granted the user receiving the errors roles sn_compliance_ws.corporate_compliance_manager  & sn_compliance_ws.it_compliance_manager

My understanding is the errors mean the user does not have privileges to complete a query_range operation on the target tables fields. A ServiceNow update was introduced in May 2025 to tighten this access. I'm not clear on where to go next.

Michael

[Matthias Ferstl]

Hi  @MichaelR8625215 

you need to add / configure your own query ACLs.

Goto: Query ACLs
Also check out this article to understand that stuff: Understanding ServiceNow’s May 2025 Query Range ACL Update: What You Need to Know 
(kudos to how ever wrote this!)

I recommend to set up reliable ACLs (based on neet-to-know-principle) as they are an important part of platform security.
Find out which table are impacted, create according rules and you should be fine.
In workspaces this is an issue, since many of the OOB widgets have queries, so this might take a while, but if you know the user roles / groups that should have access, this is the safest approach.

Kind regards