Downgrade GitHub member to outside collaborator
Automatically convert a GitHub organization member to an outside collaborator from a Slack request with Stepwork. Their access is limited to the repositories you name.
- Use case
- Access managementIT
- Best for
- IT Administrator
- Applications used
GitHub
Slack
- Business outcome
- Risk reduction
The problem
They became a contractor. They kept every repo.
When an employee moves to a contract, they often still need one or two repositories. Removing them entirely stops the work, so their full organization membership stays as it was.
That leaves a contractor with every team and every internal repository a member can reach. Scoping it down by hand means converting the account and checking each repository, and that waits until someone has time.
The outcome
They keep the repositories they need, and nothing else
Stepwork converts the member to an outside collaborator and leaves them with only the repositories in the request. The work can continue, and the run records who asked, which repositories were kept, and when membership ended.
- Organization membership and team access end.
- Only the repositories in the request stay.
- A repository that does not exist stops the run.
The process
From Slack request to scoped access
A manager posts the change in Slack. Stepwork converts the member in your GitHub organization settings and checks their repository access against the request.
- Step 1
Request it in Slack
A manager posts the person’s GitHub username and the repositories they still need in the access channel. That message starts the flow, and Stepwork records who asked and when.
- Step 2
Find the member
Stepwork signs in to GitHub and opens the organization’s People page. If no member matches the username, the run stops instead of guessing.
- Step 3
Convert to outside collaborator
Stepwork converts the member to an outside collaborator, the same action an organization owner takes from the People list. Their organization membership and team access end.
- Step 4
Limit access and reply in Slack
Stepwork checks the person’s repository access against the request. Repositories on the list are kept, and any other is removed. Then it posts the result in Slack.
Why Stepwork
Scoped down to the list, every time
Stepwork runs the path you recorded in your GitHub organization settings. It converts the member, then compares their repository access with the request. Anything not on the list is removed, whoever asked.
Similar use cases
Similar use cases
- Remove outside collaborator from GitHub reposFinds every repository where a given outside collaborator has access and removes them from each.
- Remove member from organization in GitHubSigns into GitHub org settings, locates the member, and removes them, revoking repo access and freeing the seat.
- Invite member with team assignment in GitHubInvites a new member to the GitHub org and adds them to the teams that grant their repo access.
FAQ