IT OPS

Daily Dropbox Shared-Folder Permission Drift Audit

Scans every Dropbox shared folder each morning, diffs current member access against last known state, and posts a Slack digest of who gained, lost, or changed access overnight.

CategoryIT Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires the access sweep
  • ActionList all shared folders and current membersDropboxDropbox
  • LogicDiff current roster against prior snapshot
  • LogicGroup detected drift by folder and severity
  • OutputPost daily drift digest to SlackSlack

What it does

Runs a scheduled sweep of all Dropbox shared folders, captures the full member list and access level for each, and compares it to the snapshot from the previous run. Any added members, removed members, or role changes (viewer to editor, etc.) are flagged as drift and summarized in a single Slack message so the team starts the day knowing exactly what moved.

When to use it

Use this when shared-folder membership changes faster than anyone can track manually and you want a low-noise daily record of access changes without logging into the admin console. Ideal for IT-ops teams that need a defensible audit trail and early warning of unexpected sharing.

How it works

  1. 1A daily schedule fires the audit at a fixed time.
  2. 2Dropbox returns every shared folder plus its current member roster and access levels.
  3. 3A logic step diffs the fresh roster against the prior snapshot stored from the last run.
  4. 4If drift exists, the changes are grouped by folder and severity.
  5. 5A Slack digest lists each grant, revocation, and role change with the actor and timestamp.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DropboxFiles and folders.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.