Hi @Ammy01 ,
Creating a query match and query range is just like any other ACL
testing query match is
let's say I have a query match on the description field
use the operators highlighted on the field and run
for query range use other operators
query_match ACLs – A query_match rule governs exact or direct searches. This covers “safe” operators like equals (=), not equals, is empty, etc. Essentially, these are queries where a user is looking for a specific value or record. ServiceNow documentation explains that query_match ACLs allow specific, targeted lookups – for example, “Incident number = ABC123” or “State is not Closed” would fall under match queries. These are considered lower risk because they return a focused result (you’re only pulling up what you explicitly asked for).
query_range ACLs – A query_range rule governs broad or pattern-based searches. This applies to operators like greater than/less than comparisons, “starts with”, “ends with”, “contains”, and other queries that return a range or set of results. Such queries are more powerful – e.g. filtering all incidents opened this month, or searching all users with last name starting “Smith”. Because they can reveal sets of data, they’re considered higher risk. In our HR example, searching for all salaries in a range or all SSNs that start with a certain digit would be a “range” query. The new query_range ACL type lets admins explicitly control who (if anyone) can perform those kinds of searches on a given table/field. If a user isn’t authorized via ACL to run a range query on a field, that query will now be blocked.
source
https://www.ikconsulting.com/post/understanding-servicenow-s-may-2025-query-range-acl-update-what-you-need-to-know
Please mark my answer as helpful/correct if it resolves your query.
Regards,
Chaitanya
