IT OPS

Dormant OAuth Grant Quarterly Revocation Review

Each quarter, identifies OAuth apps that have not been used in 90+ days and compiles a cleanup report in Notion with a per-app recommendation so IT can bulk-revoke stale…

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerQuarterly schedule fires
  • ActionPull grants with last-activity timestampsCustom MCP server
  • LogicFlag 90+ day idle apps and score them
  • ActionBuild Notion review doc with recommendationsNotionNotion
  • OutputNotify IT channel doc is readySlack

What it does

Finds the long tail of forgotten OAuth grants: apps an employee connected once and never used again. It builds a quarterly Notion review doc ranking each stale app and recommending keep or revoke.

When to use it

Run it as a recurring access-hygiene chore. Dormant grants are pure attack surface with no business value, and a quarterly sweep keeps your authorized-app list lean without disrupting active tools.

How it works

  1. 1A quarterly schedule starts the review.
  2. 2A custom-MCP call pulls every grant plus its last-activity or last-token-use timestamp.
  3. 3A logic step flags apps idle for 90+ days and scores each by scope sensitivity and user reach.
  4. 4A Notion action creates a structured review page listing flagged apps with a keep/revoke recommendation and rationale.
  5. 5A Slack action notifies the IT channel that the quarterly review doc is ready.
  6. 6The output records the review cycle so the next quarter compares against fresh activity data.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Custom MCP serverConnect any MCP-compatible tool you own.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.