---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Data filtration debugging

# Data filtration debugging {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Use the session log to see how data filtration affects your records and debug user
access issues.

## Vorbereitungen

Role required: admin

Output information appears in the session logs when users access records. You can use
this logging information along with impersonation to learn why users see or do not
see records. You can then use that information to adjust your data filtration rules
and ensure that users only see what you intend.

## Prozedur

1. Navigate to AllSystem SecurityDebuggingDebug All Security.  
   The Script Debugger opens in a new browser tab or window.
2. In the Script Debugger window, select the Session Log tab.
3. In another browser tab or window, impersonate a user to troubleshoot that user's access.  
   Hinweis:  
   Impersonation allows an admin to see an instance with another users settings and access. For details on impersonation, see [Impersonate a
   user](https://www.servicenow.com/docs/access?context=c_ImpersonateAUser&version=australia&pubname=australia-platform-administration&ft:locale=en-US).
4. While impersonating a user, access a list or record where you see unexpected behavior.  
   This behavior may be a record the user sees, but should not see, or a list of records that are not appearing as expected for a user.  
   After accessing records with the impersonated user, you should begin to see output in the session debugger.
5. Look for data filtration information in the session debugger.  

   This example shows two log messages where a data filter denied access to records. The log entries appear as red text, and include why the data filter denied access, as well as the sys_id of the data filter. You can
   click on this sys_id to open the data filtration record.

   This example shows a log message where a data filter allowed access to a record. These log entries appear as green text. As with the first message, you can click this sys_id to open the data filtration record.
6. Use this information to make any adjustments to your data filtration rules.  
   Repeat these steps to refine your rules and give users the access they need.