C
CertPilot

Offboarding recipe

Offboarding evidence capture (log the departure and notify the review owner)

When a departure form is submitted, log it to a tracking Sheet and notify the access-review owner. Records and notifies — it does not change any account.
StarterNot run by CertPilotVerified

“Verified” means checked against Google’s official Workspace Studio documentation — not that CertPilot has run this flow in a live Workspace.

Overview

What this recipe does

On each offboarding form submission: a timestamped row is added to the log and the review owner is notified. No account is modified.

Starter: When a form response comes in (your leaver/offboarding Google Form)

Build

Steps

  1. Log the departure to a tracking SheetSheetsUse the Sheets 'Add a row' step to record the leaver, their last day, and the systems to review — building a timestamped offboarding evidence log.
  2. Notify the access-review ownerChatUse the Chat 'Send a message' step to alert the person responsible for the access review that a leaver needs action.

Data

Variables

  • Leaver nameFrom the offboarding form response. (e.g. Sam Okafor)
  • Last dayFrom the offboarding form response. (e.g. 2026-09-15)
  • Systems to reviewFrom the offboarding form response. (e.g. Gmail, Jira, VPN)

Google Gemini

Describe it with AI

Paste this draft into Google Workspace Studio's Describe it with AI box, then review and adjust the flow it builds. This is Google's Gemini feature — CertPilot does not run any AI.

When a response is submitted to my offboarding form, add a row to my Offboarding Log sheet with the leaver's name, last day, and systems to review, then send me a Chat message so I can start the access review.

Before you start

Prerequisites

  • An eligible Google Workspace edition with Workspace Studio and Gemini enabled by your admin.
  • Access to Sheets and Chat (subject to your admin's Studio step controls).
  • An offboarding intake Google Form and an Offboarding Log spreadsheet.

Boundaries

Security & limitations

Security notes

  • The log may contain personal data (names, systems) — restrict who can view the spreadsheet.
  • Post to an existing Chat space you control; subject to your admin's Studio controls and DLP policy.

What it does not do

  • Does NOT disable, suspend, transfer ownership of, or delete any Google Workspace account — there is no directory/Admin step. This flow only records and notifies.
  • Does NOT revoke third-party SaaS access — that is a manual follow-up.
  • Chat cannot create a space — post to an existing space.

Verify

Test it safely

  • Workspace Studio test runs take real actions — a test really adds a row and really posts a Chat message.
  • Test with a fictional leaver against a test Sheet and a test Chat space.

Provenance

Official sources