How to Remove Website Access When an Employee, Freelancer or Agency Leaves

How should a small business remove website access when an employee, freelancer or agency leaves?

Remove the departing person’s individual accounts first, then review affected shared credentials, recovery contacts and connected applications that may still provide access. Confirm that another authorised person can administer every affected service, update the ownership register and record any access that cannot yet be removed. Use named accounts for agencies and freelancers so future removal is cleaner.

Identify the person’s named accounts

A small-business security guide advises using separate accounts for agencies and freelancers because their privileged access can then be removed cleanly. Begin with the departing person’s named accounts across the services they could administer. Do not disable the only business-controlled administrator while removing a supplier or employee.

Sources: Small Business Website Security: Domain, Hosting, WordPress.

Decide which website responsibilities should return in-house or move to another care provider before the handover closes.

  • List individual accounts by service.
  • Confirm which access belongs to the business.
  • Keep a current administrator in place.

Check indirect and shared access paths

An account ownership guidance source recommends checking shared credentials, recovery contacts and connected applications when someone leaves. For every affected service, identify access paths that are not tied to the person’s obvious login. Apply changes to affected shared access rather than assuming every credential in the business must change.

Sources: Domain, Hosting, and Website Account Ownership | Vassal Marketing.

Set clearer approval and access boundaries for future website work after the immediate offboarding actions are complete.

  • Review affected shared credentials.
  • Review recovery contacts.
  • Review connected applications.

Confirm continuity and update the register

Continuity means every affected service still has a current authorised administrator after the departing person’s access is removed. Update the relevant register entries with current administrators, revised contacts and any remaining dependency. Pause and seek the provider’s current instructions if the intended change could remove the business’s last authorised access.

Assign a responsible human role for each outstanding action so the handover does not become an unowned task.

  • Confirm a current administrator remains.
  • Update the ownership register.
  • Record unresolved dependencies.

Close the offboarding record

A concise offboarding record should name the departing person, date, affected services, actions completed and remaining follow-up. Mark each unresolved item with a responsible person and a next review point. Retain the record with the ownership register so the business can understand later changes to access.

  • Date the record.
  • List services reviewed.
  • Record completed and outstanding actions.

Website access offboarding runbook

Use one row for each affected service after reviewing the departing person’s access. The columns capture named accounts, indirect access, administrative continuity and unresolved follow-up without duplicating the full ownership register.

Affected serviceNamed accessIndirect access reviewedCurrent administratorOutstanding action
Domain registrarAccount removed, changed or retainedShared credentials, recovery contacts and connected applications reviewedName of current authorised administratorUnresolved dependency, responsible person and next action
DNS providerAccount removed, changed or retainedShared credentials, recovery contacts and connected applications reviewedName of current authorised administratorUnresolved dependency, responsible person and next action
Hosting providerAccount removed, changed or retainedShared credentials, recovery contacts and connected applications reviewedName of current authorised administratorUnresolved dependency, responsible person and next action
Website platform or filesAccount removed, changed or retainedShared credentials, recovery contacts and connected applications reviewedName of current authorised administratorUnresolved dependency, responsible person and next action
Business email or connected applicationAccount removed, changed or retainedShared credentials, recovery contacts and connected applications reviewedName of current authorised administratorUnresolved dependency, responsible person and next action

Record outstanding access as unresolved rather than treating the offboarding as complete. Keep detailed current ownership information in the main register.

When this is not the right approach: This runbook is not a substitute for an active incident response process where an account may already be compromised. In that situation, use the relevant provider’s authorised security and recovery process.

What follow-up questions matter most?

Which website access should be removed first?
Start with individual accounts assigned to the departing person. Keeping agency and freelancer access in named accounts makes removal cleaner while preserving business-owned administration.
What indirect access should we check?
Review affected shared credentials, recovery contacts and connected applications as well as the obvious login. Record items that cannot yet be removed and assign them for follow-up.
How do we avoid locking ourselves out?
Before removal, identify a current authorised administrator for every affected service. Update the ownership register after the change so the current access position remains clear.

What steps does this workflow follow?

Offboard departing website access

  1. Identify named accounts: List the person’s individual access across the affected website services and confirm which accounts are business-owned.
  2. Preserve authorised continuity: Identify a current authorised administrator for each affected service before disabling the departing person’s access.
  3. Remove affected access: Remove or change the departing person’s individual access using the relevant provider’s authorised controls.
  4. Check indirect routes: Review affected shared credentials, recovery contacts and connected applications that could still provide access.
  5. Update the record: Update the ownership register and record any dependency or access route that remains unresolved.
  6. Close the handover: Keep a concise dated record of the services reviewed, actions completed and outstanding follow-up.