HR & RECRUITING

Source Control Access Purge on Engineer Departure

When an engineer is marked as offboarding in monday, this workflow removes their GitHub and GitLab access, revokes personal access tokens.

CategoryHR & Recruiting
Enginesim
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonday flags engineer offboardingmonday.com
  • ActionRemove GitHub access and revoke tokensGitHubGitHub
  • ActionRemove GitLab access and revoke tokensGitLabGitLab
  • LogicFlag failed removals or live tokens
  • ActionRecord removed grants to audit log
  • OutputDeliver purge report to security SlackSlack

What it does

Locks a departing engineer out of all source control. Triggered by an offboarding flag in monday, it removes the user from GitHub organizations and teams, removes them from GitLab groups and projects, revokes any active personal access tokens, and records each removed grant. The output is a security-ready report of exactly which repositories and tokens were touched.

When to use it

Use it for any technical departure where lingering repo access or live tokens are an unacceptable risk. Best for engineering orgs that span both GitHub and GitLab and need a single, auditable purge instead of two manual cleanups.

How it works

  1. 1A monday status change to "Offboarding" for an engineering role triggers the workflow.
  2. 2It removes the user from all GitHub orgs, teams, and repository collaborations, and revokes their tokens.
  3. 3It removes the user from all GitLab groups and projects and revokes GitLab tokens.
  4. 4A logic step flags any removal that failed or any token that could not be revoked.
  5. 5Each removed grant is recorded to the security audit log.
  6. 6A consolidated purge report is delivered to the security review channel in Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect monday.comVisual work management for teams.
  2. 2
    Connect GitHubRepos, issues, pull requests, actions.
  3. 3
    Connect GitLabRepos, MRs, pipelines, registry.
  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.