- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2025 09:10 PM
Hi everyone, I'm currently learning ServiceNow and had a quick question.
In real-time projects, is it considered a valid use case to create a duplicate user record in a separate custom table once the user account is deactivated?
The goal is to maintain those deactivated user records separately for audit or reporting purposes.
Is this something commonly implemented in actual projects?
Thanks in advance for your insights
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2025 09:26 PM
Hi @rishabhnilk ,
No CUstom table will be created or involved. Only in same User table [sys_user], we will mark Active= false [Active checkbox unchecked from the user form]. so data will be in same table only with Active= True (Active users) and Active = false (Inactive users). It works like this only in rela time projects.
If you have any furtehr question, you can ask me and if my answer helped you in anyways, mark it- Solution accepted.
Regards,
Nikhil Bajaj
Regards,
Nikhil Bajaj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2025 09:51 PM
Hi @rishabhnilk ,
in addition to what others have mentioned
you can enable auditing on sys_user table to see when and who has updated what on the user record
in this scenario of yours
if auditing is enabled you can check when the user is made inactive and who has made it
to enable auditing to you can go Dictionaries and filter with table name and type = collection and update the audit checkbox to true
only the changes made after this step will be audited
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
07-20-2025 01:08 AM
Hello @rishabhnilk
In most real-time ServiceNow projects, we don’t create a separate table for inactive users. We simply set the Active field to false in the existing sys_user table. This way, you still have the user data, and it’s easy to report or audit.
If you need to track changes, you can enable auditing on the sys_user table to see who deactivated a user and when.
If my response has helped you hit helpful button and if your concern is solved do mark my response as correct.
Thanks & Regards
Viraj Hudlikar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2025 01:33 AM
Hi @rishabhnilk ,
In most of the organizations once the user left or user is not with the organization then user account will be deactivated, that's why ServiceNow gave the active field in 'sys_user' table. Some times user might become part of organization with any other type like vendor/contractor then in employment type also make very important role. That time they just need to update with latest information and user will be active in organization. so no need to create the new record for that user. This way the firms manage their employees data it is easy for audit and other purpose as well.
In some time, organizations customize their user table for their purpose like if in future that employee is eligible to work with us or not, in which department employee worked and other information.
If you have any questions related to ServiceNow/doubts, feel free to ask me.
Great learning ahead.
Thanks,
Bhimashankar H
----------------------------------------------------------------------------------------
If my answer helps you or resolves your query, please consider marking as 'Accept As Solution'. So future readers with similar questions can find it easily. Your coordination will help community to grow stronger!.
----------------------------------------------------------------------------------------

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2025 09:18 PM
Hi @rishabhnilk
No, that's not necessary. All you need to do is set the Active field in the sys_user table to false when a user is deactivated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2025 09:26 PM
Hi @rishabhnilk ,
No CUstom table will be created or involved. Only in same User table [sys_user], we will mark Active= false [Active checkbox unchecked from the user form]. so data will be in same table only with Active= True (Active users) and Active = false (Inactive users). It works like this only in rela time projects.
If you have any furtehr question, you can ask me and if my answer helped you in anyways, mark it- Solution accepted.
Regards,
Nikhil Bajaj
Regards,
Nikhil Bajaj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2025 09:51 PM
Hi @rishabhnilk ,
in addition to what others have mentioned
you can enable auditing on sys_user table to see when and who has updated what on the user record
in this scenario of yours
if auditing is enabled you can check when the user is made inactive and who has made it
to enable auditing to you can go Dictionaries and filter with table name and type = collection and update the audit checkbox to true
only the changes made after this step will be audited
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
07-20-2025 01:08 AM
Hello @rishabhnilk
In most real-time ServiceNow projects, we don’t create a separate table for inactive users. We simply set the Active field to false in the existing sys_user table. This way, you still have the user data, and it’s easy to report or audit.
If you need to track changes, you can enable auditing on the sys_user table to see who deactivated a user and when.
If my response has helped you hit helpful button and if your concern is solved do mark my response as correct.
Thanks & Regards
Viraj Hudlikar.