Will Inactivating & Locking out a user cause issues with ServiceNow App objects created by them?

[Renee-17]

If I lock out and inactivate an admin user who was the original creator of a ServiceNow Application, will that cause any issues with objects that were created by that user, (like tables, scheduled exports, imports, service portal, widgets, and other process?

[MercBuilding]

Hi @Renee-17 ,

    It doesnot get effected if the user is made inactive. Configuration inside ServiceNow doesn't depend on User, they will be still in place and work as is.

Thanks!

[ArsalanChaudhry]

Hi @Renee-17,

Locking out and inactivating an admin user with full permissions in ServiceNow should generally not cause issues with objects created by that user, as other admins typically possess the necessary permissions.

However, it's crucial to review and update any scheduled jobs, integrations, and dependencies to ensure continuous functionality.

Please mark this as correct answer and helpful if it is resolved, or mark this helpful if this helps you to reach towards solution.

Thanks,

Arsalan

[Renee-17]

I know what to look for regarding schedule jobs.  But what tables do I need to look up for  integrations, and dependencies.

[Danish Bhairag2 · Accepted solution]

Hi @Renee-17 ,

As mentioned by others it will still behave the same way it was behaving as other creds will have similar permission. 

But in case of scheduled job,scheduled reports or integrations where credentials are used to execute those problem will occur there.

U can check Run As column for scheduled jobs/reports for integrations u can check credentials table from filter navigator or the script section under business rule, script include or scheduled job. There is a possibility the creds could be hard-coded manually if created by a User/Developer like us.

Thanks,

Danish