IT OPS

Weekly Dormant Seat Audit Against Departed List

Runs every week to cross-check active SaaS seats against your roster of departed employees, then revokes and confirms any access that slipped through earlier offboarding passes.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionRead departed-employees rosterNotionNotion
  • ActionList active GitHub and Slack seatsGitHubGitHub
  • LogicMatch active seats to departed people
  • ActionRevoke straggler seats and confirm removalSlack
  • OutputPost straggler audit digest to IT channelSlack

What it does

Catches the revocations that earlier offboarding runs missed. On a weekly schedule it pulls the list of departed employees from your records, enumerates active seats across each SaaS tool, and flags any seat still belonging to someone who has left. It then revokes those stragglers and confirms each one is gone.

When to use it

Use it as a safety net behind your real-time offboarding flow. Perfect for catching seats added back by accident, tools that weren't connected at departure time, or contractors whose access lingered past their end date.

How it works

  1. 1A weekly schedule triggers the audit.
  2. 2The flow reads the departed-employees roster from a Notion database.
  3. 3It lists active members in each connected tool (GitHub org, Slack workspace) and compares against the roster.
  4. 4A logic step isolates seats that belong to departed people.
  5. 5For each match it revokes the seat and re-queries to confirm removal.
  6. 6A digest of every straggler found, revoked, and confirmed is posted to the IT channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect NotionPages, databases, comments.
  2. 2
    Connect GitHubRepos, issues, pull requests, actions.
  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.