How to limit table access for dedicated users

[ChrisGetint]

Hi!

I work as Support Engineer for a Integration as a Service product, basically we build integrations between ServiceNow and Jira.

When building the integrations, we create a ServiceNow dedicated user with some OOTB roles (such as sn_incident_viewer, sn_incident_write, ITIL, etc...).
However, these OOTB roles end up allowing the dedicated user to access other tables/applications.

How can we limit access for the user so he can only access specific applications or tables, despite the ACLs given to his role? We believe that it would be better to just assign the OOTB roles, and then trim the access instead of building the whole role from scratch and figuring out each ACL...

[YaswanthKurre · Accepted solution]

Hi @ChrisGetint ,

It is better to create a custom role and only provide the access what you need.

1. Keep the OOTB roles for functionality.
2. Create a custom role (e.g., x_integration_restrict) and apply deny ACLs to sensitive tables or records.
3. ACLs can be configured to deny access if the user has the custom role, effectively overriding broader OOTB permissions.

Refer this: Restricting REST API access to specific tables - Support and Troubleshooting

Mark this as helpful and correct if this helps you.

Thanks,

Yaswanth

[Ankur Bawiskar]

@ChrisGetint 

is 3rd party using Table API to access?

Would like to understand more on the business requirement.

you can always create a scripted REST API and use an API user and when 3rd party consumes the data, you can use GlideRecord to give JSON response as per what 3rd party wants.

If my response helped please mark it correct and close the thread so that it benefits future readers.