Users and Teams

A user is a person who signs in to the LendAPI dashboard. Everyone works inside a tenant, which is your LendAPI workspace. Each user has one role that decides what they can see and do (see Roles and Permissions).

There are three places to manage users, depending on who they work for:

Key concepts

• Role: what the user can access. Admin, Manager, Analyst, Auditor, or a custom role.
• Status: Pending (invited, has not signed in yet), active, or disabled. Disabled users cannot sign in.
• Two-factor authentication (2FA): an SMS code the user must enter after their password. Turned on for the whole workspace.

Manage your team

Open Settings → Users to see everyone on your team, with their role, last sign-in and status. You need Settings → Users at View to see this page and at Edit to make changes. User management works in Live mode; the buttons are unavailable in Sandbox mode, and changes you make are applied to both environments.

Add a user

1. Go to Settings → Users and click Add User.
2. Enter First Name, Last Name and Email. The email becomes the user's sign-in and must not already be used by another LendAPI account.
3. Enter a Phone Number. It is used for two-factor authentication codes.
4. Choose a Role: ADMIN, MANAGER, ANALYST, AUDITOR, or one of your custom roles for your team.
5. Complete any remaining required fields and save. The user receives an invitation email with a link to set their password.

The invitation link expires after one hour. If it expires, the user can use Forgot Password? on the sign-in page to get a new link.

📘

Only Admins can create Admins

A user with Settings → Users: Edit can add and edit users, but only an existing Admin can give someone the Admin role.

Edit a user

1. In Settings → Users, click Edit on the user's row.
2. Update their name, email, phone number or role, and save.

A new role applies the next time the user signs in.

You cannot change the role of the only active Admin in your workspace. Make someone else an Admin first.

Set a user's password

Click Update Password on the user's row, enter the New Password twice and save. Only Admins can set another user's password. Users can change their own password under Settings → Profile when their role has Profile at Edit. Admin, Manager and Analyst have it; Auditor has View only.

Disable or re-enable a user

Use the Status switch on the user's row. Disabling asks you to confirm with Disable, and the user can no longer sign in. Switch it back on to restore access with the same role.

You cannot disable yourself, and you cannot disable the only active Admin.

👍

Disable users who leave

Disabling keeps the user's history (notes, assignments, activity) intact and can be undone.

Sub-tenant and branch users

Manage sub-tenant users

If your workspace has sub-tenants, each sub-tenant has its own users. They sign in on the same LendAPI sign-in page but only see their own sub-tenant's data.

1. Go to Tenants and open the sub-tenant.
2. Open the Users tab.
3. Click Add User and fill in First Name, Last Name, Email, Phone Number and Role.
4. Save. The user receives an invitation email.

The Role list offers the built-in Admin and Analyst roles plus your custom roles whose Available for is Tenant. You can also edit and enable or disable sub-tenant users from the same tab.

Access to this tab is controlled by Tenants → Users in the role editor: View to see the users, Edit to add, edit, enable or disable them. Anyone with Edit can give a sub-tenant user the sub-tenant Admin role, so grant it with care. See Sub-tenants.

Branches

Branches let a sub-tenant split its work across physical or logical locations, such as stores or offices: parent tenant → sub-tenant → branch. Branches must be turned on for your workspace by LendAPI. Contact your LendAPI representative if you want to use them.

Each branch has two kinds of users, with fixed access (they do not use the role editor):

Branch users only see applications tagged to their own branch. Applications are tagged when an applicant uses the branch's product link, or when a branch user or admin creates the application and chooses the branch. They can create, edit and move applications forward, but cannot export applications or unhide masked fields.

Create a branch.

1. Go to Branches and click Add Branch.
2. Choose the sub-tenant (parent admins only), enter the branch name and optional address and point-of-contact details.
3. Enter the first Branch Manager's name and email.
4. Save. The branch is created as active, and the manager receives a Branch Invite email to set their password.

From the branch's page you can add more managers and associates, edit details, copy the branch's product links, and deactivate the branch. Deactivating a branch disables all of its users. Reactivating the branch does not re-enable them; turn users back on one by one.

A branch must always keep at least one active manager, so you cannot remove, disable or demote its last manager.

Who can manage branches is set by the Branches row in the role editor. Parent admins see every branch of every sub-tenant; sub-tenant admins see their own sub-tenant's branches.

Security and access

Two-factor authentication

When two-factor authentication is on, users get a six-digit code by SMS after entering their password and must enter it to finish signing in.

1. Go to Settings → Security.
2. Turn on Two Factor Authentication.
3. Click Save.

The setting applies to your whole workspace. Codes are sent to the phone number on the user's profile, so make sure every user has a valid mobile number. Branch users are covered when 2FA is on for the parent workspace.

Changing this setting requires Settings → Security: Edit.

API access

Team, sub-tenant and branch users are managed in the dashboard and are not part of the public LendAPI REST API. To create a sub-tenant together with its first admin user programmatically, use Create Sub Tenant; see Sub-tenants.

Required permissions

Details are in Roles and Permissions.

Best practices

• Use work email addresses. The email is the user's sign-in and cannot be shared between accounts.
• Collect phone numbers up front if you use 2FA, since codes are sent by SMS to that number.
• Disable users when someone leaves, and ask them to sign out if you change their role mid-session.
• Keep at least two Admins so one person leaving never locks you out.
• Consider single sign-on for larger teams so access is granted and removed in one place. See Single Sign-On.

Related guides