Will inactive users consume roles.

[viswa5]

Hi Team,

      Need clarification on inactive users.

-> Will inactive users consume roles.

-> what are the precautions need to take while deactivating the account / lockout the account.

-> in case the account is lockedout then users can able to view ESS view or not.

-> While deactivating the acccount do we need to remove the roles and groups(is that mandatory).

Please provide me the clarification on these same.

Advance thanks.

Regards,

Viswa.

[arpitt · Accepted solution]

-> Will inactive users consume roles. (Yes if roles are not removed)

-> what are the precautions need to take while deactivating the account / lockout the account.(Remove Roles and group associations )

-> in case the account is lockedout then users can able to view ESS view or not.(No, but they can access SN through side_door if they are inactive but not locked out)

-> While deactivating the acccount do we need to remove the roles and groups(is that mandatory). (Yes)

[srinivasthelu]

Hi Viswa,

Inactive users wont be able to log in,   I do not think you need remove roles for inactive users. Inactive users are for just audit purpose(of course you can activate them whenever you want)

Thanks

Srinivas

[arpitt]

You can still log in as an inactive user if the user is not locked out

Through: http://<your-instance>.service-now.com/side_door.do

[Michael Fry1]

Srinivas Thelu is correct that Inactive users won't be able to log in because there is an out of the box business rule (Lock Out Inactive Users) that will set Locked out to true if Active becomes false. Thus they won't count against licensing count nor can they view tickets.

As for removing roles and groups, that's good practice but not mandatory. You can also create a business rule that will do it for you automatically when active changes to false.

Precautions would be: do they have open tickets? do they have scheduled jobs that need to be updated. Is there sys_id used a script somewhere? There is a UI action available for "Find References' for the sys_id of the record in question. Works great for finding where their sys_id is used.