Gemini 4 Argon in Workflow Builder: Admin Controls Before October 27

Argon is generally available. Why might it still be missing?

Google Cloud's October 14, 2026 release note makes Gemini 4 Argon generally available in Gemini Enterprise Workflow Builder and available in its workflow agents. General availability, or GA, describes the model's status in this product. This update does not announce Workflow Builder itself as a newly launched product.

Workflow Builder is a no-code, low-code tool in the enterprise web app. Natural-language prompts or a visual editor can create chat agents and workflows that run a sequence of steps. Workflows can combine AI processing, conditional logic and human intervention for processes with a defined order.

Availability does not establish that your organization has enabled it. Argon is currently off by default in the app, and Google says updates can take up to a day to appear in workflow agents. Check the administrator's settings and the applicable location before relying on the state shown in an agent.

Where admins should look: three controls with different jobs

First, confirm that the person making changes has the Gemini Enterprise Admin IAM role, roles/discoveryengine.agentspaceAdmin, and that an existing Gemini Enterprise web app is available. An IAM role controls who can manage cloud resources. End users should consult their organization's administrator; a personal Gemini subscription does not establish administrative access.

In Google Cloud console, open Gemini Enterprise, click the intended app's name, then open Configurations and the Feature Management tab. Confirm the app name so that settings in a separate pilot app are not mistaken for the team's production environment.

Check Enable workflows and Enable model selector as needed. The first lets users create and run custom workflows; the second lets users choose models in the web app. Allowing model selection does not by itself allow Argon.

Under Model availability, inspect the Gemini 4 Argon toggle. Google's documented enablement action is to set that toggle to on. Record the actual choice and app location, then inspect the relevant workflow agent for the update. No organization settings were changed for this article.

What changes on October 27? A default is not a completed migration

Argon is currently off by default in the global, us and eu regions. Google says the toggle defaults to on beginning October 27, 2026. It does not provide an exact time or timezone, so the date should not be converted into an assumed midnight deadline elsewhere.

The announcement and settings page do not say whether this default change overrides an administrator's explicitly saved off setting. Organizations that need to restrict model access should record the current configuration, confirm the applicable controls and inspect the resulting state after the change. The published default does not settle how every saved policy behaves.

Model availability and workflow propagation also need separate checks. Google says updates can take up to a day to appear in workflow agents. It does not guarantee an immediate switch in every published workflow, successful task execution, or a fixed propagation time after an admin action. Keep the app, location, configuration time and visible agent state when investigating a problem.

Which locations apply? Global routing is not in-country processing

The release note lists the global, us and eu multi-regions, with data residency and machine learning processing support in us and eu. Data residency concerns where data is stored; machine learning processing concerns where model processing occurs. These commitments are separate from the country where a user happens to be located.

The location documentation says the CA, IN, JP, SG and UK in-country regions do not offer Argon. In an unsupported in-country region, confirming the warning routes traffic to the global endpoint. That does not keep processing in the original country or demonstrate compliance with an organization's local-processing requirements.

For example, a team requiring storage and processing in the European Union should check the app's eu location and each relevant feature's support and limitations. An office address in Europe does not establish either commitment. This hypothetical example was not executed; organizations with location requirements should select models and regions permitted by their own policies.

Evaluate one small workflow, then check permissions and costs

Choose a small workflow that uses authorized material and produces a result a person can check. One hypothetical example is drafting a status summary from approved project records, with a human review before it is sent. Check inputs, steps, output and stop conditions before extending the workflow or allowing it to change external systems. No such workflow was run for this article.

Workflow Builder lets non-admin users build and deploy agents, but administrators still provision the available data connectors, tools and permissions. Enabling Argon does not automatically grant access to more company data or enable agent sharing. Model availability, data permissions and sharing controls require separate decisions.

The release note and operational pages reviewed here do not provide a complete Argon workflow entitlement, execution-quota or price table. Do not apply personal Pro or Ultra subscription benefits, or public Gemini API token rates, directly to enterprise workflows. Confirm your organization's licenses and billing terms before running them. For consumer-app or API access, see the published Argon access guide in Sources.