HR & RECRUITING

Offboarding Access-Revocation Orchestrator

When HR marks an employee as departing in Airtable, fan out revocation tasks across every connected system and write back a per-system status so nothing is left enabled.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerevent
Steps7
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerAirtable record marked "Offboarding"AirtableAirtable
  • ActionRead employee's linked system accountsAirtableAirtable
  • ActionDeactivate Outlook mailbox + revoke sign-inOutlook
  • ActionRemove user from GitHub org and teamsGitHubGitHub
  • ActionDeactivate Slack accountSlack
  • ActionWrite per-system revocation status back to recordAirtableAirtable
  • OutputPost summary of any failed revocationsSlack

What it does

Turns a single "departing" flag in your HR roster into a complete, tracked teardown of an employee's access. It reads the person's linked accounts, revokes each one, and records the outcome of every revocation back on the employee record so you have an auditable, system-by-system trail.

When to use it

Run this the moment a termination or resignation is confirmed and you need access pulled fast and provably. It's built for teams who today chase IT, Eng, and admins one Slack message at a time and can never prove every door was closed.

How it works

  1. 1An Airtable record flips to status "Offboarding", firing the trigger.
  2. 2The flow reads the employee's linked system accounts (email, repos, channels) from the record.
  3. 3It deactivates the Outlook/M365 mailbox and revokes sign-in.
  4. 4It removes the user from GitHub org and all teams.
  5. 5It deactivates the Slack account.
  6. 6Each result (success or error) is written back to a status column on the Airtable record.
  7. 7A summary of any failed revocations is posted so a human can finish the stragglers.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect OutlookMail, calendar, contacts.
  3. 3
    Connect GitHubRepos, issues, pull requests, actions.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.