Sign-in and sessions
How people sign in to Peerlify, what Peerlify keeps about them, and how long console and device sessions last.
Updated · ·By Ivan Vyshniak
Nothing on this page changes with your selection.
Peerlify has no passwords of its own. People sign in at login.peerlify.com through an identity provider, and Peerlify trusts what that provider says about them.
Sign-in methods
The sign-in page offers Continue with GitHub, Continue with Google, Continue with Microsoft and Continue with Apple. A provider that isn't available shows a Soon label.
Below the buttons, a Work email field looks up whether your email domain has its own identity provider registered. If it does, a Continue with button for that provider appears. See Set up single sign-on.
Signing in and creating an account are the same step: the first sign-in creates your account.
A suspended account can't sign in. The sign-in page says the account has been suspended, nothing about the account's networks changes, and a sign-in session that was already open is refused the next time the console asks for it.
What Peerlify keeps about you
From the identity provider: an identifier for you at that provider, your email address and your display name. Peerlify also records which provider you used and when you last signed in.
With GitHub, Peerlify also reads which organizations you belong to and your role in each, to add you to their networks.
With Google, Peerlify also reads whether Google has verified your email address and, for a Google Workspace account, your Workspace domain, which decides the Workspace network you join.
With a Microsoft work or school account, Peerlify also reads which Entra tenant you belong to, whether you are a guest there, your Entra administrator roles, and the domains your tenant has verified. The tenant decides which organization network you join; the verified domains let your tenant take over a network created for one of its domains by earlier Microsoft sign-ins.
Each sign-in method is a separate account. If you sign in with GitHub once and with Google later, you have two accounts, each with its own networks and roles. Use the same method every time.
Console sessions
Signing in creates two browser sessions:
| Session | Lasts | Ends when |
|---|---|---|
Sign-in service (login.peerlify.com) | 30 days after it was last used; renewed each time the console signs you in | It expires, or you clear the browser's cookies for login.peerlify.com. |
Console (web.peerlify.com) | 14 days at most | It expires, you choose Log out in the user menu, or the network's admin session timeout passes. |
Admin session timeout (Settings → User Management, default 36 hours) limits how long a console session may be used with a given network before it has to sign in again.
Log out doesn't end the sign-in session
Log out ends the console session only. While the 30-day sign-in session is still valid, the next visit to the console signs you straight back in, and so does an admin session timeout. On a shared computer, also clear the browser's cookies for login.peerlify.com.
Peerlify doesn't check back with your identity provider after sign-in. Disabling someone at the provider doesn't end their Peerlify sessions, unless the network uses user and group provisioning: then your identity provider tells Peerlify, and their access to that network ends within seconds.
Device sessions
A device has its own session, created when someone signs it in with peerlify login or an auth key. It is independent of anyone's console session:
- It lasts 180 days by default (set by Default key expiry), or forever if an admin disables expiry for that device. Both settings take effect the next time the device signs in.
- It isn't affected by signing out of the console, by changes at your identity provider, or by removing the person from the network. The exception is user and group provisioning: when your identity provider deactivates someone, their device sessions in that network end.
See Devices and, for cutting a device off, Remove a device or a person.