Only members with owner privileges for an organization or admin privileges for a repository can convert organization members into outside collaborators.
Adding an outside collaborator to a private repository will use one of your paid licenses. For more information, see "About per-user pricing." When you add an outside collaborator to a repository, you'll also need to add them to any forks of the repository you'd like them to access.
After converting an organization member to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The person will no longer be an explicit member of the organization, and will no longer be able to:
- Create teams
- See all organization members and teams
- @mention any visible team
- Be a team maintainer
For more information, see "Roles in an organization."
We recommend reviewing the organization member's access to repositories to ensure their access is as you expect. For more information, see "Managing an individual's access to an organization repository."
When you convert an organization member to an outside collaborator, their privileges as organization members are saved for three months so that you can restore their membership privileges if you invite them to rejoin your organization within that time frame. For more information, see "Reinstating a former member of your organization."
Note: You may not be able to convert an organization member to an outside collaborator, if an organization owner has restricted your ability to add outside collaborators.
In the top right corner of GitHub.com, click your profile photo, then click Your organizations.
Click the name of your organization.
Under your organization name, click People.
Select the person or people you'd like to convert to outside collaborators.
Above the list of members, use the drop-down menu and click Convert to outside collaborator.
Read the information about converting members to outside collaborators, then click Convert to outside collaborator.