access issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hi Team ,
Can someone let me know waht access user required to see the data ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
53m ago
Hi @pramn,
You can open ACLs and check for query based ACLs on this particular table. Also do check if any query BR is on the table too, just in case. If you cant find any ACLs or Query BRs, check for Security Data Filters on the table.
Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards,
Ehab Pilloor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
40m ago
see this
also check this
Part of the query on sys_user has been ignored because of insufficient access for 'query_range'
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
37m ago
Hi @pramn
To resolve this, you need to create explicit query_range / query_match ACLs to grant your non-admin users access to these operations.
1: Create a query_range/query_match ACL for the Field
- Navigate to System Security > Access Control and click New.
- Set the following values:
- Type: record
- Operation: query_range
- Name: u_cmdb_qb_result
- Field: Select field ( if it is showing in your error screen shot)
- Under the Requires role related list, add the specific role given to your mobile users.
- Save the ACL.
- Grant the same role
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
34m ago
@pramn You need to create a query_match ACL on your table to suppress this error.