Entity Based Access - only Issue table Available

Mira1992
Kilo Sage

I'm configuring Entity-Based Access for a customer who would like to start using this feature. However, when setting it up, I’m only able to select the Issue [sn_grc_issue] table (see attached screenshot).

Would anyone know why this is happening or what I might be missing?

There isn’t much to configure—I've already confirmed the required property is set to true. I’ve tried setting the configuration to Entity, Entity Class, Entity Type, assigning it to the user, user fields, and group fields, read the SN documentation but the result is always the same.

If I can only select the Issue table, this won’t work for our use case.

Any advice or guidance would be greatly appreciated.

Thank you!
Miroslav


SN documentation:
https://www.servicenow.com/docs/bundle/yokohama-governance-risk-compliance/page/product/grc-common/t...

Mira1992_0-1746803274545.png

 

 

2 ACCEPTED SOLUTIONS

You must be on 20.1.x version of all GRC apps to see latest changes. On the UI you can only select master tables.

 

If you select  control on UI - indictaor, attestations, ind tasks linked to it will be auto updated.

 

Control objective and policy exception are not EBA enabled OOTB

View solution in original post

Hello @GouthamAnumol ,

Updating the plugins did the trick—I just had to confirm it with the customer first.
Thank you so much for your help!

@all


If you want to configure Entity-Based Access for a different table (e.g., a custom table), you may find the following resources helpful:

📘 Configuring Entity-Based Access for Custom TablesKB1646304
🔧 Managing Custom User and Group Fields on Entity TablesKB1646185 

For testing purposes, there are also two useful Scheduled Jobs:

  • Sync applicable entities for entity type and class access config

  • Sync applicable entities and process bulk access update configs

As GouthamAnumol mentioned earlier, the applicable record types are defined in the table:
[sn_grc_ent_access_applicable_record_type]

And the main configuration logic is handled by the Script Include:
EntityBasedAccessUtils

Hope this helps!

Best regards,





View solution in original post

9 REPLIES 9

Can you try repairing GRC: policy and compliance plugin ?

Hello @GouthamAnumolu ,

we updated the GRC: Policy and Compliance Management plugin to the version: 20.1.3 and Controls are now available/selectable in the Bulk access update configuration.

Mira1992_0-1747043468287.png


Is that expected behavior?
We expected that Entity based access can be used across the whole scope = for Policy exceptions, Indicators, Indicator Tasks, Control Objectives, etc ... 



You must be on 20.1.x version of all GRC apps to see latest changes. On the UI you can only select master tables.

 

If you select  control on UI - indictaor, attestations, ind tasks linked to it will be auto updated.

 

Control objective and policy exception are not EBA enabled OOTB

You can find EBA enabled tables list in the table which i shared earlier.

Hello @GouthamAnumol ,

Updating the plugins did the trick—I just had to confirm it with the customer first.
Thank you so much for your help!

@all


If you want to configure Entity-Based Access for a different table (e.g., a custom table), you may find the following resources helpful:

📘 Configuring Entity-Based Access for Custom TablesKB1646304
🔧 Managing Custom User and Group Fields on Entity TablesKB1646185 

For testing purposes, there are also two useful Scheduled Jobs:

  • Sync applicable entities for entity type and class access config

  • Sync applicable entities and process bulk access update configs

As GouthamAnumol mentioned earlier, the applicable record types are defined in the table:
[sn_grc_ent_access_applicable_record_type]

And the main configuration logic is handled by the Script Include:
EntityBasedAccessUtils

Hope this helps!

Best regards,