Help for owners
A freelancer or agency I stopped using still has access to my systems
Short answer
Make a list of every system the contractor touched, including accounts created in their name or their agency's. Disable named logins first, change shared passwords they knew, then check tokens, server keys and connected apps. The NCSC advises removing accounts of staff, suppliers or contractors who no longer need access, and reviewing access every few months.
Does this sound like your situation?
- The project ended months ago and I never asked what access they had.
- They set up my hosting, domain, repository or app store account under their own login.
- A shared password for the site or server has not changed since they started.
- I do not have a list of which tools they were given access to.
- A new contractor is starting and I am unsure how to separate the two.
Why does this happen?
Contractors are outside the leaving process
A staff leaver usually triggers a checklist. A contractor simply stops invoicing, so nothing tells anyone to close the accounts. The NCSC says accounts for staff, suppliers or contractors often stay active with outdated passwords and security settings.
Confirmed by ncsc.gov.uk
Access was granted in a hurry and never listed
In the first week, logins are created over chat. Nobody wrote down which tool, which role or which email address was used.
Some accounts belong to them, not you
Hosting, a domain, an app store listing or a repository set up under the contractor's own email cannot be removed by you, because you are not the owner.
Shared passwords are still known
Even if their user was disabled, a shared login stays valid until it is changed. People who knew it can still use it.
Keys and tokens do not expire with a person
Server keys, API keys and deploy tokens work whoever holds them. Removing a person's login does not make them stop working.
What can I do about it today?
- Write down what they were givenStart from the contract, emails and your own accounts. Include hosting, domain, code repositories, analytics, app stores, payment dashboards and cloud tools.
- Disable named logins, do not delete yetTurning an account off stops access while keeping its history, which you may need later.
- Change shared passwordsStart with email, hosting, payments and any admin login. Put new ones in a password manager.
- Check which accounts are in their nameIf a service lists the contractor as owner, ask them politely in writing to transfer ownership to your company email before access is removed.
- Ask them to confirm what they holdA short email asking them to list the systems they can still reach and to delete local copies of credentials. It is a courtesy, not a security measure.
- Put a review in the diaryThe NCSC advises reviewing who can access important accounts every few months.
When should I bring someone in?
- They set up your hosting, domain or app listing under their own accounts and are not responding.
- They had server or database access and you do not know which keys they hold.
- There was a dispute and you need access closed without breaking the site.
How do I handle it?
- Build the access mapI trace logins, keys and connected apps across your hosting, repository, cloud and payment accounts from the accounts you own.
- Take a backup before changing anythingA backup of the site and database is taken, so closing an account that something quietly relied on can be reversed.
- Rotate in the right orderShared passwords, then server and API keys, then deploy tokens, one at a time with a check that the service still works.
- Move ownership to the companyAccounts held in a contractor's name are transferred or recreated under an address the business controls.
- Write the next handover ruleContractors get named accounts with the least access they need, and a short exit checklist is part of every contract.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can I just delete their accounts?
Disable first. Deleting removes history and may break something that used the account. Delete once you have checked.
What if they did nothing wrong?
Closing access is routine, not an accusation. Most contractors expect it.
How is this different from a staff leaver?
The steps overlap, but contractors are often missing from the leaver process and may own accounts outside your control.
What if my own developer is the one with access?
The same method applies. Access should be named, limited and recorded, whoever holds it.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.