IT OPS

Quarterly Dropbox Access Attestation Campaign

Agent-driven quarterly campaign that compiles each sensitive Dropbox folder's external collaborators, asks the owner via Teams to attest line by line.

CategoryIT Ops
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerQuarterly attestation schedule
  • ActionCompile external roster per Dropbox folderDropboxDropbox
  • ActionSend per-owner attestation in TeamsMicrosoft Teams
  • LogicInterpret keep/remove decisions
  • ActionRecord attestations in Postgres ledgerPostgreSQLPostgres
  • OutputOpen Linear issue for each removalLinearLinear

What it does

This workflow runs a structured access-recertification campaign. For every sensitive Dropbox folder it assembles the current external collaborator roster, then reaches each folder owner in Teams with an itemized attestation: keep or remove, per person. Decisions are logged to Postgres as the new approval-of-record, and any "remove" decision spawns a Linear issue so the revocation is actually executed and tracked.

When to use it

Use it for periodic compliance recertification — SOC 2, ISO, or internal policy — where owners must affirmatively re-attest who should retain access. It replaces a manual spreadsheet exercise with an orchestrated, fully auditable campaign.

How it works

  1. 1A quarterly schedule launches the campaign.
  2. 2Dropbox supplies the external collaborator roster for each sensitive folder.
  3. 3The agent composes a per-owner attestation and sends it via Teams.
  4. 4A logic step interprets each keep/remove response.
  5. 5Decisions are written to the Postgres approval ledger.
  6. 6Each removal decision opens a Linear remediation issue.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DropboxFiles and folders.
  2. 2
    Connect Microsoft TeamsChannels, chats, files.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Connect LinearIssues, projects, cycles, triage.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.