Perk supports several ways to sign in, so you can access the platform securely. This article explains each sign-in method: what it is, when it applies, and where to go to use it. The methods available depend on how you want to configure your organization's Perk account.
Email one-time passcode (OTP)
Email one-time passcode (OTP) is the default sign-in method for all Perk users. When you sign in, Perk sends a one-time passcode to your email. Enter this code on the sign-in page to access your account—there’s no password to remember or manage.
The passcode expires after 5 minutes, so make sure to use it quickly. This method is always available unless your admin has turned on SSO-only sign-in. For more information, see Sign in to Perk with your email address.
Passkeys
Passkeys are a newer, device-based sign-in option that let you verify your identity using your device's built-in security—such as Face ID, Touch ID, or Windows Hello—instead of entering a passcode.
Passkeys are saved on the device or browser where you set them up, so you may need to create one for each device you use to sign in to Perk. Even if you have a passkey set up, you can still sign in with an email one-time passcode whenever you prefer.
Single sign-on (SSO)
Single sign-on (SSO) lets you sign in to Perk using the same credentials you use for other company tools. It’s managed through a central identity provider and must be set up by your account admin.
Once SSO is set up, you’ll be redirected to your company’s dedicated sign-in page instead of the standard Perk sign-in screen.
Note: When SSO is enforced for an organization, it overrides all other sign-in methods. Users are redirected to the company SSO flow regardless of which other methods they have set up, including passkeys.
Federated identity provider (Google)
If your organisation uses Google as its identity provider, you can sign in to Perk using your Google account.
This works when the email address on your Perk account matches your Google account email. Perk does not have access to your Google password—it only uses Google to verify your identity. For more information, see Sign in to Perk with a Google account.
Other identity providers
Perk supports SSO using OAuth 2.0 and SAML 2.0, so it works with a range of identity providers beyond Google, including Microsoft Entra ID, OneLogin, and Okta.
Your account admin sets up and manages the connection. If you’re not sure which provider your organisation uses, contact your admin. To learn more, see Using SSO.
Signing in on the Perk app
The Perk app supports one-time passcode (OTP), Google account sign-in, and SSO—the same core methods available on the web. You can choose whichever method applies to your account when you open the app. We will offer passkeys as a sign-in option shortly. To learn more, see Sign in to the Perk app.
How admins control sign-in methods
Admins on Premium and Pro plans can set up SSO through an identity provider. To make SSO the only way to sign in, turn on the SSO-only setting. This prevents users from using other sign-in methods.
Admins can also turn on Admin override. This allows admins to sign in with a one-time passcode if SSO isn’t working, so you don’t lose access to the account. For more information, see Customize SSO settings.