Remove outside collaborator from GitHub repos
Automatically remove an outside collaborator from every repository in your GitHub organization from a Slack request with Stepwork. External code access ends in one run.
- Use case
- Access managementIT
- Best for
- IT Administrator, IT Manager
- Applications used
GitHub
Slack
- Business outcome
- Risk reduction
The problem
The project ended. Their repo access didn’t.
Contractors and agency developers join GitHub as outside collaborators, added one repository at a time. When the work ends, nobody has a full list of where they were added.
So an admin hunts repository by repository, or misses a few. Each one missed is source code an outside person can still read, months after their contract finished.
The outcome
Every repository is closed to them in one run
Stepwork removes the outside collaborator from every repository in your organization at once. Nothing is left behind in a repository nobody remembered, and the run records who asked and when access ended.
- Access ends in every repository, not only the ones on a list.
- Organization members are never changed by this flow.
- The run stops if the username is not an outside collaborator.
The process
From Slack request to no repository access
A teammate posts the collaborator’s GitHub username in Slack. Stepwork removes them from the outside collaborators list in your organization settings.
- Step 1
Request it in Slack
A teammate posts the outside collaborator’s GitHub username in the access channel. That message starts the flow, and Stepwork records who asked and when.
- Step 2
Find the collaborator
Stepwork signs in to GitHub and opens the organization’s outside collaborators list. If the username is not there, the run stops instead of guessing.
- Step 3
Remove from all repositories
Stepwork removes the person from every repository in the organization in one action, the option GitHub gives organization owners for outside collaborators.
- Step 4
Confirm and reply in Slack
Stepwork checks that the person no longer appears as an outside collaborator, then posts the result back in Slack.
Why Stepwork
No repository left behind
Credentials stay in 1Password. Stepwork signs in to GitHub with a vault reference, removes the collaborator from every repository at once, and confirms they are gone. Nobody has to remember where they were added.
Similar use cases
Similar use cases
- Downgrade GitHub member to outside collaboratorConverts an org member to an outside collaborator limited to specified repositories.
- Remove member from organization in GitHubSigns into GitHub org settings, locates the member, and removes them, revoking repo access and freeing the seat.
- Deactivate expired guest accounts in SlackReviews guest accounts against their intended end dates and deactivates those past expiry.
FAQ