A Conversational Agents agent calls tools as the Dialogflow service agent unless you pick a service account, and the project owner sees everything
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Conversational Agents (Dialogflow CX) calls tools and webhooks as the Dialogflow CX Service Agent, or as a service account you name. Google documents that the project owner has full access to every agent in the project and that sharing an agent adds the Dialogflow Reader role by default. Read 16 Nov 2026.
Two directions of access: who reaches the agent, and what the agent reaches
A Dialogflow CX agent has two access questions. Who may build, query or share the agent is an IAM question about people and applications. What the agent reaches when it calls a tool or webhook depends on the credential the tool uses. Google's access control page covers the first; the tool and webhook pages cover the second (Google Cloud: Dialogflow CX access control, read 16 Nov 2026). The Conversational Agents console is the newer interface that replaces the Dialogflow CX console.
Who can reach the agent by default
Google documents that the IAM Project Owner role is granted by default to the user who created the project that owns the agent, and that this owner has full access to all agents in the project. Agent sharing in the console adds agent roles, and the Dialogflow Reader role is added by default to a shared principal, which users need to open the Conversational Agents console. Setting agent roles in the console needs the Project IAM Admin role.
The agent roles are IAM roles with IAM conditions that limit them to one agent or part of it. Google lists Conversational Reader, Conversational Admin and Conversational Client, among others, mapping to Dialogflow API Reader, Admin and Client. A service account added to the project can call the agent from an application, which is the way to give an application detect-intent access without admin rights.
Which identity the agent's tools and webhooks use
| Option | What Google documents | What it reaches |
|---|---|---|
| Dialogflow CX Service Agent ID token | Dialogflow generates an ID token as the service agent, an address at gcp-sa-dialogflow.iam.gserviceaccount.com, and adds it to the Authorization header | Cloud Run and Cloud Run functions, after you grant roles/run.invoker or roles/cloudfunctions.invoker to the service agent; same-project services need no extra permission |
| Service account | Dialogflow generates an access token for a service account you create; you need roles/iam.serviceAccountUser, and the service agent needs roles/iam.serviceAccountTokenCreator | Any Google API the service account has roles for |
| API key | Key name, location and value are provided in the tool | The service the key opens |
| OAuth client credentials | Server-to-server; Google recommends storing the client secret in Secret Manager | The third-party API the client may call |
What the defaults imply
The service agent's own default permissions: none found on 16 Nov 2026 in the pages read. What Google documents is that the tool authenticates as the service agent only for Cloud Run and Cloud Run functions where you grant the invoker role, and that a service account tool is limited to the roles of that account. For webhooks, Google documents a priority order when several authentication options are enabled: authentication headers, basic auth, third-party OAuth, then service agent authentication (Google Cloud: Dialogflow CX webhooks). A webhook that carries a header credential will use it ahead of the service agent.
How to narrow it
- Use a dedicated service account per tool with only the roles that tool needs, and grant TokenCreator only on that account (check: a role per tool).
- Grant run.invoker on the single Cloud Run service, not the project (check: restrict tool invokers).
- Give people Conversational Reader or Client on one agent through the sharing tab, and keep Project Owner rare.
- Where service accounts cross projects, Google notes that the organization policy must support it; review the constraint (check: scope the trust).
- Compare the Gemini platforms on the Agent Runtime page and the Google Cloud page.
Related pages
Sources
- Google Cloud: Dialogflow CX access control, read 16 Nov 2026
- Google Cloud: Dialogflow CX tools, read 16 Nov 2026
- Google Cloud: Dialogflow CX webhooks, read 16 Nov 2026
Last reviewed 16 Nov 2026.