Hide “Records were restricted” message in Indicator Management workspace

[SaiRahulGupS]

Hello All,

I’m working with the Platform Analytics Indicator Management workspace, which displays records from the database view pa_indicator_management_db_view.

My requirement is to hide certain indicators for end users based on conditions, while allowing admins to see all indicators. I achieved this using a query business rule, and the filtering works as expected.

However, in the Indicator Management workspace, non‑admin users see an info message stating that “records were restricted.” This message does not appear in the Core UI list view of the same database view.

My question: Is there a way to suppress or hide this “records were restricted” message in the workspace so that end users simply see the filtered list without the banner?

Any guidance on whether this can be handled via any other ways

[pr8172510]

Hi @SaiRahulGupS,

The "Records were restricted" banner is automatically displayed when records are filtered by ACLs, Query Business Rules, Data Filtration, or Security Constraints.

In Platform Analytics workspaces, this message is generated by the Workspace framework to indicate that the user is not seeing all available records.

There is no documented OOTB property or configuration to suppress this banner while still applying record restrictions.

If the filtering is business-driven rather than security-driven, consider:

• Applying the filter directly in the data source/query used by the workspace.
• Using a filtered database view or dedicated workspace view for end users.

However, if a Query Business Rule or security mechanism is restricting records, the banner is expected behavior and is intended to provide transparency to the user.

[Tanushree Maiti]

Hi @SaiRahulGupS 

Option1 : Standard Read ACLs block records after a list loads, which triggers this UI warning. 

Instead of that ,  create a Before Query Business Rule on the table and add logic to filter records based on the current user's access, such as matching the assigned user or assignment group.

By restricting the GlideRecord query to return only records that the current user is authorized to access, unauthorized records are never retrieved in the first place. As a result, the security constraint message is avoided, and the user sees only the records they are permitted to view.

The options given in these post , you can try in your Workspace:

https://sn-nerd.com/2024/05/22/6-ways-to-eliminate-rows-removed-by-security-constraints-message-in-s...

https://www.servicenow.com/community/itsm-forum/workspace-records-view-restriction-based-on-group-me...