Contractor access management means giving contractors only the access the work needs, through accounts you can see, with an end date written down on the day you grant it. Do that, and offboarding a contractor is a ten-minute job. Skip it, and their access quietly outlives the contract.
Contractors are where lingering access is most common in small companies, for structural reasons rather than carelessness. This post covers why, the choice between giving them a company account or using their own email, whether they count as seats, how to track what they have, and how to end it.
Why contractors are different
An employee leaving is an event. HR knows, the manager knows, there is a last day and usually a farewell message. A contract ending is often none of those things. The invoice stops. Nobody sends anything.
Several other things make contractors harder to manage than employees. They are often not in your directory: if they have no Google Workspace account, suspending someone in Google does nothing for them, and any tool that matches people to your directory treats them as strangers. They use their own email, and an account under [email protected] looks like nobody you employ, so it survives reviews where everyone checks names they recognize.
Access is also scattered by design. Whoever hired them invited them: the marketing lead added the freelance designer to Figma, and the CTO added the agency developer to GitHub. No one person knows the full picture. Agencies make it worse by rotating people. The developer who started on your project may not be the one who finishes it, and the first one's access is rarely removed when the second arrives.
Finally, they work for other clients too. Their laptop, password manager and browser sessions are shared with work you know nothing about. That is not a reason to distrust them. It is a reason to keep what they can reach narrow, and to end it cleanly.
Giving access: their email or yours
The first decision is which identity the contractor uses in your tools.
| Company account ([email protected]) | Their own email | |
|---|---|---|
| Shows in your directory | Yes | No |
| Suspending one account ends Google sign-in | Yes | No; each tool separately |
| Costs | A Google Workspace license, plus each tool's seat | Each tool's seat, or a guest role |
| Files they create | Owned by your account | May be owned by their account |
| Best for | Long engagements, many tools, sensitive data | A short job in one or two tools |
A useful rule: if the contractor needs more than a handful of tools, or touches customer data, money or production systems, give them a company account. It costs a license, and it buys you a single switch to turn them off and a name in every member list that you recognize.
For short, narrow work, most tools have a guest or collaborator role that limits what an outsider can see. Two examples, from each vendor's help pages as we read them on 27 October 2026. Slack has guests, but only on paid plans. Per Slack's guest documentation, multi-channel guests are billed like regular members, while single-channel guests are free, up to five for each paid active member. GitHub lets you add an outside collaborator to specific repositories without making them an organization member. On the Team plan, GitHub bills outside collaborators on private repositories owned by your organization, so a contractor on a private repo is a paid seat.
Where files are concerned, put contractor work in shared spaces you own. Google, for example, says the organization owns the files in a shared drive, not an individual, and they stay when the person's account goes (Google's shared drives help). Files a contractor creates in their own personal Drive and shares with you stay theirs.
Do contractors count as seats?
In most per-seat tools, yes. A contractor with a member account in Figma, HubSpot or your support desk takes a seat exactly like an employee. The two examples above show the exceptions are narrow and specific: Slack's single-channel guests are free within a ratio, and GitHub bills outside collaborators on private repositories on the Team plan. A company Google Workspace account needs a license of its own.
That makes contractors a money question as well as a security one. A finished contractor who is still in three paid tools costs you three seats a month until someone notices. If you are already reviewing seats for cost, SaaS license management covers how to find them, and contractor accounts under outside email addresses are usually the easiest wins.
Give the least access that does the job
Contractors are the clearest case for the principle of least privilege: access to what the work needs, at the lowest role that does it, for as long as the work lasts. In practice that means a guest or viewer role where one exists, a single project or repository rather than the whole workspace, and no admin rights unless the job is literally administration. If a contractor needs admin to do one setup task, grant it for that task and take it back when it is done.
It also means avoiding shared logins. Giving a contractor the password to an account several people use means you cannot remove them without changing it for everyone. Shared accounts covers the alternatives.
Tracking it
Keep a contractor register. It can be a sheet, with one row per contractor. Record their name and company, if they come through an agency, and the email they use in your tools, which may differ between tools. Record a sponsor: the employee who hired them and answers for their access. List each tool with the role given, a start date and an end date. And note any API keys, SSH keys or integrations they set up, because those are the things nobody remembers at the end.
The sponsor column matters most. Access with no named owner is access nobody removes. When a sponsor leaves the company, their contractors move to someone else, or their access ends too.
Review the register whenever you review employee access. The user access review post has a process that works for both. The register is the contractor-shaped version of the who-has-what record described in provisioning and deprovisioning.
At 5 people and at 50
A five-person company with one freelancer does not need a register; it needs the freelancer's email written next to the two tools they use, and a reminder on the end date. A fifty-person company with a design agency, two freelance developers and a part-time bookkeeper does. That is several sponsors, several outside email domains and a dozen tools, and nobody holds it all in their head.
End dates
Every contractor gets an end date the day they get access, even if the date is a guess. A wrong end date that triggers a conversation is better than no end date.
Some tools let you enforce it. Slack lets workspace owners and admins set automatic deactivation for guests, either after a period or on a custom date, with a reminder five days before, according to the same Slack help page. Where a tool has no such setting, put the date in a calendar with the sponsor and whoever removes access as attendees.
When a contract is extended, extend the end date explicitly and update the register. An extension that only exists in an email thread is how the end date stops meaning anything.
Offboarding contractors
When the contract ends, or the agency swaps the person out, work through the same steps every time.
Remove them from every tool in the register, by the email they actually used there. Then search each tool's member list for their name and other addresses, in case the register missed something.
Revoke the keys. API keys, SSH keys and deploy keys they created come next, and any integration that runs under their account moves to one you own first. Removing the person before moving the integration is how a contract ending takes down a business process.
Move their files. Anything they own goes to a shared space or an employee's account, before you remove them; some tools will not let you transfer ownership from an account that is already gone.
Change shared passwords they knew, and check where the two-factor codes for those accounts go.
If they had a company account, suspend it, then follow your usual employee offboarding checklist for the rest.
Close the row. Mark it in the register as ended, with the date.
For agencies, ask in the contract to be told when a person leaves your project. You cannot remove access you do not know should end. Revoking access covers sessions and tokens in more depth if you suspect something is still live.
Common mistakes
The first is inviting contractors as full members because it is quicker than finding the guest setting. The second is letting the sponsor be "whoever is around"; access with a vague owner has no owner. The third is forgetting the agency's previous people when a new one arrives. And the fourth is treating the last invoice as the end. Payment stopping is not an offboarding signal anyone receives, unless you make it one.
Where SmashSSO fits
SmashSSO helps most with the visibility problem. Its access grid shows who has an account in each tool and with what role, matched by email against your Google Workspace directory, and accounts that match nobody there are flagged. A contractor on a personal email shows up as one of those unmatched accounts, so you can see them, decide, and remove them from one place, through a tool's member API where you have added a token or through an agent in your own Chrome otherwise. Contractors with company accounts are covered like employees: when they are suspended in Google Workspace, you are alerted and shown where they still have access.
It does not keep a contractor register or end dates for you, and it is not SSO. Agent-run changes need your Chrome open and can fail when a tool changes its screens, and some tools' terms restrict automated use. It costs a flat fee from $199 a month, billed annually (pricing). How it works has the details, and orphaned accounts covers what to do with the strangers you find.