Sign in with GitHub
How GitHub sign-in gives you a personal network and a network for each GitHub organization, who owns it, and what happens when someone leaves.
Updated · ·By Ivan Vyshniak
Nothing on this page changes with your selection.
Continue with GitHub on the sign-in page signs you in with your GitHub account. Peerlify reads your profile, your verified email addresses and the organizations you are an active member of, with your role in each.
Your own network
Your first sign-in creates a network named after you, with you as its Owner. You keep it whatever organizations you belong to.
Organization networks
Each GitHub organization you belong to can have one Peerlify network.
- Who creates it. Only an owner of the organization on GitHub creates it, by signing in, and becomes its Owner in Peerlify.
- Who joins. Other organization owners who sign in later join as Admin; members join as Member. A member who signs in before the network exists gets only their own network, and joins at their next sign-in after an owner has created it. If Manual user approval is on, members wait in the queue until an admin approves them (see Approve new members).
- A network without an Owner gets as its Owner the first organization owner who signs in. For a network from before Peerlify tracked organizations by ID, linked by its Owner or by Peerlify support, that has to be someone who was already in it before the link.
- Renaming the organization keeps its network, members and devices. An organization that later takes the old name never gets into it, and an organization created after a network was made can never take that network over.
- Outsiders join through an invite.
Networks Peerlify made for an organization before it tracked organizations by their GitHub ID are linked to the organization the next time their Owner signs in. If such a network has no Owner, sign-ins never link it: contact Peerlify support to link it to your organization. Until then its members keep their access and nobody new joins it automatically. The details are in How you get networks.
Leaving, and removing people
- Someone leaves the organization. Their next GitHub sign-in removes the membership they got through the organization, once GitHub confirms they left; their auth keys there are revoked and their devices stay. Access they got through an invite stays. See Someone leaves your GitHub organization.
- You remove someone on the Members page. The removal sticks: their later sign-ins don't add them back until they accept an invite. See A removal sticks.
A person who left the organization but never signs in again stays a member until you remove them.
For organization owners: approve Peerlify
If your organization has OAuth app access restrictions turned on, GitHub hides your organization from Peerlify until you approve the app, so members get only their own network. Approve it either way:
- when someone signs in, they click Request next to your organization on GitHub's authorization screen (or Grant, if they are an owner); an owner then approves it under Organization → Settings → Third-party access → OAuth application policy, or
- an owner approves Peerlify on that page ahead of time.
Restricting the app later never removes anyone from the Peerlify network: Peerlify removes people only when GitHub confirms they left.
If your organization requires SAML single sign-on, GitHub lists it only for people whose GitHub sign-in is authorized for your SAML session. Until then they don't join automatically, and nobody is removed.
If sign-in fails
The login page explains what went wrong, for example "Sign-in was cancelled" when you declined on GitHub's page. See Sign-in and enrollment problems for every message and its fix.