Why access drifts
Adding a user takes a minute and has someone asking for it. Removing one takes a decision and has nobody asking. The container governance guide says access "decays faster than anything else" for exactly that reason, and what is true of a tag container is true of every tool in the stack. Each kind of drift has its own cause, and the review has a step for each.
| Kind of drift | How it usually happens | Where the review catches it |
|---|---|---|
| Former staff still able to sign in | Nobody told the tool owner, or the tool was not on the leaver list | Match every account |
| Agencies and freelancers after the work ended | Access was granted for a project and never withdrawn | Review agency and freelancer access |
| Too many administrators | Admin rights given to get something done quickly | Confirm owners and deputies; check roles |
| Roles wider than the work | A person changed jobs and kept their old access as well as gaining new | Check roles against work |
| Shared logins | Quicker than adding users, or the tool was bought on one person's account | Replace shared logins |
| Integrations under a personal account | Someone connected two tools with their own credentials | Check integration and service accounts |
| Nobody to grant or remove access | The only administrator left | Confirm owners and deputies |
The reason to care is not only security in the abstract. Many marketing tools hold Personal DataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier.: the CRMThe system that stores an organisation's contacts, companies, deals and interactions, and the processes built around it., the email platform, form tools, analytics with user-level data, ad accounts holding customer lists. The GDPR's principles, as the GDPR glossary entry states them, include keeping personal data secure, and the business as controller must be able to show that it complies. A reviewed and recorded access register is part of how it shows that. Anything beyond that, such as which rules apply to a particular tool or dataset, is a decision for whoever owns data protection in the business.
Several pages already cover parts of this. The marketing tool onboarding SOP sets access when a tool arrives. The tutorial on taking over marketing brings every account under the business's control once, at a handover. The approvals and compliance reviews guide names an access audit among the periodic audits worth scheduling. Platform guides cover one platform each. This tutorial is the recurring review across every tool, using the onboarding SOP's rules as its tests.
Before you start
Gather five things. The stack record, or whatever list of tools the business keeps, with each tool's owner; the tutorial on running a marketing stack audit builds one if none exists, and the marketing stack hub describes what owning a tool means in practice, including holding administrative access and the renewal. A current list of staff and contractors with their roles, from whoever keeps people records. A list of suppliers with live engagements and the date each one ends. The access register, if the onboarding SOP has been used and one exists. And administrator access to each tool, held by someone in the business; a tool where nobody in the business can see the user list is the review's first finding.
Then agree who decides. A short RACI matrix with one row per tool, one accountable owner for access decisions on each, and the review's coordinator as responsible, prevents the most common stall: a list of removals that everyone agrees with and nobody makes. Ask whoever owns data protection which tools hold personal data, and review those first.
The onboarding SOP's access rules become the tests every account is checked against:
- Individual accounts. Every person signs in as themselves, never through a shared login.
- Least access. Each person has only the access their work needs.
- Few administrators. Admin rights sit with the tool owner and marketing operations.
- A named deputy. Someone else can administer the tool if the owner leaves.
- Security features on. Whatever sign-in protections the supplier offers are switched on.
The steps
Build the access register from each tool's user list
For each tool, take the user list from the tool itself, not from memory or from the old register, because the tool's own list is the only one that shows who can actually sign in. Include invited users who never accepted, users marked inactive but not removed, and any accounts used by integrations or by the supplier's own support staff. Record each account in one register with the tool, the name or address on the account, its role, whether it has administrator rights and the date it was added if the tool shows one. Tools that come from outside the stack record, found on card statements or in the tag container, go in too.
Match every account to a current person, supplier or integration
Take each account and find what it belongs to: a person on the current staff list, a supplier with a live engagement, or an integration the stack still runs. Mark anything that matches nothing. Unmatched accounts are the main yield of the review: former staff, former suppliers, test accounts and generic addresses nobody can explain. Do not remove anything yet; an unmatched account may still authorise something, and the later steps decide what happens to each.
Confirm each tool's owner and a deputy administrator
For each tool, confirm the owner can sign in with administrator rights and is still in post, and that a second named person can administer it if the owner is away or leaves. The onboarding SOP asks for that deputy so that the account is not lost with one person. Then look at the administrator list as a whole and shorten it: the container governance guide asks for the account-level administrator list to be kept very short, because an administrator can grant themselves anything. Where nobody in the business holds administrator access, recovering it comes before everything else on that tool.
Check each person's role against the work they do
For every matched person, compare their access with their current job. Someone who reads reports does not need to edit; someone who builds does not need to publish or administer. Movers are the usual finding here, carrying access from a previous role alongside the new one. Each platform names its roles differently, so use the platform guides for the detail: the guide to Google Ads manager accounts and access, the tutorial on setting up a Meta business portfolio, the tutorial on securing social media accounts and the container governance guide for the tag manager (GTMTag management system.). For reports, remember that sharing a dashboard and granting access to the data behind it are separate decisions, as the guide to sharing and embedding Looker Studio reports explains.
Review agency and freelancer access against live engagements
List every account held by an agency, freelancer or other supplier and set it beside the engagement it serves. The business owns its accounts and grants access to suppliers, which is the principle the takeover tutorial takes from the manager accounts guide, so a supplier's access is the business's to withdraw. Where the engagement has ended, the access goes; container governance puts it plainly, that an agency that finished last year should not still be able to publish. Where the engagement continues, check the role is no wider than the work. A supplier that owns an account the business depends on is an ownership problem, not an access one, and the agency offboarding checklist and the GA4 property handover checklist for the GA4Google's event-based analytics platform. property cover moving it into the business's name. Where the account is a local listing the business can no longer manage, the diagnosis for being locked out of a Google Business Profile works out who holds it before any access request. When the supplier is hired to configure and run the tools in the first place, the guide to hiring and evaluating a marketing technology partner settles before the work starts which seats, credentials and copies stay in the business's name.
Replace shared logins with named accounts
Find every login used by more than one person: a team inbox that signs in to a scheduling tool, an owner's password passed round, a generic account bought on one person's card. Give each person their own account at the narrowest role that does the job, then change the shared password so that it stops working for everyone who knew it. A shared login cannot show who did what and cannot be withdrawn from one person, which is why the onboarding SOP rules it out. Where a tool genuinely offers only one login, the tutorial on securing social media accounts describes the fallback: a business-held vault, protected sign-in, and a change of password whenever someone who knew it leaves.
Check integration and service accounts and who holds their credentials
List the accounts and keys that let one tool reach another: integration users, connection tokens, keys held by a supplier, connections authorised under a person's own login. For each, record what it connects, who holds the credential and whether that person or supplier is still current. A connection authorised under someone who has left, or under a supplier whose work has ended, is a finding even if it still works. The tutorial on reassigning CRM records when someone leaves sets the order: reconnect the integration under an integration user or a long-term owner, check the data still flows, then remove the old access. The agency offboarding checklist adds that keys a supplier used are rotated. Where the business keeps an integration register, as the tutorial on documenting marketing integrations builds one, its credentials and owner columns are the list to check, and this step updates them.
Remove, downgrade and record each change
Work through the findings tool by tool. Hand over first and remove second: records owned by a leaver go to a new owner, integrations move to a lasting account, then sign-in goes. Downgrade roles that are wider than the work. Record each change in the register with the date, what was done, who did it and why. That record is the evidence the review happened; the approvals guide asks for audit trailsThe record, attached to the work item, of what was reviewed, which version, who reviewed it, when, what they decided and the evidence relied on. because a control that cannot be shown later is barely better than none. Note anything that could not be fixed, such as a tool where only the supplier can remove a user, with an owner and a date.
Set the triggers for joiners, movers and leavers between reviews
A review fixes access on one day. Triggers keep it right on the others. Write down what happens when someone joins (the tool owner grants access on request at the right role), moves (their old access is reviewed with the new), or leaves (their access is removed on their last day, after the handover; the tutorial on securing social media accounts makes the same-day rule explicit for social accounts), and when a supplier's engagement ends (the agency offboarding checklist runs). Make sure each tool's owner is on the leaver notice. The marketing tool access request SOP writes these triggers out as one procedure, from the request and its end date to the register row that closes it. The joiner trigger is easier to keep when the access each role needs is listed in the team's onboarding pack for new marketers. The handover before a leaver's last day, from recurring tasks to files on personal drives, is covered by the tutorial on handing over marketing work when someone leaves. Then put the date of the next review in the register, with the coordinator's name beside it.
The access register
The register is a working table, kept with the stack record. One row per account in each tool is enough; the point is that every row is matched, owned and dated. The stack recordThe live register of every marketing tool: owner, deputy, cost, notice date, users, use cases and status, kept current by onboarding, reviews and retirement. holds one row per tool; the register holds one row for each account inside those tools.
| Field | What to record | Why it matters |
|---|---|---|
| Tool | The tool, with its owner and deputy | The owner decides access for the tool |
| Account | The name or address the account uses | Matching to a person, supplier or integration |
| Belongs to | Current person, supplier with live engagement, integration, or unmatched | Unmatched accounts are the main finding |
| Type | Individual, shared, integration or service, supplier | Shared and integration accounts get their own steps |
| Role | The access the account has, in the tool's own terms | Checking role against work |
| Administrator | Yes or no | Keeping the administrator list short |
| Holds personal data | Whether the tool holds personal data the account can see | Prioritising the review |
| Granted | When and by whom, where known | Tracing how access drifted |
| Last reviewed | The date of this review | Showing the control works |
| Action | Kept, downgraded, removed, handed over, open finding | The record of the review |
The register also answers the questions that come up between reviews: who can see a customer list, who can publish a tag, who still has access from a supplier the business stopped using. If it cannot answer them, it is missing rows.
A lettings agency reviews its tool access (illustrative)
Varnokel Lettings reviews access across its marketing tools
Varnokel Lettings, an invented lettings agency with 4 branches, runs its first access review across the 12 tools its marketing team uses. The register built from the tools' own user lists holds 87 accounts; the staff list has 31 names and the supplier list 3 live engagements.
Matching leaves 14 accounts unmatched. Nine belong to former staff, including a branch manager who left 8 months earlier and could still export the CRM's landlord contacts. One is an analytics agency whose contract ended the previous spring and which still holds administrator rights on the analytics property and the tag container. Two are test accounts from a form tool trial, and two are invited users who never signed in.
Two more findings come from the later steps. One branch signs in to the social scheduling tool through a single shared login known to 6 people, and the email platform's connection to the CRM was authorised under the former branch manager's account.
The marketing lead, accountable for access in the RACI agreed at the start, reconnects the CRM integration under an integration user and checks that new enquiries still arrive, then removes the 9 former staff accounts. The agency's access is removed once the team has confirmed that the business, not the agency, owns the analytics property and the container. Each of the 6 branch staff gets their own scheduling account and the shared password is changed. Administrator rights fall from 19 accounts to 11, every tool gets a named deputy, and the leaver form now lists all 12 tools and their owners.
Verify it worked
- Compare each tool's own user list with the register. Every account in the tool has a row, including invited and inactive users.
- Filter the register for unmatched accounts. Each is explained, removed or logged as an open finding with an owner and a date.
- Open each tool's administrator list. The owner and a named deputy can both administer, and the list is shorter.
- Ask someone who knew an old shared password to try it. It fails, and each person has their own account.
- Check a reconnected integration. Data still flows, its credential holder is current and the register records the change.
If it goes wrong
- Nobody in the business can see a tool's user list. Administrator access probably sits with a leaver or a supplier. Recover it before anything else on that tool.
- Nobody can explain some unmatched accounts. They may still authorise something. Leave them until the later steps decide what each does.
- An integration stops after a removal. It was probably authorised under that account. Reconnect it under an integration user, check data flows, then remove the old access.
- Agreed removals never happen. Nobody is accountable for each tool. Name one accountable owner per tool in the RACI and make the coordinator responsible.
- Access drifts again after the review. The triggers are probably missing. Write joiner, mover and leaver triggers, put every tool owner on the leaver notice and date the next review.
Next steps
- Read the tutorial on running a marketing stack audit to build a stack record if you have none.
- Read the tutorial on documenting marketing integrations to keep credentials and owners current between reviews.
- Read the tutorial on reassigning CRM records when someone leaves for the hand-over order to reuse in other tools.
Common mistakes
- Reviewing from the old register. Only each tool's own user list shows who can sign in today; start there.
- Removing before handing over. Deleting a leaver's account can orphan records and break integrations authorised under it. Hand over, then remove.
- Forgetting integration accounts. Keys and connections under a person's or supplier's name outlive their owner unless someone looks for them.
- Leaving agencies as administrators. A supplier needs the narrowest role the work allows, and none at all once the work ends.
- Tolerating one shared login "just for this tool". It cannot show who did what and cannot be withdrawn from one person.
- No deputy. A tool with one administrator is one resignation away from being locked.
- Fixing without recording. A review with no dated record cannot show that access is controlled.
- Relying on the review alone. Without joiner, mover and leaver triggers, access drifts again the day after.
