Google Workspace + Kroy

Connect Google Workspace once. Use it safely with any AI.

  1. Google Workspace, where it already is.

    Google Workspace stays the authoritative record. Nothing moves, and nothing is copied that doesn’t need to be.

  2. Google Workspace connects to Kroy.

    OAuth 2. Kroy holds the connection.

  3. Your AI connects to Kroy.

    Claude, ChatGPT or another AI connects to Kroy — not to Google Workspace. It never receives Google Workspace credentials.

  4. Exactly what is allowed.

    Each Google Workspace action is a Kroy capability; send mail waits for a person by default. Sending mail and sharing files require human approval by default.

  5. A real request.

    Claude asks for read mail. Kroy checks the person, the agent and the policy, calls Google Workspace, and records the request.

Google Workspace
Kroy
Claude
Priya Client manager
AUDIT

Google Workspace capabilities

  • gmail.mail.read
  • gdrive.files.read
  • gcalendar.events.read
  • gmail.draft.create
  • !gmail.mail.send
  • Sending mail and sharing files requir…
Google Workspace
Kroy
Claude
Priya Client manager
AUDIT

Google Workspace capabilities

  • gmail.mail.read
  • gdrive.files.read
  • gcalendar.events.read
  • gmail.draft.create
  • !gmail.mail.send
  • Sending mail and sharing files requir…
Google Workspace connecting to Kroy, then to an authorised AI. Google Workspace, where it already is.. Google Workspace connects to Kroy.. Your AI connects to Kroy.. Exactly what is allowed.. A real request..

Supported resources

  • Gmail messages and drafts
  • Google Drive files and shared drives
  • Google Docs and Sheets content (read)
  • Google Calendar events

Authentication

OAuth 2.0 with Google, configured by a Google Workspace administrator. Kroy holds the connection; AI clients never receive Google tokens.

Supported actions

CapabilityTypeDefault
gmail.mail.read
Read mail
readPolicy
gmail.draft.create
Create draft
writePolicy
gmail.mail.send
Send mail
writeHuman approval
gdrive.files.read
Read files
readPolicy
gdrive.files.create
Create file
writePolicy
gdrive.files.share
Share file
writeHuman approval
gcalendar.events.read
Read calendar
readPolicy
gcalendar.events.create
Create calendar event
writePolicy

Events

gdrive.file.createdgmail.mail.received

Overview

For many firms, Google Workspace is where the work is: the proposal in Drive, the client thread in Gmail, the deadline in Calendar. Kroy connects to Workspace once, then gives each authorised AI exactly the slice a task needs.

Permissions

Each Workspace action is a Kroy capability. Kroy decides every request against the person, the agent, the delegation between them and the organisation’s policies.

A Skill such as Prepare Proposal might be allowed to read a client folder and the previous proposals, and to create a new document — but not to read the rest of the drive, and not to email the client.

Drafts, not sends

A common policy is that AI may prepare external communication but a person sends it. Kroy enforces this at the action level: gmail.draft.create can be permitted while gmail.mail.send requires approval. The same applies to sharing: gdrive.files.share with anyone outside the organisation requires approval by default.

Industries

Consultancies, law firms and accountancy practices running on Google Workspace can use the same per-client boundaries described for Microsoft 365: an AI acting for a person sees the clients and matters that person works on, and nothing else.

Security

Kroy holds the Google connection. AI clients receive results, never tokens. Revoking an AI’s Kroy access removes its Workspace access immediately. Every read, draft, send and refusal is recorded.

Limitations

  • Sending mail and sharing files require human approval by default.
  • Kroy respects Google Drive sharing; it cannot grant access Google Workspace does not.
  • Workspace administration, user management and security settings cannot be changed through Kroy.
  • Actions are subject to Google’s own API quotas.