Completing Your Branch and User Setup Files

The Three Files You Need

All three are attached at the bottom of this page.

Branch file upload template. A spreadsheet with one row per branch, covering address, phone, NMLS number, and how you identify each branch.

User file upload template. A spreadsheet with one row per user, covering name, contact details, permission level, and which branch they belong to.

Instructions document. A column-by-column reference for both templates: what each column expects, which columns are required, and how values need to be formatted. Read this first. It answers most questions before you run into them.

Both templates are CSV files. You can open them in Excel, Numbers, or Google Sheets.

Before You Start

A few things apply to both files:

• Leave the column headers and column order exactly as they are. Both files are read by column position. Renaming, reordering, or inserting a column will cause the upload to fail.
• Save as CSV. If you open a file in Excel and use "Save As," confirm the format stays CSV rather than switching to a workbook.
• Watch for numbers that lose leading zeros. Spreadsheet apps often drop the leading zero from a zip code, turning 02134 into 2134. Format those columns as text before you type, or confirm the values are intact before you send the file.
• Use company email addresses. Every user email needs to be on your company's approved domain. Personal addresses such as Gmail cannot be used.
• Enter phone numbers as digits only. Remove any dots or dashes.

Permission Levels and Role IDs

The user template has a Role ID column, which is where you set what each person can see and do. Enter the number that matches the level of access you want:

If your company has multiple DBAs under one corporate umbrella, divisions are how those are organized. Anyone who needs to oversee every branch within their DBA should be set to Role ID 4.

About NMLS Numbers

Every loan officer needs an NMLS number in the user file. It serves two purposes: it verifies permissible purpose to receive prescreened credit information, and it prints on personalized firm offer of credit letters and email offers.

You can leave the NMLS column blank for loan officer assistants and for admins who are not loan officers.

How to Complete and Return Your Files

1. Download all three files from the attachments at the bottom of this page.
2. Open the instructions document and read the column definitions for both templates.
3. Fill in the branch template first. Users are assigned to branches, so your branch list needs to exist before the user list can reference it.
4. In the branch template, give every branch a name or identification number in the "Branch Name or Identification Number" column. This is what connects users to branches.
5. Fill in the user template. In the branch column, copy the branch identifier exactly as you wrote it in the branch file.
6. Check the required columns are complete. The instructions document marks these with an asterisk.
7. Email both completed files to your Activation Manager.

If a branch identifier is spelled differently in the two files, the user will not attach to that branch. Copying the values directly from your branch file avoids this.

Two Things to Send Separately

Neither of these fits in the templates, and both are easy to overlook.

A company fallback Apply Now URL. The user template has an optional Apply Now URL column for each loan officer's individual link. Email your Activation Manager a single company-wide fallback URL as well. If a user is ever created without their own link, the fallback keeps the Apply Now button in their email offers from erroring out.

Logos for each DBA. If you fill in the DBA column on the branch template, send a logo for each DBA along with your files.

Optional Columns Worth Knowing About

These are not required, but they change what appears on your offers:

• Branch License. State licensing specific to a branch, printed on that branch's firm offer of credit letters and email offers. If you leave it blank, the company-level licensing disclosures collected during onboarding are used instead.
• User License. A licensing statement specific to a loan officer, printed on their mailed firm offer of credit letters.
• Alt ID. Your own internal identifier for a user, which can be used to route data to the right account from an API or another integration.
• Title for marketing. A loan officer's signature title. If you leave it blank, Loan Officer is used.

FAQ

What is the branch phone number used for? Calls are forwarded to it when a loan officer has not set up a personalized campaign of their own.

Can I add columns for information we track internally? No. Extra columns break the upload. Send any additional details to your Activation Manager in the body of your email instead.

Do I need to include users who are not loan officers? Include anyone who needs to sign in. Set the "licensed Loan Officer that should receive alerts" column to No for admins who only need an account for management purposes, so they do not receive alerts of their own.

Can we hold off on users receiving their activation emails? Yes. Set the activation email column to No, and set the active column to No as well. Many companies do this so users are not emailed before an official rollout, then have accounts switched on at a planned time. Let your Activation Manager know when you want them sent.

Summary

Read the instructions document, complete the branch file before the user file, and email both to your Activation Manager along with your fallback Apply Now URL. Accurate setup files mean your team's branches, permissions, and offers are correct the moment your account is live.