Website Maintenance Best Practice Reminder: Block Old Accounts

Rose, on the SCLS blog, reminds us:

​You wouldn't let a staff member keep a key to the library after they become a former staff member, would you? Of course not! Don't forget to take the same care with the library's website. When a staff member leaves the library (for any reason, good or bad), it's good practice to limit their access to edit library websites, such as:
​

• Main public-facing website
• Staff blog or wiki
• Social media/other groups where the library has a presence (Facebook, Twitter, Google, Slack, etc.)

For example, if your library website runs on Drupal, there are options* to deal with a departing staff member's website editing account:
​

• Change the password on the account so the departing staff member can't log in anymore.
• Reassign the account to someone else with a new username & email.
• Block the account so that it cannot be used to log in at all.
• Delete the account so it is gone forever. On a Drupal site, this option will also prompt the question: should the content created with this account be deleted or reassigned to another staff member?​

​The specific options and steps for each platform may differ. The important thing is to remember to make sure the account housekeeping happens!