Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Standard Operating Procedures

Marketing Tool Access Request SOP

A standard procedure for granting, changing and removing access to marketing tools when people join, move or leave and when suppliers start or stop.
SOPbeginner10 min readUpdated

Owner, trigger and scope

Each tool's owner grants and removes access in their tool. They decide the role, because they know what each level can do and they answer for who holds it. The requesting manager states the work, the tools it needs and an end date; for a supplier, that is the manager who runs the engagement. Marketing operations keeps the access register, makes sure every tool owner hears about leavers and ended suppliers, and coordinates removal across the stack. A short RACI matrix with a row per tool, naming the accountable owner and the deputy, is the quickest way to make those roles stick.

The trigger is any of four events: someone joins the marketing team, changes role or leaves the business, or an agency, freelancer or other supplier starts or ends an engagement. Each event can touch many tools at once, and the procedure runs once per event across all of them.

The procedure sits between three neighbours that own their own jobs:

SituationWhere it is handled
A new tool arrives and its roles are set up for the first timeMarketing tool onboarding SOP
The periodic check of every account in every toolReviewing access to marketing tools
Social accounts: ownership, admins, recovery details and handlesSecuring social media accounts
Whether the business is paying for seats it does not useReviewing licences and seats

The access review's last step names the joiner, mover and leaver triggers in a paragraph; this SOP writes them out. If an account looks as though it is in the wrong hands, stop and run the compromised marketing account response SOP rather than an access request. The SOP library routes the other recurring operational jobs.

Before you start: inputs and access

InputOwnerNotes
The requestRequesting managerThe person or supplier, the work they will do, the tools, the role and an end date
The access list by roleMarketing operationsFrom the team's onboarding pack for new marketers
The access registerMarketing operationsOne row per tool and person or supplier, as the access review builds it
The leaver notice or supplier datesRequesting manager, with people recordsThe last working day, or the engagement's start and end
The business vaultMarketing operationsFor any credential that cannot be a named account

Each tool owner needs administrator access to their own tool, held by someone employed by the business. A tool where only a supplier can add or remove users is an ownership problem; fix it through the review before the next request arrives.

The procedure

  1. Take the request with the work, the tools and an end date

    Ask the requesting manager for the request in writing, in the team's usual intake place: who the person or supplier is, the work they will do, the tools that work needs, the role in each and the date the access should end or be reviewed. For a joiner, start from the access each role needs as the onboarding pack tutorial lists it, so the access is ready on the first day and nothing is guessed. For a supplier, the agency onboarding checklist puts access first in its order and is the list to run alongside this step. A request with no work or no end date goes back to the manager before anything is granted.

  2. Check the role against the work and the narrowest level that allows it

    For each tool, the tool owner compares the work with the roles the tool offers and picks the narrowest one that lets the work be done. Someone who reads reports does not need to edit; someone who builds does not need to publish or administer. The access review tutorial sets these tests: individual accounts, least access, few administrators and a named deputy. Each platform names its roles differently and its help centre is the reference for them, so record the role in the tool's own terms rather than translating it. Where a tool holds Personal Data, such as the CRM or the email platform, ask whether the work needs the data at all.

  3. Grant a named account through the business's own ownership structure

    Grant access from the business's own account, never by sharing a login or by moving an asset into someone else's. The guide to Google Ads manager accounts and access states the principle: the business owns its account and grants access to agencies, not the other way around. The same rule runs through the Meta business portfolio tutorial, the TikTok Business Center tutorial and the LinkedIn Campaign Manager tutorial, each of which shows how a supplier is given access to assets the business keeps. For analytics, the property stays in the business's account and the supplier gets a user role on it; the GA4 property handover checklist holds the ownership lines to confirm whenever a GA4 property is shared with a supplier.

  4. Switch on two-factor sign-in and keep any shared credential in the vault

    Confirm the new account signs in with two-factor sign-in wherever the tool offers it, checked rather than taken on trust. The tutorial on securing social media accounts asks for this on every platform and, as general practice, keeps any credential the business itself must hold, such as the login for a tool that does not support individual users, in a password vault the business owns. The vault records who can open each entry, so a shared credential can at least be traced and changed when someone leaves. Never send a password by email or chat.

  5. Record the grant in the access register

    Add a row to the register for each tool: who asked, who granted, the person or supplier, the role, whether it is administrator access and the end or review date. The access review builds its register from each tool's own user list and checks every account against it, so a grant that never reaches the register becomes the next review's unexplained account. Confirm the tool still has an owner and a deputy administrator after the change, and that the administrator list has not grown without a reason.

  6. For a mover, review the old access with the new

    When someone changes role, the new access is only half the request. List what they hold from the old role and decide, tool by tool, what the new work still needs. The access review names movers as the usual source of roles wider than the work, carrying old access alongside new. Downgrade or remove what the new role does not use, and move anything they owned that the old team still depends on, such as reports, records or an integration, before the old access goes. Record each change on the register.

  7. For a leaver, finish the handover, then remove access the same day

    Marketing operations sends the leaver's name and last day to every tool owner on the register. The handover comes first: the tutorial on handing over marketing work lists the accounts, pages and admin rights held in the person's name and gives each a new owner. In the CRM, the tutorial on reassigning CRM records when someone leaves moves owned records, routing, sender names and integrations before the sign-in goes. Then, on the last day, every tool owner removes the person's access. The social accounts tutorial makes the same-day rule explicit, and it applies across the stack. Removal deals with sign-in; a paid seat that is no longer needed is released through the licence and seat review, so the two do not drift apart.

  8. For a supplier that ends, run the offboarding order and rotate credentials

    When an agency, freelancer or other supplier ends, run the agency offboarding checklist in its order: ownership first, then assets and knowledge, then continuity, and access removal near the end, so the supplier can hand over what the business still needs before it loses sign-in. Remove every supplier user from ad, analytics, tag and social accounts, then rotate shared passwords and integration keys the supplier used. Check connections authorised under the supplier's own credentials, which keep working after the people are gone. Close the supplier's rows on the register with the date and who removed each one.

