# An access request is not access: prepare your Google Ads handoff for December.

A clear agency handoff plan for the announced multi-party approval changes, without sharing passwords or treating a pending request as complete.

By AdzUp Editorial | 2026-11-18

## Know which workflow the announcement concerns.

Google’s 4 November 2026 announcement schedules changes to Google Ads API multi-party approvals for the week of 7 December. When an approval is required for an access invitation, creation of the invitation resource will be deferred until approval. The post also describes handling for stale requests. This concerns integrations using the affected approval workflows; it is not a statement that every manual account invitation behaves identically.

For a business appointing an agency, the useful question is who owns each step between “requested” and “ready to work”. A technical success response, a pending approval and usable access are different states. The following handoff approach is AdzUp’s operational interpretation of that distinction.



## Define ownership before the launch deadline.

In an illustrative manufacturing company, the marketer may request agency access while the owner or an internal administrator holds approval responsibility. If the campaign launch assumes the agency is already connected, a pending request can become a last-minute scramble. Identify the approver and a backup contact before committing to a delivery schedule.

Agree the account involved, the business purpose and the intended permission level. Use the platform’s authorised access process rather than exchanging a shared password. This is an ownership decision as well as a technical task: the business should know who can act for it and how that relationship will be reviewed when work ends.

- Record requested, awaiting approval, approved and verified access as separate handoff states.
- Name the person who reviews exceptions or a request that is no longer valid.
- Keep account ownership and removal of access in the project handover.

## Ask the integration owner to expose pending states.

An onboarding tool should tell the operator what remains outstanding. Ask whether it can show the difference between a deferred invitation, an approval outcome and a request invalidated by another change. A business-facing screen should not claim “connected” solely because the first request was submitted.

Use a controlled test plan for the affected workflow and the current API version. The technical team should follow the official release guidance for handling responses and changed errors. The client-facing acceptance check is simpler: can the intended person perform the agreed task in the intended account, with the expected permission boundary?



## Make the handover evidence small and useful.

A concise handover record can identify the account, authorised participants, verified scope, confirmation date and person responsible for later access reviews. It should not contain passwords, authentication tokens or screenshots exposing unrelated customer information. Keep operational evidence proportionate to the task.

Finally, allow for an honest pending state in the project schedule. Approval processes exist to support controlled access; bypassing them to meet an arbitrary launch time creates a different problem. If access is not verified, report that dependency clearly and continue preparation that does not require it.



## Sources

- [Google, 4 November 2026: Upcoming multi-party approval changes](https://developers.google.com/ads/blog/posts/2026/11/upcoming-changes-to-multi-party)
