- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2019 12:54 PM
Will ServiceNow track who updates records while impersonating another user? The Impersonate User feature is extremely useful but any updates saved while impersonating a user save as the impersonated user, not the administrator. Without removing the feature from an administrator account, can the administrator be logged as the user posting the update?
Solved! Go to Solution.
- Labels:
-
Multiple Versions
-
User Interface (UI)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2019 01:32 PM
Hello,
While impersonating a user any updates are done as the user being impersonated. There is a log of who impersonates whom and during which time period but record updates will not show that the update did not come from the user listed. There is no way to change that feature unfortunately.
--David

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2019 01:32 PM
Hello,
While impersonating a user any updates are done as the user being impersonated. There is a log of who impersonates whom and during which time period but record updates will not show that the update did not come from the user listed. There is no way to change that feature unfortunately.
--David
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2019 01:33 PM
I don't think it's possible, because when you impersonate a person, you are that person.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2019 05:37 PM
As of Geneva, impersonations are logged in the System Log. Logging can be enabled or disabled with the glide.sys.log_impersonation property, in the sys_properties file but it must be manually added.
I also found this helpful post to create custom script that logs the action:
https://community.servicenow.com/community?id=community_question&sys_id=325c03a5db9cdbc01dcaf3231f9619e4
I suspect that the custom table counts against the new subscription model.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2019 07:51 AM
I found the following link on the community while looking for information on the same issue. I haven't tested it yet, but it might help...