A quota is a configurable or allocated limit on the amount of a resource you can use, such as daily agent creations or queries. For seat-based subscriptions, quotas are automatically adjusted based on the number of licenses your organization purchases. A limit is a system constraint or capacity threshold, such as subagent depth, file upload size, or the number of individuals an agent can be shared with. System limits are fixed constraints, unless explicitly noted as an adjustable administrative setting.
For information on overall Gemini Enterprise quotas, pooling across editions, and overage pricing, see Quotas and overages.
Feature and edition-based quotas
Creating and running agents in Workflow Builder depends on your Gemini Enterprise edition.
Daily creation quotas
Creating and drafting agents consumes a daily creation quota allocated by edition. Daily creation quotas are pooled across all users with licenses for that edition within a specific project and location, and reset daily at midnight Pacific Time (PT).
| Edition | Daily creation quota | Description |
|---|---|---|
| Frontline Worker / Starter | 0 | Cannot create custom agents in Workflow Builder. Users can only run agents shared with them. |
| Standard | 1 agent per user per day (pooled) | Pooled across all Standard edition licensed seats in the project and location. For example, 100 licenses provide 100 creation operations per day for the organization. |
| Plus | 10 agents per user per day (pooled) | Pooled across all Plus edition licensed seats in the project and location. For example, 100 licenses provide 1,000 creation operations per day for the organization. |
| Pay-as-you-go | Unlimited | No daily creation limits. Usage is billed according to underlying resource consumption and query volume. |
For more information about how quotas are pooled, calculated, and billed for overages across editions, see Quotas and overages.
Agent capacity limits
The following limits govern the number of active agents that can exist in an application instance:
| Resource | Default limit | Scope | Description |
|---|---|---|---|
| Agents per user | 1,000 | Per user account | The maximum number of agents that a single user can create and own. |
| Agents per application instance | 10,000 | Per application instance | The total maximum number of agents that can exist across all users within an application instance. |
Sharing limits
When sharing an agent with colleagues in your organization, the following limits apply:
| Setting | Limit | Description |
|---|---|---|
| Maximum individual members per agent | 1,500 individual accounts | The maximum number of individual user accounts that can be added directly to an agent's access list. Enforced by Google Cloud IAM allow policies. |
| Google Groups support | Unlimited total members (1 group = 1 policy member) | Sharing with a Google Group counts as a single member toward the 1,500-member policy limit. |
Sharing limit error behavior
If you attempt to share an agent with more than 1,500 individual user accounts, the operation fails and returns the following error:
The number of members in the policy (1,501) is larger than the maximum allowed size 1,500.
Best practices for sharing at scale
To share an agent with large audiences (such as team-wide, department-wide, or organization-wide distributions) without encountering the 1,500-member IAM limit:
- Request that your app administrator enable group sharing in feature controls.
- In the agent sharing dialog, enter the email address of a Google Group or Workspace group (for example,
support-team@example.com) rather than individual user accounts. - Manage audience membership dynamically within the Google Group; all group members automatically inherit access without modifying the agent's IAM policy.
For step-by-step sharing instructions and permission levels, see Share a chat agent and Share a workflow agent.
Flow builder complexity limits
The flow builder canvas enforces structural and routing constraints to maintain low execution latency, ensure deterministic orchestration, and prevent circular call graphs:
| Constraint | Limit | Description |
|---|---|---|
| Subagent depth | 1 level | Single-level flow depth only. Subagents cannot call additional subagents. Nested multi-level hierarchies are not supported. |
| Subagents routed by chat root | 50 subagents | The maximum number of subagents that a single chat root agent can evaluate and route requests to. |
| Nodes per flow | 100 nodes | The maximum total number of nodes (including trigger, condition, action, subagent, and human-in-the-loop nodes) allowed in a single workflow. |
| Skills per node | 20 skills | The maximum number of tool skills or actions that can be attached to a single flow node. |
| Simultaneous subagent execution | 1 subagent at a time | Workflow executions evaluate and run subagents sequentially; parallel branch execution across multiple subagents is not supported. |
Knowledge base and file upload limits
The following limits apply to documents uploaded directly to an agent's knowledge base:
| Resource | Limit | Description |
|---|---|---|
| Maximum file size | 20 MB per file | The maximum size for an individual file uploaded directly to an agent's knowledge base. |
| Maximum files per agent | 100 files | The maximum total number of files that can be attached to a single agent. |
| Maximum files per upload batch | 10 files | The maximum number of files that can be selected and uploaded in a single operation. |
| Supported document types | PDF, DOCX, TXT, PPTX, CSV, XLSX, HTML, and Markdown (.md). | |
Storage capacity
Uploaded files and indexed documents consume storage from your organization's storage capacity pool. Storage is pooled across all users in a project and location, regardless of edition:
- Frontline Worker / Starter: 2 GiB per user.
- Standard: 30 GiB per user.
- Plus: 75 GiB per user.