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.

Website access removal checklist
Website content management system
- Review the user list in WordPress, Joomla!, or your other content management system. Remove the departing person’s account or lower its permissions if there is a clear business reason to retain it.
- Check for unfamiliar administrator accounts and accounts using personal or agency email addresses. An unknown administrator is a reason to investigate, not to assume the full story.
- Before deleting a WordPress user, decide what should happen to their posts and pages. WordPress offers the option to assign that content to another user or delete it. Choose reassignment if the business needs to retain the content and its attribution.
- Where supported, revoke active sessions, application passwords, and other access tokens associated with the departing person. Removing a user login may not address every separate way a service can connect.
For broader WordPress account and site safeguards, see our WordPress security hardening checklist.
Hosting, server, and file access
- Remove personal accounts from the hosting control panel and any server-management tools.
- Review FTP or SFTP users, database accounts, deployment tools, and remote access. Remove accounts that are no longer needed.
- Check who can access backups and restore tools. These may contain site files or data and should remain under business control.
- If an agency owns the hosting account, arrange a transfer to a company-controlled account before ending access. Confirm you can sign in and manage the site after the handoff.
Domain registrar and DNS
- Review users and account owners at the domain registrar, where the domain is registered, and in the DNS service, where its routing records are managed.
- Confirm the business controls the account’s recovery email and authentication methods. Remove the former employee or agency from those settings if they have access.
- Look for changes or records the departing person managed, such as website routing or email configuration. Keep what the business still relies on and make changes carefully.
Email, cloud storage, and recovery accounts
- Remove or disable the person’s access to company email and shared cloud storage according to your organization’s process.
- Check shared folders for website files, credentials, design assets, and documentation. Transfer business materials to an account the company controls.
- Review recovery email addresses, phone numbers, and backup authentication methods on important accounts. Replace personal or agency-controlled recovery options.
Analytics, search tools, and connected services
- Review users and permissions in analytics, search performance tools, tag management, form services, and other tools connected to the site.
- For Google Search Console, check the owners and users list and remove access that should no longer be present. If the departing agency was a verified owner, also check whether its verification method or token remains in place. Google explains owner, user, and permission management in its Search Console permissions guidance.
- Review connected applications, API keys, webhooks, and integration accounts. Remove or replace credentials the former employee or agency could use, while confirming that active business services still work.
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.
