---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Script Debugger impersonation support

# Script Debugger impersonation
support {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

You can use the Script Debugger
while impersonating another user, but only if the impersonated user has the script_debugger role
and has read access to the target script.  
While impersonating another user, you can:

* See and change breakpoints that belong to the impersonated user.
* View and pause on scripts that the impersonated user has read access to.
* Evaluate expressions in Console on behalf of the impersonated user.
{#impersonation-support__ul_hxs_dt1_1x}

The Script Debugger step-through controls
also use the read access of the impersonated user. For example, if the impersonated user does
not have read access to a function in the call stack, any Step into
action instead becomes a Step over action.  
The impersonated debugging session lasts until:

* You stop impersonating the user.
* You log out or the user session ends.
* You pause the Script Debugger.
* You close the Script Debugger.
{#impersonation-support__ul_f1j_hk1_1x}
**Related topics**   

* [Script Debugger multiple developer
  support](https://www.servicenow.com/docs/access?context=multiple-developer-support&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US)