In this guide

An operator leaves a team and their login is removed. The weekly report stops running because it used that person’s authorization. Meanwhile, an old partner account still has access to the advertiser.

Access review is both a security task and an operations task. It needs to establish who can act and which ongoing processes depend on that access.

Inventory people and integrations separately

List named users, shared arrangements, partner links, service accounts, API credentials, and scheduled exports. Record the account scope, permission level, business owner, and reason for access.

A person disappearing from one interface does not prove that every connected system has been addressed. The ad platform, analytics property, tag manager, creative storage, and billing tools may have separate permission systems.

OWASP’s authorization guidance supports limiting access to the functions required. Applied operationally, a reporting-only role should not receive campaign-editing access merely because it is convenient.

Find hidden ownership dependencies

Check scheduled reports, automated imports, OAuth connections, and jobs created under the departing account. Determine whether they should continue and who will own them.

Transfer supported ownership through the platform’s documented process. Where an integration must be reauthorized, test the replacement before the old authorization is removed, provided the security circumstances permit that sequence.

If access must be revoked immediately, do so through the incident or offboarding process and track the expected service interruption explicitly. Avoid leaving unnecessary access active just because a dependency has not been documented.

Verify the effective result

After a change, inspect the actual permission list and integration status. Confirm that the intended owner can perform the required task and that the removed principal no longer has the relevant access.

Do not test by exchanging passwords. Use named accounts and the organization’s approved access process.

For credentials that require rotation, identify every dependent system, update it securely, and verify operation. Keep secret values out of tickets and handoff documents.

Review dormant access before it becomes urgent

A periodic review can ask four straightforward questions:

  • Is the person or partner still responsible for this work?
  • Is the scope limited to the accounts they need?
  • Are the granted actions appropriate to the current role?
  • Does any automation depend on access that belongs to an individual?

Record the decision and owner rather than simply marking the list reviewed. An unexplained permission should have a next action.

Keep an operational handoff

Document where campaign approvals, exports, billing contacts, and active incidents are owned after the change. Check the next scheduled execution of any transferred job.

The incident-response guide is useful if the review discovers unexpected activity or a broken dependency.

A completed access review leaves a clear result: unnecessary authority is removed, required work has an accountable owner, and the next report or campaign change does not depend on someone who has already left.

AdOpsNow Editorial

Examples use illustrative data. See our editorial standards or report a correction.