Zevonix Cloud
Menu
Home › Blog

Website Access Removal Checklist for Departing Staff

5 min read

A notebook, keyring, and folder arranged on a tidy desk.

A website access removal checklist helps you close the right doors when an employee or agency leaves, without accidentally losing content or control of the site. The website itself is only one access point. Hosting, the domain, email, analytics, and connected services may each have separate users, passwords, or ownership settings.

Start by confirming that someone who represents your business can still administer the site and its related accounts. Then transfer anything the business needs, remove the departing person’s individual access, and change shared credentials they may know. Finish by checking that the changes took effect.

Before you remove access

Make sure a company-controlled account works before changing someone else’s permissions. Sign in and confirm that it can manage the website, hosting, domain, and other essential tools. Avoid relying on an account tied to the departing person’s work email or an agency’s email address.

Make a list of accounts and services the person used, including any that may have been created under their own or the agency’s account. Ask the departing person or agency to identify integrations, keys, recovery methods, and ownership details that are not obvious from your records.

Preserve business content and records before deleting an account. If you are concerned about suspicious activity, document what you find and consider getting help before making changes that could remove useful evidence.

An abstract arrangement of secure compartments linked by fine pathways.

Website access removal checklist

Website content management system

For broader WordPress account and site safeguards, see our WordPress security hardening checklist.

Hosting, server, and file access

Domain registrar and DNS

Email, cloud storage, and recovery accounts

Analytics, search tools, and connected services

Change shared credentials and verify the handoff

Removing an individual account does not change a shared password that person already knows. Rotate shared passwords, keys, and tokens where the departing person had access. Update any systems that rely on those credentials, and use individual accounts instead of shared logins when the service allows it.

Where available, review active sessions and sign out devices or sessions that should no longer be active. Turn on available sign-in protections for company-controlled accounts, and make sure recovery details belong to the business.

Do a final pass through user lists, ownership and permission screens, connected apps, and recovery settings. Write down what you removed or transferred and who now owns each account. Then check that the site and its important connected services still work.

If you need to coordinate an access handoff alongside a care plan, our website care information explains the website support Zevonix Cloud offers. Zevonix Cloud manages WordPress, Joomla!, Laravel, and static sites, with security monitoring, updates, and checked nightly off-site backups included.

Frequently asked questions

How do I remove a former employee from WordPress?

Use an administrator account controlled by the business to review the user list and remove or change the former employee’s access. Before deleting the account, decide whether their posts and pages should be assigned to another user or removed.

Should I delete the account or change its role?

Remove the account if the person no longer needs access. Lowering its role can make sense only when there is a specific, approved reason to keep that account active. Do not leave unnecessary access in place just to preserve content; choose the appropriate content-transfer option when deleting a user.

Do I need to change shared passwords after an agency leaves?

Yes, if the agency or its staff could know a shared password, key, or token, replace it and update services that use it. Also review individual accounts and connected applications, since changing a shared password does not remove those separate access paths.

What should I do if I find an unknown website administrator?

Record what you found and review the site’s other users, connected accounts, and recent changes. If you cannot confirm the account is authorized, secure company-controlled access and get qualified help investigating before removing evidence or making broad changes.

Keep ownership with the business

A careful offboarding is more than deleting one login. Confirm business ownership, transfer important content, remove individual access across every relevant service, rotate shared credentials, and verify the result. If you want help reviewing website access and care, contact the Zevonix Cloud office in Jacksonville or Palm Coast.