How to restrict make filter condition as static from reports

[SivaprasadV]

In servicenow I have a custom table. I have created reports on by connecting the custom table which will show all the records which are assigned to him. Once user click on the count, he should be able to see all the records which are assigned to him. But user has access to change the filter contions. how to restrict to change the filter conditions...?

[SivaprasadV]

I know that we can do that by making list control --> Omit List as true. which will remove the filter action completely. I want to give access to admin user to update the filter conditons.

[Vaishnavi Lathk]

Hello @SivaprasadV ,

In ServiceNow, this is actually expected behavior. When a user clicks on the report count, it opens the list view, and the platform allows users to modify filter conditions there by default. There’s no OOB way to completely lock or make those filters static.

What you can do instead is control the data at the backend:

• You can write a Before Query Business Rule on your custom table to always enforce something like assigned_to = current user. So even if the user changes the filter, they will still only see their own records.

• You can also use ACLs to restrict access. For example, grant read access only when the assigned_to field matches the logged-in user. This ensures users can’t access other records, regardless of how they tweak the filter.

So while the filter UI can’t be locked, you can still make sure users only see what they’re supposed to see.
Thanks

[SivaprasadV · Accepted solution]

Hi @Vaishnavi Lathk  and @J Siva ,

Thank you for your suggestions, Just know I checked that in we can make filter condtions editable for admin role users by below navigation.

From the list view click on three dots beside the field name--> Configure-->List Control-->Under the Display Configuration Section-->Add Filter Roles (Add the role which role user needs access to add Filter condition)

[J Siva]

Hi @SivaprasadV 

I don’t think we can restrict users from modifying the filter conditions because the filters are applied at the database level, not just on the report (If we click the count, the list of records will be shown from the actual table).

As a workaround:
You can use a Single Score and a Column‑type data visualization. Disable “Allow Chart Interaction” in the Single Score report so that when a user clicks the count, no action is triggered.

Users can still view the list of records in the Column‑type data visualization, where they cannot edit the filter conditions.

Regards,
Siva