IT OPS

Weekly Dropbox permission-drift diff against an approved baseline

Compares current team-folder membership against a baseline stored in Coda each week, flags every added, removed, or role-changed permission.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule starts comparison
  • ActionSnapshot current team-folder membershipDropboxDropbox
  • ActionRead approved baseline matrix from CodaCodaCoda
  • LogicDiff snapshot vs baseline, flag unauthorized adds
  • ActionWrite drift report to Coda audit logCodaCoda
  • OutputEmail drift report to ITOutlook

What it does

Every week this workflow snapshots who has access to which Dropbox team folders, diffs that snapshot against an approved baseline kept in Coda, and produces a drift report of every permission that was added, removed, or changed role since the baseline. Unauthorized additions are highlighted for follow-up.

When to use it

Use it when you maintain an approved access matrix and need to detect quiet drift, the slow accumulation of one-off grants that never get cleaned up. It's report-only by design, giving IT visibility before deciding what to revoke.

How it works

  1. 1A weekly schedule starts the comparison.
  2. 2Dropbox returns current membership for every team folder.
  3. 3The approved baseline matrix is read from Coda.
  4. 4A diff step computes added, removed, and role-changed entries per folder.
  5. 5A filter elevates additions that are not present in the baseline as unauthorized.
  6. 6The drift report is written to Coda for the audit trail and emailed to IT via Outlook.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DropboxFiles and folders.
  2. 2
    Connect CodaDocs, packs, automations.
  3. 3
    Connect OutlookMail, calendar, contacts.
  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.