How to Manage SecureWebX Users in SecureWebX

Who can open a credit application is a decision your store should make on purpose. Here is how to add a user, pick the role, confirm the first sign in and close the door behind anyone who leaves.

1. Open the user list

   From SecureWebX home, open Users. You get every person who can reach this store's applications, their role and their status. A brand new store reads No users yet until the first manager is added, and people already working in LeadLocate CRM arrive here through the same onboarding rather than being typed in twice.

2. Add the person or send an invitation

   Use Add a User when you are creating the account yourself with their name, work email and mobile number. Use Invite user when you would rather they set their own password: they get an invitation at their work email and finish the setup themselves. Either way, use the work email, never a shared front desk mailbox.

3. Give them the role that matches the job

   Pick the role before you save, not later. A finance manager working deals all day needs the application inbox, the worksheets and the lender shares. A salesperson who only hands out the apply link needs far less than that, and a receptionist who never touches a credit application needs no access here at all.

4. Have them accept the terms on the first sign in

   Every user ticks I have read and accept the SecureWebX Terms of Service. before the console opens. It is not a formality anyone should click past: the SecureWebX Terms of Service link on that screen is what your store is agreeing to about handling application data, and acceptance is recorded per user.

5. Confirm the first sign in worked

   Watch them do it once. They enter email and password, a single use code goes to the mobile number on their record, and the dashboard opens. If no code arrives, the number on the user record is wrong; open that User and correct it, then try again.

6. Close access the day someone leaves

   When a person leaves the store, remove their access from the same user list, that morning, before anything else on your list. Their work stays where it is: applications, notes, worksheets and the audit trail keep the name attached, because records here are archived rather than deleted.

You need a SecureWebX login with user administration, each teammate's work email and mobile number, and a decision about what each of them should be able to open. Five minutes of thinking about roles before you add ten people saves an afternoon of cleanup later.

Keep one rule: one person, one login. A shared login means the sign in code goes to one phone, the audit log shows a desk instead of a person, and the store loses the ability to answer a simple question about who opened a customer's application. The user roles and permissions page explains how roles work across the platform, and the same thinking applies here.

Start from what the person does on a Saturday. Finance staff work submitted applications end to end, so they need the inbox, the stipulations, the worksheets and the ability to send a deal to a lender. Sales managers usually want to see the pipeline and the worksheet without handling documents. Salespeople mostly need to get a customer into the application, which is the apply link, not the console.

Give the smaller role when you are unsure. Raising someone a level takes ten seconds once they ask, and every access change is written to the audit log with who made it. That log is one of the protections described on credit application security, along with encryption of application data at rest, a code on every sign in and a watermarked viewer that gates printing.

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.

The new teammate on the user list with their role, and, once they have signed in, a record of that sign in in the security log. Their name starts appearing as an assignee on applications, in notes, and on anything they send out.

They should also be able to get here without a second password. Each product is its own application under one login, so the SecureWebX button on the CRM dock carries a signed in user straight into the console, as described on single sign on. If a new hire is already working in the CRM, that one click is usually how they will open SecureWebX every day.

The invitation never arrived. Check the address on the user record first, then the store's spam folder. A personal mailbox typed in by mistake is the usual answer; correct it on the User record and send the invitation again.

They signed in but half the console is missing. That is the role doing its job. Decide whether the work really calls for more access, then raise the role rather than handing them somebody else's login.

Two people are sharing one account. The code goes to the phone on that record, so the second person is stuck at the code screen. Add them their own user; it fixes the sign in and the audit trail in the same move.

Nobody at the store can get in to fix it. Our support team can see your screen with you and sort it out on the call, so keep working the deal and call us while the customer is still in the box.

Handing customers a way to apply is the other half of this setup, and apply links covers the branded links a store can customize with its own sections, fields, document uploads and disclosures. Users open what comes back; apply links decide what comes in.

The LeadLocate Help Center has the neighboring guides, including setting up the sign in code, exporting an application and opening a support ticket. A permission split your store needs that you do not see in the roles today is available on request, and our team puts it in production for your dealership.

Do my CRM users automatically become SecureWebX users?

Store onboarding brings your team across so nobody is typed in twice, and the SecureWebX button on the CRM dock opens the console for a signed in user. You still choose each person's role here.

How many users can a store have?

Add the whole team. One login per person is the goal, since sign in codes, assignments and the audit log all key off the individual user rather than a desk.

What happens to a person's work when I remove them?

It stays. Applications, notes, worksheets and the audit trail keep their name on them, because records are archived rather than deleted, which is what a compliance review expects to find.

Can a lender or an outside partner have a login?

Add them as a partner rather than as a user, and invite them to set themselves up. They get their own credentials and your user list stays your team.

Users, roles, invitations and a full audit trail come with SecureWebX, alongside the application inbox and secure lender shares. See the console in the pre-recorded demo.

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