Which system property is added and set to true in order to see impersonation events...

InServiceNow, impersonation allows administrators toact as another userto troubleshoot, test permissions, or verify user experiences.

Tolog impersonation eventsin theSystem Log, the system property:

CopyEdit

glide.sys.log_impersonation

must beaddedand set totrue(true).

Key Features ofglide.sys.log_impersonation:Logswho impersonated whomin theSystem Log.

Capturestimestamp, user details, and session activity.

Helps withauditing and security compliance.

Navigate toSystem Definition > System Properties.

Search forglide.sys.log_impersonation.

If it doesn’t exist, create it:

Name:glide.sys.log_impersonation

Type:True/False

Value:true

Save the property and test impersonation.

How to Enable Impersonation Logging:

A. glide.user_setting →Incorrect

Not related to impersonation logging.

Deals withuser preferences and settings.

B. glide.sys.all_impersonation →Incorrect

No such property exists in ServiceNow.

D. glide.impersonation_setting →Incorrect

Incorrect property name; does not exist.

E. glide.sys.admin_login →Incorrect

Logsadmin logins, not impersonation events.

Why Other Options Are Incorrect?

Impersonating Users in ServiceNow

System Logs & Impersonation Tracking

Official ServiceNow Documentation Reference: