A process for requesting access to client ad accounts

Every login an agency holds is a risk and a responsibility. A written request, a named approver and a planned removal keep the list short and explainable.

Request

  • Requester names the client, the account, the role needed and the reason, in one line.
  • Ask for the lowest role that does the job, and widen it only when a task needs it.
  • Set an end date for anything temporary, such as a contractor or a one-off audit.

Approve and grant

  • The client owner approves in writing. Agency leads approve their own team.
  • Anyone who can spend money or change a live setting needs a second approver. No shared logins, ever.
  • The person who grants is not the person who requested. The grant goes into the register: client, account, person, role, approver and dates.

Review and remove

  • Each quarter, the operations lead compares the register with the real user list in each account, and removes anyone missing from it.
  • When someone leaves the team or the client, remove their access the same day and log it.
Made-up scenario: a freelancer had a 30 day audit role with an end date in the register. The end date was missed and the role stayed for three months. A weekly check of expired entries would have caught it.

Checklist

  • Each request names client, account, role, reason and end date.
  • Each grant has a named approver and a register entry.
  • Quarterly review done, and every mismatch fixed or explained.

5 min read. Last updated 2026-10-07. Examples use made-up numbers.

This guide in numbers

5minutes to read
3terms explained
4sections
4related guides

Use it as a checklist

Tick items as you go. Your ticks stay in this browser only.

Built for shop owners, creators and agencies. Stock photos, not customers.

Run the next client review from one screen.

We open one agency at a time, with your own accounts connected read-only first.

Request access

How we plan to price it