1. Log in and navigate

Log in to LambdaAssetCheck

Sign in with your email and password, or with single sign-on (SSO) if your organisation has enabled it. This page covers password sign-in, two-step verification (MFA), staying signed in, resetting a password, and SSO.

Last updated: September 2026

What you'll need

TierAny plan
PlatformWeb app or mobile app
PermissionNone. You need an account, which an owner or administrator creates for you.
WhereYour organisation's app URL, which your administrator provides

Two things are worth having ready before you start:

  • Your credentials — email and password, or your company SSO if your organisation requires it.
  • An authenticator app when MFA is required for you. Owners, administrators, and Admin-designated roles always need one for password sign-in. Your organisation may also require MFA for every password user (Organisation Settings → Security). Setup happens at sign-in when it is required — not from My account.

Sign in

  1. Open your organisation's LambdaAssetCheck URL.
  2. Enter your Email.
  3. Enter your Password.
  4. Optional: select Remember for 30 days only on a device you control.
  5. Select Sign In.
Sign-in screen: email, password, Remember for 30 days, Forgot password, and Sign In.

What happens next

  • If MFA is not required and not enabled → you go to Home.
  • If MFA is already enabled → you enter a 6-digit authenticator code (or a recovery code).
  • If MFA is required for your account and you have not set it up yet → you complete Set up authenticator MFA before Home.

The sidebar areas you see depend on your role and permissions.

Two-step verification (MFA)

If your organisation requires it, you enter a 6-digit code from an authenticator app after your password.

WhoMFA on password sign-in
Owners, administrators, and custom roles with the Admin designationRequired
Everyone, if your organisation turns on Require MFA for all password usersRequired
Everyone elseNot used
Anyone signing in with SSONot used — your identity provider handles it
Signing in with a password, then reaching the Two-step verification screen with its Authentication code field and Verify button

Setup, recovery codes, and what to do if you lose your authenticator: Set up two-step verification.

Stay signed in

Use Remember for 30 days only on a device you control. Do not use it on shared or public computers.

  1. On the sign-in screen, select Remember for 30 days.
  2. Complete sign-in as usual, including two-step verification if prompted.
Selecting Remember for 30 days on the sign-in screen

Expected result: On that trusted device, you stay signed in longer between visits. Leave the checkbox cleared on a shared computer.

Reset your password

  1. On the sign-in screen, select Forgot password?.
  2. Enter the email address for your account.
  3. Select Reset password.
  4. Follow the reset link in the email (check spam if it does not arrive).
The Forgot password page reached from the sign-in link, with the account email entered and Reset password ready to select

If the email does not arrive, confirm you used the address your administrator registered, then ask them to verify your account is active.

Expected result: You see confirmation that instructions were sent if an eligible account exists for that email. After you set a new password from the link, sign in normally. If MFA is enabled, you still complete two-step verification after the new password.

Single sign-on (SSO)

If your organisation uses SSO, sign in through your company identity provider instead of a LambdaAssetCheck password.

  1. Open the sign-in page and enter your work Email.
  2. When SSO is available for your domain, select Continue with {organisation} SSO (the button shows your organisation name).
  3. Complete sign-in at your identity provider.

Administrators configure SSO under Administration → Organisation Settings → Security. Setup steps: Set up single sign-on.

The sign-in page after entering a work email: "Continue with AssetCheck Inc. SSO" appears above the password field, so either route is available

Expected result: You go to your identity provider, then return to LambdaAssetCheck Home. If your organisation requires SSO, the password fields may be hidden.

Important: After SSO, you are not asked for a LambdaAssetCheck authenticator code — even if MFA is enabled or required in LambdaAssetCheck. Second factor on this path is only at the identity provider. If SSO is optional and you sign in with a LambdaAssetCheck password instead, that password path still follows the MFA rules above.

Was this page helpful?

Need more help?

Top