Leadership1 publisher2 min readPublished
Google routes Gemini's background drafting through the sources an admin has enabled
Gemini can now be prompted from Gmail, Drive, Docs, Slides and Chat to assemble a deck or a spreadsheet in the background. Google's own post says twice that the sources it reads depend on the user's picks or the admin's.
The Board Room · Leadership desk
What happened
- Google says Gemini can now be prompted to run complex cross-app tasks from inside Gmail, Drive, Docs, Slides and Chat, generating formatted Docs, structured Sheets or stylized Slides.
- In the Chat example, Gemini works in the background across active projects, Chat conversations, the Gmail inbox and action items, then hands back a direct link to a finished multi-slide deck.
- Prompted in Gmail, Gemini turns a long thread into a structured Doc, connecting the active thread with related Drive files, emails and chats through Workspace Intelligence.
- The announcement is a Google Workspace blog post by product manager Jill Daley, setting out five agentic capabilities.
Compiled by The Board RoomSomething wrong?How this is made
Why it matters
- constraint Source enablement is the only limit the post names on what these agents read, so an AI policy that is never expressed as an enabled or disabled source leaves the drafting untouched.
- decision Whoever administers Workspace decides which corpora an agent may traverse on a colleague's prompt. That list needs a named owner and a review interval.
- exposure The person who opens a background-generated draft is signing off on material assembled from sources an administrator chose for them.
- capability A Chat message can now yield a leadership deck without its author opening Slides. The human contribution shifts from assembly to checking.
Google's post states the scope of what Gemini reads twice, and both times in the same construction. Gemini gathers real-time context from relevant files, emails and chat threads "depending on which sources you select (or your admin has enabled)" [3]. The second appearance is in the Docs flow, where a drafted email pulls project information "from sources that you have selected or your admin has enabled" [7]. In both passages the user and the administrator appear as alternatives inside the same clause [11].
The four flows described share a shape: the prompt is issued in one app and the artifact lands in another [12]. A prompt in Drive returns a structured spreadsheet built from the open folder plus other sources the user chooses, including material costs and sustainability metrics [6]. In Docs, the output is a Gmail draft that can be sent without leaving the document [7].
Jill Daley, a product manager for Google Workspace, wrote that "Under your direction, Gemini works in the background to help you get things done, like securely creating the first draft of a document in Google Drive for you to review" [4][9]. The order in that sentence puts creation before review. She also wrote that "Gemini works as an intelligent orchestrator, generating formatted Docs, structured Sheets, or stylized Slides under your direction while you stay focused on your current task" [2].
The product copy is specific about what governs the reading: selection determines what the agent reads, and the administrator is one of the two parties doing the selecting [3][7]. Drafting respects a rule only once that rule shows up as an enabled or disabled source. The two passages that condition Gemini's sources on admin enablement do not say where that setting lives or what it defaults to [13].
The choice in front of an operator this quarter is narrow. Someone has to own the enabled source list, and someone has to decide how often it is looked at, because those settings are what the drafting respects [3]. The version of the question that arrives later is harder, because by then the artifacts are already in Drive and the person reviewing a deck is judging material gathered from a corpus someone else chose [4].
The feature set is still growing. Google says Gemini may ask clarifying questions in the Chat presentation flow, and that this is "coming soon to all of the places where you can create presentations in Workspace" [10].
What to watch
- Whether Google publishes admin documentation naming the source-enablement controls, their defaults and the Workspace editions covered.
- Whether artifacts generated in the background record which files, mail and chats fed them, so a reviewer can check provenance.
- Whether admins get per-source or per-app granularity, or a single Gemini on-off switch for the whole domain.