DOCUMENT OPS

Block external Google Drive shares until a redaction review passes

Detects when a Drive file's sharing changes to external or anyone-with-link, scans it for sensitive data, and reverts the share plus opens a review if it fails the gate.

CategoryDocument Ops
Enginesim
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDrive file shared externally or set to anyone-with-linkGoogle DriveGoogle Drive
  • ActionRead file content as textGoogle DriveGoogle Drive
  • ActionScan for PII and secretsOpenAI
  • LogicPass or fail against sharing policy
  • ActionRevoke external permission on failGoogle DriveGoogle Drive
  • OutputOpen redaction review task in LinearLinearLinear

What it does

Monitors Google Drive permission changes and intercepts files that get shared externally or set to "anyone with the link." Each newly externalized file is scanned for PII and secrets; if it fails, the workflow revokes the external grant and routes it for human redaction review.

When to use it

Use it when contractors or employees can self-serve external sharing and you need a safety net that catches an over-shared spreadsheet or contract before a recipient ever opens it. Best for orgs enforcing data-handling policy on a shared Drive.

How it works

  1. 1A Drive file-permission change to external/public fires the trigger.
  2. 2The file content is read and reduced to text.
  3. 3An OpenAI scan returns sensitive-data findings by category and location.
  4. 4A logic branch decides pass or fail against policy.
  5. 5On fail, the external permission is removed so the link goes dead immediately.
  6. 6A review task is created in Linear with the file link, the findings, and the user who shared it, so an owner can redact and re-approve.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.