A freelancer finishes a project. A colleague moves to another team. A seasonal employee leaves after a busy period. The work changes, but their access to shared folders, dashboards and online tools may stay exactly as it was.
This is rarely a deliberate decision. In a small organisation, people are busy and the account that was useful yesterday simply gets forgotten.
Managing access well does not require a large security programme. It starts with treating permission as something connected to a real job, not something that lasts forever.
Begin with the work, not the account
When giving someone access, ask which task they need to complete and which information they actually need. Editing one shared document is different from administering an entire workspace.
Use individual accounts and the narrowest practical permissions that let the person do the job. Avoid shared logins when the service supports named users. A temporary project should have a clear point at which access will be reconsidered.
Make changes part of the handover
A change of role deserves an access review just as much as a departure. Someone may need a different set of tools without needing everything from their previous work.
When a contract or assignment finishes, the person responsible for the project should tell the person who manages access. Do not assume that payroll, a calendar invitation or the end date in a contract automatically removes permissions from every service.
Keep a short record of the services involved and who is authorised to review them. It can live in an existing team process rather than a new spreadsheet full of personal information.
Preserve the work before removing access
Check who owns shared documents, customer correspondence, scheduled reports and integrations. If an important resource is tied only to one individual's account, arrange an appropriate handover to a company-controlled owner before access ends.
This does not mean copying a departing person's private files or email. Follow the organisation's privacy, employment and retention rules, and involve the appropriate administrator when ownership is unclear.
The aim is to protect business continuity and remove permissions that are no longer justified, not to erase useful work.
Review what the tools actually show
Use the administration and sharing settings of each service to confirm access has changed. A name removed from a team list may still have a separate invitation to a folder or another application.
Pay special attention to external collaborators, old invitations and elevated administrative roles. When technical accounts or integrations are involved, have the responsible technical person check them rather than making an improvised change that could interrupt a working service.
If access cannot be removed immediately because work is still in progress, agree on an owner, a reason and a definite review date.
Keep the routine proportionate
A short review at the end of each project or role change is more reliable than an annual clean-up. For longer-running teams, a periodic look at who can access important systems helps catch permissions that no longer fit.
Avoid collecting more employee information than necessary. The useful questions are simple: who needs access, to what, for which work, and who can confirm it is still appropriate?
Good access management is often quiet. People have what they need to work, changes are handled promptly, and old permissions do not become permanent simply because nobody remembered to look.
