- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2025 03:00 AM
How can we check who has impersonated our instance over a period of time?
Is there any way or any method to do access Impersonate counting's?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2025 03:07 AM
Hi @SH40171025
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0717055
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2025 03:08 AM
To retrieve information about impersonation in your instance, follow these steps:
- Navigate to "sys_properties.list"
- Click New
- Fill in the new property with the following values:
- Name: glide.sys.log_impersonation
- Type: true/false
- Value: true
- Save
- Go back to "sys_properties.list" and show List view
- Type "glide.sys.log_impersonation" in the Name column and press Enter to confirm the property has been added.
- Perform a cache flush by typing "cache.do" in the navigator
- Log out then Log in again
After logging back in, you can see the history of impersonation in a system log by:
- Navigating to System log > All
- Type "*impersona" in the Message column and press Enter
- You will see the history of impersonations in the system log by looking for messages like:
- "Impersonation start:"
- "Impersonation end:"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2025 03:12 AM
Hi @SH40171025 ,
in addition to what @Dr Atul G- LNG has shared
you can check the user preferences tables for each users impersonations
where name = recent.impersonations
Please mark my answer as helpful/correct if it resolves your query.
Regards,
Chaitanya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2025 02:19 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2025 02:23 PM
Please accept answers and close the thread.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2025 03:48 AM - edited 06-25-2025 03:49 AM
Hello @SH40171025,
I just tried in my client's instance and no system property is needed to create. The glide.sys.log_impersonation as per suggested KB is not existing in my client's and still you can check the logs.
Simply change your URI accordingly and navigate to:
https://your-instance.service-now.com/syslog_list.do?sysparm_query=sys_created_onONThis%20month%40ja...
(the query has applied filter for the last month, you can adjust it)
And you can see who impersonated for whom and when it was.
Search in the Sys Log for:
Impersonation start
Impersonation end
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2025 02:23 PM
Please accept answers and close the thread.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2025 03:48 AM - edited 06-25-2025 03:49 AM
Hello @SH40171025,
I just tried in my client's instance and no system property is needed to create. The glide.sys.log_impersonation as per suggested KB is not existing in my client's and still you can check the logs.
Simply change your URI accordingly and navigate to:
https://your-instance.service-now.com/syslog_list.do?sysparm_query=sys_created_onONThis%20month%40ja...
(the query has applied filter for the last month, you can adjust it)
And you can see who impersonated for whom and when it was.
Search in the Sys Log for:
Impersonation start
Impersonation end
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2025 12:18 AM
Hi,
our issue with that is, on the syslog you shouldn't run reports, we need a way to export for audit reasons the impersonations. And the records in the isc_impersonation_event are kept for just 7 days, so currently our work around is that once week the data is exported to an excel spreadsheet.
Anyone have a better idea? I'm wondering that this isn't really kept in a seperate place and OOTB.
