How to Set up Two-Factor Authentication in SecureWebX

There is no switch to hunt for. Every SecureWebX sign in asks for a code, because the records behind that login are credit applications. Your job is to keep the right mobile number on your user record.

1. Put your mobile number on your user record

   The code goes to the number stored on your user, not to a number you type at the door, so check it before the day you need it. A user who already has a good mobile number on file reads Already set up in the console, and nothing else is required of that person.

2. Sign in with your email and password

   Open the console and sign in the way you always do. The password screen hands off to the code screen on its own; there is no separate security tab to visit first and no setting a manager has to release for you.

3. Enter the code that arrives by text

   The text carries a short numeric code. Type it into the code screen and you are in. The code is single use and short lived, so an old text sitting in your phone from this morning will not work in the afternoon; request a fresh one instead of scrolling back.

4. Fix a number that is wrong or missing

   New phone, new carrier, or a typo from onboarding: a manager opens that person's user record and uses Set on the mobile number, then the next sign in sends the code to the new phone. The change lands in the audit log with who made it, which is exactly what you want an access change to do.

5. Give lenders and partners their own sign in

   Never hand a lender or a vendor one of your logins. Add them as a partner and choose Invite this partner to set it up themselves so they create their own credentials and answer their own code. Your users stay yours, and the audit log stays readable.

You need a SecureWebX user of your own and a mobile phone that can take a text. That is the list. Managers who set up teammates also need the user administration view, which comes with the manager roles described on user roles and permissions.

One rule saves a lot of trouble later: one person, one login. A shared front desk login means the code goes to whoever owns that phone, and the audit log then shows a room instead of a person. Give every teammate their own user, and every code reaches the right hand.

Because of what is behind the login. A credit application carries a Social Security or ITIN number, income, residence history and a signature. A second factor on every sign in is one of the protections built into credit application security, next to encryption of application data at rest, a full audit log, virus scanning on uploads and a watermarked viewer that gates printing and downloading.

Dealers ask whether they should use an authenticator app instead, the way they do for email or social accounts. The code here comes as a text to the number on your user record, so your team installs nothing and a new hire is productive the same morning. A different second factor your compliance policy calls for is available on request, and our team puts it in production for your dealership.

Leave your number and a lead specialist calls you back to answer your questions about pricing, coverage, and setup. Mon - Sat, 9:00 AM - 6:00 PM Pacific.

Prefer to talk right now? Call or text 844-376-2274.

After the password screen, a short code screen. Within a few seconds the text arrives on the phone tied to your user, you type the code, and the console opens on the dashboard with the application badges. From there on it behaves like any other session, and the one click launch from the CRM dock still carries you in without re typing anything.

On a manager's user list, people with a mobile number on file read Already set up. Each sign in writes to the security log with the user, the time and the result, so a manager reviewing access sees who came in and when without asking anyone.

No text arrived. The number on the user record is the one to check first, especially for anyone who changed phones. A manager opens the user and corrects it, then you sign in again. Also check that the phone has service where you are standing; a code cannot reach a phone in the basement of the service drive.

The code is refused. You used an older text. Codes expire and each one works once. Start the sign in again and use the newest message.

Two people share the login. The code goes to the phone on that record, which is the other person's. Split it into two users; it takes a minute and it fixes the sign in, the audit trail and the assignment of applications at the same time.

You are locked out with nobody in the store to help. Our support team can see your screen with you and sort it out on the call, and a manager with user administration can update your number in the meantime.

Adding and removing the people who sign in is covered in the guide to managing SecureWebX users, and the way one set of credentials carries you between the applications is on single sign on. Each product is its own application under one login, so the same care you take with this user record pays off everywhere your team works.

The LeadLocate Help Center holds the rest of the step by step guides. If your store has a security review coming up and wants the full picture in writing, the credit application security page is the one to send to whoever is asking.

Do I have to turn two factor authentication on?

No. It runs on every SecureWebX sign in for every user. The only thing you maintain is the mobile number on your user record, which is where the code goes.

Do I need an authenticator app?

No. The code arrives as a text to the number on your user record, so there is nothing to install on a phone or a workstation before a new hire can sign in.

What happens when someone changes their phone number?

A manager opens that user record and updates the mobile number. The next sign in sends the code to the new phone, and the change is recorded in the audit log.

Can a lender or vendor use our login?

Give them their own instead. Add them as a partner and invite them to set themselves up, so they hold their own credentials and your audit log still reads clearly.

A code on every sign in, encryption at rest, a full audit log and a watermarked viewer come standard with SecureWebX. See the whole console in the pre-recorded demo.

Prefer to talk right now? Call or text 844-376-2274.