A veterinary group's quarter of access requests (illustrative)

Illustrative example — not a real result

Four access events in one quarter, and one the register caught

Klovanti Vets, an invented group of 6 veterinary practices, runs its marketing on 9 tools with a team of 5 and an analytics agency. In one quarter the procedure runs 4 times.

A content assistant joins. The request lists the content management system, the social scheduler and the asset library, with a review date at the end of the probation period. Each tool owner grants a role that lets her draft and upload but not publish or administer, and the assistant's accounts are ready on the first morning with two-factor sign-in on.

The paid media manager moves to email. The email platform's owner grants access, and the review of the old role finds administrator rights on both ad accounts. They are reduced to the narrowest viewing role for 2 weeks while the paid media work is handed to a colleague, then removed.

A practice marketing coordinator leaves. The handover gives her 3 social pages and 140 open CRM records new owners, and an integration she had connected under her own login is reconnected under an integration user. On her last day all 7 of her accounts are removed.

The agency's contract ends. Running the offboarding order, marketing operations checks the register and finds the agency still holding administrator rights on the analytics property, granted 2 years earlier for a set-up project and never reduced. The business confirms it owns the property, the agency's access is removed with the rest, and the tag container's shared publishing password is changed.

QA checks

Before each request is closed, marketing operations checks the register and the tools against the list below. Where a check fails, fix it in the tool and record the fix rather than noting it for the next review.

  • Every grant is a named account at the narrowest role the work needs.
  • Each tool still has an owner and a deputy administrator after the change.
  • Leavers and ended suppliers appear in no tool's user list.
  • Records the leaver owned have a new owner.
  • The register row shows who asked, who granted, the role and the end date.

Hand-offs and records

The procedure hands on three things. The requesting manager is told the access is live, with the role in each tool and the end or review date, so they know when to renew or withdraw it. Each tool owner keeps a current user list that matches the register. The next periodic access review receives a register in which every account already has a reason, so it spends its time on drift rather than on reconstructing who asked for what.

Where a tool holds personal data, the register is also part of how the business shows that access is limited to the people who need it. The GDPR, as the GDPR glossary entry states it, includes keeping personal data secure, and the controller must be able to show that it complies. Which rules apply to a particular tool is a decision for whoever owns data protection; this is general direction, not legal advice.

The lasting record is a row in the access register per tool and per person or supplier: request date, requester, role granted, granted by, end or review date and, on removal, the date and who removed it.

Common mistakes

Most access problems start with a shortcut that saved a few minutes on the day.

  • Sharing a login to save time. It cannot show who did what and cannot be withdrawn from one person.
  • Granting the role the last person had. Start from the work, not from a colleague's access.
  • No end date. Access without an end or review date stays until a review finds it.
  • Adding the new role and keeping the old. Movers are where roles grow wider than the work.
  • Removing before the handover. Records, reports and integrations end up under an account nobody can open.
  • Waiting after the last day. A former colleague who can still sign in can still post, export or change spend.
  • Letting a supplier hold the account. The business owns the asset and grants access to it, not the reverse.
  • Forgetting integration keys. Rotate what a supplier used; connections outlive the people who made them.
  • Granting without recording. A grant that never reaches the register is the next review's mystery account.

Frequently asked questions

Who should approve a request for access to a marketing tool?

The tool's owner grants it, because they know what each role in the tool can do and they are accountable for who holds it. The requesting manager's part is to say what work the person or supplier will do, which tools that needs and when it ends. Marketing operations does not approve each grant; it keeps the register and makes sure leavers and ended suppliers are handled across every tool.

Should an agency be given the login of the business's own account?

No. The business owns each account and grants the agency its own named access to it, at the narrowest role the work needs. A shared password cannot show who did what and cannot be withdrawn from one person without changing it for everyone. Where a platform offers a way for a supplier's own business account to be linked or given access, that is the route, as each platform's help centre describes.

When should a leaver's access be removed?

On their last day, after the handover. Removing access first can leave records, reports and integrations stranded under an account nobody can open; leaving it in place after they go means a former colleague can still sign in. Hand over first, then remove every account on the register on the same day.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Google Ads Help — Google Ads Help
  2. Meta Business Help Centre — Meta Business Help Centre
  3. Regulation (EU) 2016/679 (GDPR) — EUR-Lex

Related