Resolve dashboard report record count restrictions caused by custom business rulesIssue When a custom business rule restricts your data access, dashboard report widgets display incorrect record counts. For example, an admin might see "Incident State Closed (877)" while you see only "Incident State Closed (2)" for the same widget. Release All supported releases Cause A custom business rule is restricting your data access. To identify which rule is causing the issue, follow these steps: Diagnostic steps: Impersonate the affected user by navigating to the user record and selecting Impersonate user from the context menu.Open the system logs. In your browser's developer tools or by tailing the instance logs, look for a message containing query restricted to user followed by a user ID (sys_id). This message indicates which business rule is restricting the data. Example log entry: 2022-05-10 22:36:06 (864) Default-thread-14 A2A56603DB170910B55EDEFAD39619BA txid=969f2e07db57 *** Script: query restricted to user: 08f561074f58df040fba1ed11310c73e Open the Business Rule [sys_script] table by navigating to System Definition > Business Rules or by visiting the direct table URL: (your instance URL)/sys_script.list.Use the filter or search to find the business rule script that contains the text query restricted to user. This is the rule causing the data restriction. Resolution After identifying the business rule causing the restriction: Open the business rule record you identified in the Cause section.Uncheck the Active checkbox to disable the rule.Select Update to save your changes.Impersonate the affected user again and verify that the dashboard widgets now display the correct record counts.