All insights

Who still has access to your website?

Build a practical offboarding routine for website editors, agencies, volunteers, and the accounts behind your domain and hosting.

Three keys and a violet tag hang from a dark board.

The practical takeawayTrace access across the website and its connected services, transfer ownership, then confirm that former users can no longer act.

  1. List the accounts
  2. Transfer ownership
  3. Confirm the change

A former volunteer disappears from the website's user list. Their personal email still owns the domain renewal, a form sends notifications to their inbox, and the agency they worked with still manages a shared folder of documents. Removing one login was the right thing to do. It addressed only one part of the handoff. For a small team, the missing pieces often live in the services nobody thinks about until they stop working.

Start with one real departure

Choose a recent staff change and retrace the work that person performed. Could they publish landing pages, download registrations, approve a bill, modify a form, or invite another editor? Looking at tasks helps you discover services that a list of usernames misses. The person responsible for the newsletter may also be the recovery contact for the service that sends confirmation emails.

Walk through the website, hosting account, domain registrar, analytics property, form service, email platform, and shared asset library. Include a partner agency when it manages any of these for you. Record the service, the business owner, the role the person held, and how to change it. Keep passwords, recovery codes, and payment details in your approved secure system rather than in this inventory.

Transfer business ownership before removing access

A named editor can usually be removed without affecting other people. An individual who is the only account owner needs a different handoff. Put an appropriate organization-controlled account or designated successor in charge and verify that the successor can perform the required administrative tasks. Preserve a second recovery route under the organization's control when the service supports it.

Think about the work attached to the account. A scheduled report might be owned by the departing person. A donation confirmation may reply to their email. In WordPress, consider how existing content should be attributed when removing an author. The goal is a site that continues to work for the public and has an accountable owner behind each service.

Account for active sessions and shared access

Some services let an administrator revoke active sessions. Others have separate controls for integrations, linked applications, or devices. Follow the service’s current guidance and separate a routine departure from an urgent access incident. If your organization has an incident procedure, use it for the urgent case. A normal personnel checklist cannot answer questions about a suspected compromise.

Where a password or credential was shared, removing an individual username does not change who knows the shared value. Coordinate its replacement with the owner of each dependent service. A form integration that suddenly loses access can quietly stop delivering inquiries. Make one planned change, test the legitimate connection, and record who owns future changes. Named accounts are easier to review the next time someone leaves.

Verify the handoff through an ordinary task

Have the successor publish a harmless draft internally, open a routine report, or view the billing notices they now own. Check the relevant administration screens for the former user's permissions. Use the platform's own controls and logs for confirmation. Nobody needs to borrow the former employee’s password to verify a clean handoff.

Send an approved test through the public contact form and confirm that the right team receives it. Check the reply address as well as the destination. A surprising number of handoffs succeed on the account side while leaving customer correspondence routed toward a person who has moved on.

Keep a record the next administrator can use

A useful completion note identifies the person or vendor, the services reviewed, the successor, and any outstanding item with a responsible owner. Record the date of the verification. If a vendor controls one account and has not yet confirmed removal, leave that item open. That short list gives management a meaningful view of what remains.

Use the next onboarding conversation to improve the process. Ask what the new person actually needs to do, provide the appropriate role, and record where it was granted. An occasional review of privileged accounts is much easier when every grant starts with a purpose. The next departure then becomes an orderly transition instead of a search through years of email.

Sources & further reading