All docs
How it works

Google permissions: what Agent Planners asks for and why

TL;DR

Agent Planners connects each Google product separately and asks only for what its tools use. User management on Google Analytics and Tag Manager is part of each connect for every workspace, and every access change waits for an admin. Permissions that no Google API method uses, or that a permission we already hold covers, are not requested.

How we decide what to ask for

  • One connection per product. Google Ads, Google Analytics, Tag Manager, Search Console and the others each ask for their own permissions when you connect them.
  • Only what a tool uses. Every permission is tied to the tools that call it — read from each Google API's own documentation, not assumed.
  • The narrowest one that works. Where a read-only permission is enough we ask for that; a broader one only where a change needs it, and changes wait for your approval by default.
  • New permissions start as a pilot. A permission Google has not verified for us yet is offered only to our own workspace, so every other workspace keeps exactly today's consent screen.
The full list, per product, with Google's own wording and what we do with the data: Privacy policy — Google user data.

User management on Google Analytics and Tag Manager

  • Listing who has access is a read.
  • Every change — giving someone access, changing a role, removing someone — waits for an admin of your workspace, on every path (tasks, schedules, MCP, the REST API). Auto-approve does not cover it.
  • Never: granting the administrator role, changing or removing an administrator, removing the last administrator, or touching the Google login the connection itself uses.
PermissionWhat it lets the agent doTools
analytics.manage.users (Google Analytics Admin API)The only scope the Admin API accepts for properties.accessBindings create / patch / delete (v1alpha). analytics.edit does not cover access bindings.ga4.list_access_bindings, ga4.create_access_binding, ga4.update_access_binding, ga4.delete_access_binding
tagmanager.manage.users (Tag Manager API)accounts.user_permissions list / create / update / delete accept only this scope; the edit / publish scopes we hold do not cover user permissions.gtm.list_user_permissions, gtm.create_user_permission, gtm.update_user_permission, gtm.delete_user_permission
Available to every workspace since 18 November 2026, and part of the Google Analytics and Tag Manager connect since 19 November 2026: whoever connects or Re-authorizes the product (an admin or editor) grants it on Google's consent screen. A connection authorized before then gets it with its next Re-authorize; until then the card says so and the tools answer that the connection does not hold it.

A partner link lets a data partner (a CRM or customer-data platform registered with Google) upload customer data into your Google Ads account. The agent can list your account's partner links, and link or unlink a partner only after an admin approves. It uses the Data Manager permission your Google Ads connection already has when Customer Match uploads are turned on — no new permission.

PermissionWhy we do not request it
admob.report (AdMob API)Redundant: every AdMob method that accepts admob.report (accounts get / list, network / mediation / campaign reports, adSources list) also accepts admob.readonly, which the AdMob connect already requests.
datamanager.partnerlink (Data Manager API)Redundant: its three methods (partnerLinks search / create / delete) also accept datamanager, which Google already approved and the Google Ads Data Manager connect requests. The partner-link capability is built on datamanager (google_ads.*_partner_link, an RZ-only pilot) — measured live 2026-11-14: partnerLinks:search answered 200 with the datamanager grant.
analytics.partner.edit (Google Analytics Admin API)No method in the public Admin API (v1alpha or v1beta) lists it, and it is not on Google's OAuth scopes page — nothing the application can call uses it, so it cannot be demonstrated for verification. The Google Ads / DV360 / SA360 links the Admin API offers use analytics.edit, which we hold.
admob.googlebidding.readwrite (AdMob API)No method in the public AdMob API (v1 or v1beta) lists it; not on Google's OAuth scopes page. Mediation and bidding setup the application offers use admob.monetization.
adsdartsearch (Search Ads 360 API)Neither the Search Ads 360 Reporting API (searchads360 v0) nor the legacy DoubleClick Search API (v2) lists it; both use doubleclicksearch, which the SA360 connect already requests.
youtube.download (YouTube Data API v3)No YouTube Data API v3 method lists it and the API serves no video files; YouTube's terms forbid downloading outside YouTube's own features. Not used: a person downloads their own video from YouTube Studio and uploads it to the Asset Library.
Checked on 14 November 2026 against each API's published method list and Google's OAuth scopes page.

Frequently asked questions

Why does the consent screen ask to manage users?
So the agent can list who has access to your Google Analytics property or Tag Manager account and propose access changes. Nothing changes until an admin of your workspace approves that exact change, and the agent never grants the administrator role or touches administrators or the connection's own login.
Can the agent make someone an administrator?
No. The administrator role is never granted by the agent, administrators are never changed or removed, and every access change waits for an admin of your workspace.
Do I need to re-authorize after a new permission is added?
Only to use the feature that needs it. A connection keeps the permissions it was granted; the card says when a Re-authorize would add one.

Related