Skip to main content
Manage Team is where a company admin runs the roster: who has access to Leaf360, what role each person holds, whether their seat is paid by the company or by the person themselves, and what happens to their leads and tasks if they leave. Open it from your name at the bottom of the sidebar, then Account Settings, then User Management under the Workspace section. Only admins see that entry and can open the screen at all — anyone else who lands here sees a message saying team management is admin only.
Manage Team and Team Management are two different screens that happen to share a name pattern. Manage Team is about people: who is on the roster, their role, their seat and their login. Team Management is about grouping people into teams and routing leads, loans and contacts to them. An admin usually needs both, for different reasons.

Who this list covers

The roster is every employee assigned to this workspace — active, invited, or deactivated. Clients and real estate agent contacts are filtered out, so the list is your staff only. A legacy account with no workspace recorded on it still shows up rather than being hidden, until its assignment is corrected.

The summary cards

Three cards sit above the table: These counts cover the whole roster, not just the members currently visible on the table’s page.
Company seats and the plan breakdown only appear once billing data has loaded for your company. If it fails to load, the cards still show with a dash instead of a number, and the table drops its Billing, Workspaces, Plan and Add-ons columns until it recovers.

Filtering and searching the table

A row of small tags above the table narrows it to All Members, Active, Invited, Inactive, and, once billing data is loaded, Company Paid, Self Paid, Free, Core and Pro. Each tag carries its own count. All Members counts active and invited people together; a deactivated member isn’t hidden, it just moves to the Inactive tag. The search box beside the tags matches on name, email, phone and NMLS number, and narrows whichever tag you have selected. The table shows 25 rows at a time, with Previous and Next at the foot.

The columns

Every row shows Name, Email and phone, and Role. Once billing data has loaded, four more columns appear: Billing (Company Paid, Self Paid, Self Pay scheduled, Past due, Suspended or No seat), Workspaces (which Leaf360 products the member has access to), Plan (Free, Core or Pro), and Add-ons. The last two columns are Status and Last Active, which also shows when the account was created, and Security, which reads 2FA On or 2FA Off.

Inviting someone

Invite Team Member opens a form for one or more people at once. Each entry takes first and last name, email, mobile phone, an NMLS number, a role, and, where your company allows self-pay, whether the seat is Company Paid or Self Paid. NMLS is required for the Loan Officer and Branch Manager roles. You also pick which Leaf360 workspace the invite lands in, limited to the workspaces your company has turned on. Roles offered are Admin, Branch Manager, Sales Manager, Loan Officer, Loan Partner and Processor.
1

Add each person

Fill in one card per invitee, or click Add another team member for more. Leaf360 flags an email already on your roster, or repeated within the same batch, before you can send.
2

Confirm

Send N invitations asks you to confirm. Every invitation goes out by email immediately once you confirm.
3

Check the results

If any invitation fails, the successful ones still go out. Leaf360 shows a count of failures, and the failed entries stay in the form with their error so you can fix and resend just those.

Inviting from a spreadsheet

Import CSV lets you send the same invitations in bulk from a file. A downloadable template lists the columns Leaf360 expects: First Name, Last Name, Email, Phone, Role and Billing. Common variants of a role name, such as “LO” or “Loan Originator”, are recognized and mapped automatically, and any row Leaf360 can’t place is flagged for you to fix before sending. The send step works the same as the bulk invitation form above.

Opening a member

Click a row to open a side panel with the person’s identity, contact details, role, status and billing.
  • Identity and role — you can edit these right in the panel: first name, last name, NMLS number, phone, and role. Save changes writes them back.
  • Email is shown but not editable here. Use Change email in Quick actions to update the sign-in address. The change takes effect immediately, and the member isn’t notified automatically, so tell them yourself.
  • Billing, where available, lets you move the member between Company Paid and Self Paid. Moving someone onto a company seat takes effect immediately and may add a prorated charge if it pushes you past your purchased seats. Moving someone to self-pay is scheduled for the end of the current billing period instead of happening right away, and you can cancel the scheduled change before it lands.

Quick actions

Every action below asks you to confirm what it does before it runs.

The full profile

Click Open full profile in the side panel to leave the panel for a dedicated page with its own tabs: Personal info (name, phone, birth date, marital status, home address and an emergency contact), Employee details (department, position, NMLS ID, NMLS state, license expiry, start date and professional designations such as Loan Officer, Processor, Closer and Originator), Permissions (email verification and 2FA status, last login, and, for admins, an editable role with its own save step), and Management. The Management tab repeats the password reset and activate/deactivate controls, and adds a Danger Zone with Remove Team Member.
Removing a team member checks their assigned leads, contacts and tasks first. If they have any, you must either reassign every one of them to another team member in a single step, or remove the person without reassigning anything, which leaves those records without an owner.

Loans keep their original loan officer

Loans are deliberately left alone. They aren’t part of the check, and they aren’t part of the reassignment step. A departing loan officer stays recorded as the loan officer on every loan they originated, and removing them from your team doesn’t change that. This is intentional, and it’s worth understanding before you try to tidy it up. Your annual audit has to show who the assigned loan officer was on each loan at the time it was worked. If removing a person rewrote that field across their back catalogue, the record of who handled which loan would be gone, and the audit couldn’t be completed.
Don’t reassign historical loans to a current team member just to make a departed colleague disappear from your pipeline. The loan officer of record is audit evidence, not an assignment.
If you need someone to service a loan whose original loan officer has left, add them to the loan as a team member instead of replacing the loan officer on it. That gives them the access they need and leaves the record of who originated it intact.