InsightsGemini Enterprise
Your first teams can be working in Gemini Enterprise by day ten
The setup order, connectors, guardrails, two workflows of your own and champion training that get your first teams working in Gemini Enterprise.
- Written by
- CloudMagic engineering team
- Published
- Reading time
- 13 minutes
The short answer
Your first teams can be working in Gemini Enterprise on day ten when the location, encryption, network perimeter and identity decisions are made and your administrators are booked before day one. Week one sets those controls first, connects two or three of your document sources, switches on Model Armor and gets ten people using it. Week two builds two of your own workflows in Workflow Builder, each with a person's approval step, trains your champions and ends with a go or no-go for wider rollout.
We call this offer Two-Week Activation. It is for a company that has bought Gemini Enterprise seats, or is about to, and wants people using them. In ten working days our engineers set it up with your administrators, connect two or three of your document sources, turn on the guardrails, build two of your own workflows with a person's approval step in each, and train the colleagues who will teach everyone else. Product details were checked against Google's documentation on November 14, 2026.
All of it is configuration inside Gemini Enterprise: connectors, Model Armor, Deep Research, Gemini Notebook for business, skills and Workflow Builder. Workflows that need custom code, such as an agent built with the Agent Development Kit, a custom connector or a write-back into a system of record, follow our 30-day plan for one workflow instead.
The two weeks count from the day the four setup decisions are made and your administrators' time is booked. A build team cannot speed those up, so we work through them with you on a free one-hour readiness call before day one.
What has to be true before day one?
Everything below is settled on the readiness call. During the two weeks, one named sponsor on your side answers setup and access questions within one business day.
- Standard or Plus seats bought, or a trial started, in the project and location the app will use.
- The location chosen, and a yes or no on customer-managed encryption keys (CMEK) and on VPC Service Controls.
- The identity provider chosen.
- Consent sessions booked for day 1 with your Google Workspace administrator, or with the administrators of your identity provider and office suite.
- Access to the project for our engineers.
- Two workflows named, each with an owner who will approve what it drafts.
- About ten first users, and the people you want as champions.
Across the ten working days, plan on about four hours from your Google Cloud administrator and two from your identity administrator, mostly on days 1 and 2; an hour a day in week two from each workflow owner; and your champions for two training sessions. If one of your first workflows is contract review or HR policy answers, our two-week plans for a legal first pass and HR answers cover it in detail.
Google's in-country regions need an allowlist from your Google account team. If you need one, the two weeks start after it is granted.
What happens week by week?
Days 1 and 2 set the controls, days 3 to 5 put the app in front of ten people, and week two adds your workflows and trains your champions.
| When | What happens | Who we need from you | What exists at the end |
|---|---|---|---|
| Before day 1 | Readiness call; decisions written down; consents and access booked | Sponsor, admins, workflow owners | A plan with scope, go-live gates and a fee |
| Days 1 and 2 | CMEK key, VPC Service Controls tested and enforced, identity provider, consents, roles | Google Cloud, identity and security admins | A project that is safe to build in |
| Days 3 to 5 | App, Model Armor, logging decision, two or three connectors, permission test, first users | Admins, a test user, ten first users | Gemini Enterprise live for ten people on your documents |
| Week 2 | Two workflows with approval steps; starter skills; champions trained; go or no-go | Workflow owners, champions | Two workflows in use, a design document, a runbook |
| Weeks 3 and 4, optional | Company-wide sessions; welcome emails and FAQs; adoption check-ins | Champions, internal communications | Every session recorded; adoption tracked |
What happens in week one?
Week one ends with your first ten people using Gemini Enterprise on your own documents, with the guardrails already on.
Days 1 and 2 are an admin session with your Google Cloud, identity and security administrators. If you chose them, the encryption key is registered and a VPC Service Controls perimeter is tested in dry run and then enforced before any app or data store exists, because Google does not support adding existing data stores to a perimeter without recreating them. Then come the identity provider, the consents for each data source, and the Gemini Enterprise Admin and User roles.
On days 3 to 5 we create the app and attach a Model Armor template, which every Gemini Enterprise edition includes at no additional cost. Model Armor does not mask personal data by itself, but Gemini Enterprise blocks any assistant response that triggers a Sensitive Data Protection detector, so we choose the detectors with you. Our post on stopping instructions hidden in documents covers what screening catches and what it misses.
Whether prompts and responses are written to the audit logs is a setting; with it off, the logs record the activity without the text. Logged prompts hold whatever people typed, so your security and records owners make that call and we write it down.
Then we connect two or three of your sources, all on connectors Google lists as generally available. Workflow Builder supports a shorter list of sources than search does: Google Drive, Gmail, Google Calendar and Google Chat, plus the third-party connectors listed on Google's Workflow Builder page. We check before day one that your two workflows use sources on that list. Federated search reads the source when someone asks, so nothing waits on indexing. Ingestion copies content into the Gemini Enterprise index for better search quality, and Google notes it may take several hours depending on data volume, so it is scoped to the sites or folders your first teams use and runs in parallel. Search is permission-aware, and we check it: a test user who should not see a test document searches for it and must not find it. Our post on keeping protected records out of an agent's reach covers the stricter version for regulated data.
The model toggles get set to your policy the same day: Gemini 4 Argon has defaulted to on since October 27, 2026, and Gemini 4 Carbon and Gemini 4 Hydrogen arrived turned off, so an administrator checks each one instead of trusting the defaults. Deep Research, Gemini Notebook for business (formerly NotebookLM Enterprise) and Projects go on. We record the starting active-user count, run an admin workshop for your team on app and connector setup, agent administration and usage monitoring, and the first ten users start.
What happens in week two?
Week two builds two of your own workflows, gives people a starter set of skills, and trains the champions who will carry the rollout.
The workflows are built in Workflow Builder (formerly Agent Designer), generally available since September 3, 2026, from processes your teams named before day one. Workflow Builder supports review, approval and information-request steps, and Google's documentation says adding or updating data through connectors requires human review. The workflow gathers and drafts, and a named person approves before anything goes out.
Here is one workflow in full, for Larrow Market, the made-up grocery chain from our demos. The company, the folders and the figures are invented to show the shape of a week-two build.
| Step in Workflow Builder | What it does | What it touches |
|---|---|---|
| 1. Trigger | The store operations lead types @ and the workflow's name in chat on Friday afternoon | Gemini Enterprise chat |
| 2. Gather | Reads the files changed in the last 7 days in the store rollout Drive folder and the messages in the rollout Chat space, under the lead's own permissions | Google Drive, Google Chat |
| 3. Draft | Writes a four-line status note: milestones done, blockers with the file each comes from, decisions needed next week, dates that moved | Instructions stored in the workflow |
| 4. Approval | Stops and shows the lead the draft: "Done: refrigeration sign-off at Depot 3 (Depot 3 inspection). Blocker: permit delay at Store 19 (permit log). Decision needed: weekend overtime for the Store 19 install. Moved: Store 19 opening, from March 3 to March 10." | The named lead; nothing moves until the lead approves or edits |
| 5. Post | Posts the approved note to the leadership Chat space | Google Chat |
The second workflow follows the same shape with a different owner and its own approval step.
Skills are reusable instructions for a single task in chat, called with an @ or / mention, such as rewriting a rough customer note in your house style or turning meeting notes into an action table. Administrators turn on skills and skill sharing, and we write a starter set for the single tasks your first users repeat most. Google notes that skills are not available for use with agents, so a one-step rewrite belongs in a skill and a job that reads folders and waits for approval belongs in Workflow Builder.
Your champions get two train-the-trainer sessions, and the first end-user sessions run with them in the room. We write the Technical Design Document and the runbook. On day 10 you decide whether to roll out wider, against the gates written before day 1. This is the day-10 checklist, and every row needs a yes:
| Gate | Pass mark | Where the evidence sits |
|---|---|---|
| Controls before data | If you chose them, the key was registered and the perimeter enforced before the app or any data store was created | Creation dates from the console, copied into the design document |
| Permission test | A test user who should not see the test document found nothing, on every connector | One screenshot per connector, kept with the runbook |
| Guardrails | Model Armor template attached; detectors listed and signed off by security | The design document |
| Logging decision | Prompt logging on or off, who decided, and who can read the logs | The runbook |
| Workflow 1 and workflow 2 | Each owner approved its drafts on ten real examples, and no draft went anywhere without them | The owner's written sign-off and the saved workflow version |
| Model toggles | Each Gemini 4 model on or off as your policy says | The console, checked on day 10 |
| People | Ten first users active in the usage figures, which Google refreshes about every 6 hours, so we read them on the morning of day 10; each champion has run one session | The analytics baseline and the session recordings |
A failed row means no wider rollout that day and a written list of what failed. For agents that need a full answer key and repeated scored runs, our testing method describes how we do it.
Why does the setup order matter?
Location, encryption keys, network perimeter and identity provider are cheap to decide on day one and expensive to change afterwards.
| Decision | What Google's documentation says |
|---|---|
| Location | Licenses belong to a project and a location. Google recommends global unless you have a security or regulatory reason for the US or EU multi-region, and CMEK and Access Transparency need the US or EU multi-region. The location is chosen when the app is created, and Google's documentation describes no way to move it afterwards. |
| Encryption keys | CMEK applies only after the key is registered. Any app or data connector created before that stays unprotected. |
| Network perimeter | With VPC Service Controls on, new data stores are blocked until an administrator adds their data sources and egress domains to the managed organization policy constraints. Google recommends dry run mode first. |
| Identity provider | If you change identity providers, users lose their existing chat history. |
So the encryption key decision comes first, because it settles the location. The key and perimeter go in before any connector, and the identity provider should be one you will keep.
Which edition do you need?
Standard or Plus. The editions keep the name Gemini Enterprise, as do the docs and contracts, although Google's product page now says "Gemini for enterprise".
The Business edition, for up to 500 users, is managed without the Google Cloud console, and Google's edition table does not give it the full connector set or the enterprise-grade security and compliance features. This plan depends on both.
Between Standard and Plus, the rollout difference is the daily allowance per license, pooled across your users. Plus gives 10 Deep Research reports a day per license against 3 on Standard, 200 assistant queries against 160, and 75 GiB of storage and indexing per user against 30.
Frontline is for staff who work away from a desk. It needs 150 or more Standard or Plus users, and Frontline users can only use agents an administrator has provisioned for them.
Do we need Google Workspace, or can we keep our identity provider and office suite?
You do not need Google Workspace. Google Identity is Google's recommended identity provider, and a third-party provider that supports OIDC or SAML 2.0 works through Workforce Identity Federation.
If your files, mail and chat live outside Google, Gemini Enterprise reaches them through connectors, and the widely used ones are on Google's generally available list. One rule catches teams out. For some office-suite sources, Google's identity page says that connecting them by ingestion requires that suite's own identity service through Workforce Identity Federation, even when another provider handles sign-in. The same sources connected by federation carry no such rule. We settle each source's path before day one. On Google Workspace, the day 1 consent is your Workspace administrator turning on Gemini Enterprise's access to Workspace data and the smart features settings, and allowlisting Google's app if your organization restricts OAuth apps.
What happens after two weeks, when you want every licensed employee using it?
We add weeks 3 and 4 to the same agreement and run the company-wide training with your champions.
Those weeks hold hour-long sessions for end users on Gemini Enterprise and your two workflows, sessions on the agent features, and two builder workshops: no-code agents in Workflow Builder for anyone, and the Agent Development Kit for your technical staff. Every session is recorded for you to keep. We draft the welcome emails and the FAQ your communications team sends, and each week we review active users with you against the target set on day 1. Your champions lead the sessions for their own departments, with us beside them.
What do you own at the end?
Everything, in your own Google Cloud project from the first day: the app and its configuration, the connectors, the Model Armor template, the two workflows with their version history, the skills, the Technical Design Document, the runbook, the training material and recordings, and the analytics baseline.
After that the choice is yours. We stay to run and improve it, or your team takes it over with the runbook. If you want the two workflows checked against real examples every month and before any planned change, we offer that as Agent Quality, on a 6 or 12 month term.
When do we tell a client not to start?
When the two weeks would end in rework or with nobody using it. The usual reasons, which we raise on the readiness call:
- You are on the Business edition.
- One of the four setup decisions is still open, or a change of identity provider is planned in the next few months.
- You need an in-country region and the allowlist has not been granted.
- Nobody can make setup decisions within a business day, or the workflows have no owner.
- The permission test shows documents open to far more people than should see them, and the sharing needs fixing first.
- The workflows your teams named need custom code, or depend on something Google marks preview, such as most third-party connectors and the Agent Marketplace. Nothing on the critical path of the two weeks is in preview, so those become a second phase.
Frequently asked questions
Can we run the two weeks on a free trial?
Yes. Google offers Gemini Enterprise Plus at no cost for 30 days, and the two weeks fit inside that. Start the trial in the project and location you intend to keep, because licenses belong to both. Google's license notes say trial subscriptions exclude AI developer tools (the coding tools for your developers, not Workflow Builder) unless the project is on an invoiced billing account, which matters only for the developer workshop.
What does it cost?
The statement of work is already written: scope, gates and exclusions are fixed, weeks 3 and 4 are an option, and you sign it after the free readiness call. The two weeks are a fixed fee. Ask us whether Google funding applies to your project. The readiness call is booked through our contact page.
Does Google train its models on our prompts or documents?
No. Google's security documentation says Gemini Enterprise does not use your prompts, generated responses or connected enterprise data, whether ingested or reached through federated search, to train Google's foundation models.
Sources
- Gemini Enterprise licenses, Google Cloud
- Gemini Enterprise locations, Google Cloud
- Customer-managed encryption keys, Google Cloud
- Use VPC Service Controls, Google Cloud
- Configure an identity provider, Google Cloud
- Gemini Enterprise editions, Google Cloud
- Quotas and pay-as-you-go usage, Google Cloud
- Introduction to connectors and data stores, Google Cloud
- Connect a third-party data source, Google Cloud
- Set up a document library data store (ingestion time), Google Cloud
- Set up a Google Drive data store, Google Cloud
- Enable Model Armor, Google Cloud
- Set up usage audit logs, Google Cloud
- Workflow Builder workflows, Google Cloud
- Create and manage skills, Google Cloud
- Gemini Enterprise security overview, Google Cloud
- Gemini Enterprise release notes, Google Cloud
- Gemini Enterprise product page (Plus trial), Google Cloud