Quick answer
When a former agency may still have website access, list every system it could reach, record each account and access level, confirm which accounts belong to the business, approve removals in writing and verify them by checking the user list afterwards. Ask for transfer of any account held in the agency’s name before removing access.
- Ask the agency for its own list of systems and compare it with yours, since each side usually forgets something.
- Include shared logins and API keys, and change shared passwords after removing access.
- Verify removal by checking the user or access list yourself, and keep a record of what was removed and when.
When an agency hands over a site, access routes can linger. Record every system, account and access level, confirm business ownership and verify removals. This article helps owners check without assuming they know everything. It is written for business owners responsible for website access and ends with the decision, owner and next step to record.
An illustrative scenario
This is a hypothetical example, not a Web Design Davao client case.
Situation. An agency handover leaves several known or suspected access routes behind.
What happens. After an agency handover, an owner knows the agency had a WordPress login, access to the hosting panel and the analytics account. She lists every system, asks the agency to list its own, compares the two, checks which accounts sit in the business’s name, removes access with written approval and then logs in as an admin to confirm the agency accounts are gone.
Access inventory
List every system the agency could have reached: hosting, the domain account, WordPress, analytics, tag manager, email and any third-party tools. Use the system and account fields. Ask the agency for its own list and compare it with yours, because each side usually remembers something the other forgot. Include shared logins and API keys, which are easy to overlook.
Ownership verification
For each account, record the level of access and confirm who owns it. Use the access level and business owner fields. An account in the agency’s name is not yours to remove, so ask them to transfer it first. Do not remove access you do not understand, because some accounts support automatic tasks. Ask your maintainer if you are unsure.
Revocation and audit
Approve removals in writing, carry them out and verify. Use the removal approval and verification fields. Verification means checking the user list or access list afterwards, not trusting a message that it was done. Change shared passwords, and keep an audit record of what was removed, when and by whom.
Agency access exit checklist
Use this at the point described above. The workflow owner completes it and a named reviewer checks it. A completed row shows that the information, owner and next step are recorded; it does not prove the outcome. Keep it somewhere the team can edit, and keep it free of passwords, tokens and real client records.
Blank copy
| System | Account | Access level | Business owner | Removal approval | Verification |
|---|---|---|---|---|---|
Illustrative completed row (hypothetical)
| System | Account | Access level | Business owner | Removal approval | Verification |
|---|---|---|---|---|---|
| WordPress admin | Agency user account | Administrator | Business owner | Owner approves removal | User no longer listed |
Working through the completed row
The example row lists the WordPress admin, an agency user account, the administrator level, the business owner, the owner’s approval for removal and verification that the user no longer appears.
Common mistakes
- Trusting a message that access was removed.
- Forgetting API keys and shared logins.
- Removing accounts you do not understand.
Questions to settle before you rely on it
- Which systems did the agency touch?
- Who in the business owns each account?
- How will removal be verified?
How you know it is complete
The checklist is complete when each system has an account, access level, owner, approval and verification. Record who reviewed it and the date.
Where you may not have the answer
An account is held in the agency’s name. Ask them to transfer it before you remove access, and record the request. The handoff, not a guess, is the correct next step.
Your next action
Compare your system list with the agency’s.
Ask Web Design Davao to review this workflow and scope the website or marketing support required. Website maintenance & security arrangements are agreed individually; nothing here assumes a particular service, role or timing is already available.
How Web Design Davao works
- Enquiries are generally answered within four hours during support hours (Monday to Friday, business hours), with after-hours help for emergency requests. Scope is agreed individually.
- Preventative website maintenance includes keeping plugins up to date and reviewing website code for known vulnerabilities. This reduces exposure to attack; it does not guarantee a site cannot be compromised. See website updates and uptime monitoring.
Frequently asked questions
Which systems should I check after an agency handover?
Hosting, the domain account, WordPress, analytics, tag manager, email and any third-party tools. Include shared logins and API keys, which are easy to overlook. Ask the agency for its own list and compare it with yours.
What if an account is in the agency’s name?
Ask them to transfer it to the business before you remove access, and record the request. An account in the agency’s name is not yours to remove, and some accounts support automatic tasks, so ask your maintainer if unsure.
How do I know access was really removed?
Check the user list or access list afterwards, for example by logging in as an administrator, rather than trusting a message that it was done. Approve removals in writing and keep an audit record of what was removed, when and by whom.