Forum Discussion

jamesramsden's avatar
2 months ago
Solved

Removing old user accounts

Removal of old user accounts in SL

I would like to know regarding the removal of unused user accounts within SL. To ensure that the deactivation or deletion of these accounts does not inadvertently affect system functionality, I am seeking confirmation on whether a query or report can be run that provides visibility into account activity and dependencies.

Specifically:

Identify historical usage of a user account within SL (e.g. dashboards, reports, scheduled tasks, integrations, or automated processes).
Generate a report or dataset that highlights what functionality or items are tied to a given account.
Use this information to safely assess whether an account can be removed without impacting operational workflows.

I want to establish a controlled process for the removal of old user accounts while safeguarding against disruption to active services, monitoring, or reporting functions.

Thanks

  • As a variety of objects within SL1 may be directly associated with a user account that have impact to other users it is generally not recommended to delete accounts. To ensure data integrity, audibility, and the ability to restore access if needed, it is advised to suspend user accounts rather than deleting them. Suspension maintains historical references and prevents accidental loss of critical information while still restricting the user's account and prevents that user from logging in to SL1.

2 Replies

  • While suspending a user is a viable option to avoid problems, it's not really answering/solving the Idea submitted by jamesramsden​ 

    How can we [easily] identify facets of the platform that would be affected if a user was deleted?

    It is not unlikely for a user account to be deleted and overlook the impact it may have on platform functionality.  It would be very useful to be able to run a report that highlights items associated with a particular user so that we can pre-emptively change ownership. 

  • As a variety of objects within SL1 may be directly associated with a user account that have impact to other users it is generally not recommended to delete accounts. To ensure data integrity, audibility, and the ability to restore access if needed, it is advised to suspend user accounts rather than deleting them. Suspension maintains historical references and prevents accidental loss of critical information while still restricting the user's account and prevents that user from logging in to SL1.