IT OPS

Quarterly Stale Dropbox Access Revocation Runbook

Each quarter, identifies shared-folder members who have had no access activity past a threshold, and after Slack approval runs a shell-driven Dropbox API revocation.

CategoryIT Ops
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerQuarterly schedule starts the runbook
  • ActionList members with last-activity timestampsDropboxDropbox
  • LogicSelect members past inactivity threshold
  • OutputRequest batch revocation approval in SlackSlack
  • ActionRevoke approved members via Dropbox APIShell

What it does

Finds dormant access: members who still hold rights to shared folders but have not opened or modified anything within the configured inactivity window. It compiles the stale-access list, requests one batch approval in Slack, and on approval executes the revocations through a shell step calling the Dropbox API, recording every removal as it goes.

When to use it

Use this for the recurring housekeeping pass that keeps shared-folder rosters lean. It closes the loop that audit-only workflows leave open by actually removing access once a human signs off, while keeping a clear record of what was revoked and why.

How it works

  1. 1A quarterly schedule starts the cleanup runbook.
  2. 2Dropbox returns folder members with their last-activity timestamps.
  3. 3A logic step selects members past the inactivity threshold.
  4. 4The candidate list is posted to Slack for a single batch approval.
  5. 5On approval, a shell step calls the Dropbox API to revoke each member.
  6. 6Each revocation is logged to the run output for the audit trail.

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
    Connect ShellRun sandboxed commands inside the workspace.
  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.