AI Training · Google Workspace with Gemini
Google Workspace with Gemini Training for Companies
Gemini already sits inside Docs, Sheets, Slides, Gmail, Meet, and Drive, the tools your team has open all day anyway.
This training gives teams a repeatable way to draft, summarize, analyze, and communicate there. Source checks, approved-account rules, and a person's judgment get built into every workflow, not bolted on after.
- modules
- 6
- hours
- 13
Some of the 500+ brands we've worked with
Selected brands we’ve worked with across industries.
MeteksanGlobalCase Study
VisperaGlobalCase Study
Why this training
Why train on this tool?
Put the AI where your team already works: Docs, Sheets, Slides, Gmail, Meet, Drive. Gemini sits inside all of it, and that's the whole advantage over a separate chat window nobody remembers to open.
That proximity cuts both ways — a summary can look complete while skipping a caveat, and a number can look right until someone reopens the filtered range, so the safe habit is checking the file before the meeting rather than trusting approved accounts and Drive permissions alone. This two-day program builds that method across the whole Workspace stack, leaning on the prompting habits from our AI literacy and prompt engineering training, using your own environment and documents throughout; the rest of the tool family is indexed under AI training.
Google Workspace is already where the work happens
Briefs, budgets, decks, and meeting notes already move through Docs, Sheets, Slides, Gmail, Meet, and Drive — training Gemini inside that environment keeps it close to the document a team needs to finish.
A vague prompt gets a vague answer
Useful output depends on audience, source, objective, constraints, and format, and most people never write any of that down — training gives teams a repeatable way to supply that context without oversharing.
Speed isn't accuracy
A polished summary can still miss a qualification, and a confident analysis can misread a source — the habit that keeps Gemini safe is checking the result against the files and figures that matter.
What belongs in a prompt, and what doesn't?
An approved company account doesn't make every piece of information appropriate for every prompt — staff need plain daily rules for personal data, confidential material, and when to use a synthetic example instead.
Write it down so the next person can use it
One good prompt in one person's head changes nothing for the company around them — shared examples, review standards, and named owners let a team reuse what works.
Syllabus
Training syllabus
Google Workspace with Gemini foundations
90 minBeginner
A practical map of where Gemini fits across Google Workspace, and where a person's judgment stays essential no matter which interface ships next. Participants leave with a shared vocabulary that doesn't depend on a particular edition or feature.
- Where Gemini actually helps
- Drafting, summarizing, analyzing, and transforming as task types
- Where generative AI is strong, and where it isn't
- Delegate this, keep that
- A low-risk first workflow
Prompting with real work context
120 minBeginner
A reusable method built around objective, audience, source, task, constraints, format, and checks. Participants shape a vague ask as a grounded instruction that uses approved context. The result is a first draft someone can review.
- A repeatable context-task-format-check structure
- Naming the audience, objective, tone, and success criteria
- Pointing to approved sources without copying unneeded data
- Asking for alternatives and missing assumptions
- Rewriting a draft twice before calling it done
- Building a shared prompt library from approved examples
Docs, Slides, and Drive workflows
150 minIntermediate
Document and presentation work from source review to the final human edit, with a visible link back to Drive at every step.
- Drafting a document from a brief and a source set
- Summarizing long material without losing key decisions
- Rewriting for a different audience or tone
- Turning a reviewed doc into a slide outline
- Using Drive permissions as part of the workflow
- Checking claims against source files before anyone sees them
Sheets and Gmail workflows, with Meet follow-up
150 minIntermediate
Support for reading data, writing email, and following up on meetings, applied directly to Sheets, Gmail, and Meet. Participants use Gemini to frame questions, explain patterns, draft replies, and turn a discussion into actions. Then they check the figures and owners. Deadlines get checked before anyone trusts the output too.
- Framing a question before touching spreadsheet data
- Explaining patterns and tables in plain terms
- Checking calculations and source ranges independently
- Drafting Gmail replies from approved context
- Turning meeting notes into actions and owners
- Keeping the AI's read separate from the evidence
Approved accounts and KVKK-compliant data boundaries
120 minIntermediate
Company policy translated into choices people make while working: which account to use, what data belongs in a prompt, and when a workflow needs an escalation.
- Approved versus unsanctioned tools
- KVKK duties when a prompt holds personal data
- Where confidential and client information stops
- Drive permissions and what "accessible" doesn't mean
- Reducing or synthesizing context for safer practice
- When to escalate, and what to write down
Team norms for adoption and workflow rollout
150 minAdvanced
Moving from individual experiments to a habit the whole team keeps. Participants pick a pilot, set a review standard, name an owner, and leave with a rollout plan scoped to a normal quarter.
- Picking a pilot workflow with a named owner
- Defining what a good output looks like, before measuring anything
- Team rules for source checks and sign-off
- Keeping a prompt library alive after the workshop
- Coaching without creating an unsupervised shadow process
- A 90-day plan for Workspace adoption
Outcomes
Outcomes & audience
What you will learn
- Draft and summarize. Analyze inside the Workspace tools you already use
- Write prompts with useful context
- Keep a Docs or Slides workflow traceable to its source
- Check figures before trusting them
- Turn meeting notes into owners and a deadline
- Know the KVKK rule before pasting
- A checklist for verifying a claim before it ships
- Prompts and norms the team keeps after the rollout
Who should attend
- Operations and project teams whose day already runs through Workspace
- Marketing and sales, including communications staff
- Finance and people teams, including admin functions
- Whoever owns Gemini adoption for their department
- IT, security, privacy, and Workspace admins
- L&D and enablement, including digital-transformation leads
Format
Training format
This runs as a two-day program, and most teams split it into half-day blocks so the calendar survives. Onsite or live online covers the same syllabus, built around your Workspace environment, sample files, and existing team rules.
- Format
- Onsite or live online
- Duration
- 2 days (about 13 hours, can be split into half-day sessions)
- Group size
- Up to 20 participants per group
- Language
- English or Turkish
- Materials
- Prompt library, workflow templates, source-check checklist, and exercise workbook
- Certificate
- Certificate of completion
Keep exploring
Related programs
Next step
Plan a Gemini rollout for your Workspace teams
Questions
Frequently asked questions
Who ends up in a Google Workspace with Gemini session?
Anyone whose day already runs through Docs, Sheets, Slides, Gmail, Meet, or Drive: operations, marketing, sales, finance, people, admin, managers, and internal enablement teams. Cohorts can be grouped by function so exercises match each team's own documents and decisions.
Do we need any coding background to join?
Coding or data-science experience isn't a requirement here, just a working familiarity with the Workspace apps your team already uses day to day.
Which Workspace apps does the course touch?
The syllabus runs on current workflows across Docs, Sheets, Slides, Gmail, Meet, and Drive: drafting, summarizing, analyzing, checking, and collaborating. We don't promise a specific menu item or interface, because those change between Workspace editions and over time.
What if Gemini isn't turned on for everyone yet?
Hands-on practice works best on an approved company account with access your organization has already configured. Where access is uneven or still under review, we run the same session with facilitator demonstrations and shared exercises instead of asking anyone to log in on a personal account.
How does this compare to Copilot training for Microsoft 365?
This program is built around Docs, Sheets, Slides, Gmail, Meet, and Drive. The Copilot program covers Word, Excel, PowerPoint, Outlook, and Teams instead. Good prompting and verification habits carry over between the two, but the source context, collaboration patterns, and daily workflows don't.
What happens to KVKK-covered data during the sessions?
Exercises run on approved non-sensitive material or reduced examples. Synthetic data needs your team's sign-off beforehand. We set clear rules for personal and confidential information before anyone opens a laptop. Approved company accounts stay separate from unsanctioned tools throughout, and participants practice checking permissions and escalating a doubtful case rather than guessing. None of this replaces your own legal advice. It gives the team a working default for daily use.
Can you adapt the syllabus to how our team works?
Before the first session we map your teams, environment, sample workflows, and data rules, then fold that into the exercises. The core stays the same: prompting with specific context, Workspace workflows, source checks, safe data handling, and adoption.
What do people walk away with?
A prompt library, workflow templates, a source-check list, draft team norms, and an adoption plan built around Workspace principles rather than one feature release. Update the details as Gemini's capabilities change. The underlying method holds.