Product updates and changes

1. Overview

The LOS 2.0 Dashboard is redesigned as the user’s primary operational workspace. The old dashboard mainly displayed disconnected statistics, communication counts, loan files, rates, tasks, training, and pipeline analytics. The new dashboard brings those areas together around what the logged-in user actually needs to act on.

2. Header / Global Navigation

Old LOS

The old header primarily contained utility icons, notification indicators, communication shortcuts, and the logged-in user’s avatar. Navigation was largely dependent on the left sidebar, and there was no major system-wide search experience exposed directly in the header.

LOS 2.0

The header becomes a persistent global action and navigation layer.

Global Search

A new search box is displayed prominently in the header with the prompt “Search pages, records, training, flyers & actions…”. The purpose is to let users find LOS information without first navigating into individual modules.

• Customers
• Partners
• Flyers
• Training Videos
• LOS Pages
• Available actions/features

Where applicable, selecting a result should navigate directly to the selected record or feature. A keyboard shortcut such as Ctrl + K can immediately focus or open Global Search.

Permission-aware search: Global Search only returns pages, records, and actions the signed-in user is authorized to access.

3. Header Quick Actions

LOS 2.0 keeps frequently used tools in the header so users can reach communications and utilities without leaving their current workflow.

• Information / help
• Support / headset
• Notifications
• Messages
• Communication tools
• Video
• Calendar
• Calculator / utilities
• Theme control
• User profile

Notification badges should indicate unread or pending activity. Clicking a quick-action icon should open the related module, dropdown, panel, or action.

4. Dark Mode

Dark Mode is a major LOS 2.0 interface enhancement. The header provides a theme control that allows users to switch between supported application themes.

The setting must affect the full LOS experience rather than only the Dashboard.

• Header
• Sidebar
• Dashboard
• Cards
• Tables
• Forms
• Popups and modals
• Dropdowns
• Search
• Charts
• Loan screens
• Customer and Partner screens
• PPE screens
• Task screens

Theme preference: The selected light or dark theme is retained across navigation and future sessions.

5. Logged-In User Area

The right side of the header displays the currently authenticated user, including user avatar, user name, and a dropdown control. The dropdown can expose appropriate account actions such as profile, account settings, or logout. The displayed identity must always represent the actual logged-in account.

6. Sidebar Redesign

Old LOS

The old LOS used a comparatively wide vertical sidebar containing module icons. Even in a compact visual state, it consumed more horizontal workspace than necessary.

LOS 2.0

The sidebar is significantly slimmer to maximize usable application workspace while keeping major LOS modules immediately accessible.

Sidebar States

• Visible / compact: primary navigation icons and LOS branding remain available.
• Collapsed: sidebar is reduced to an extremely narrow icon-based navigation rail.
• Fully hidden: the user can hide the sidebar completely when maximum screen space is needed. A restore control remains available.

Navigation Behavior

The currently selected module should be visually highlighted. When the sidebar is compact, hovering over an icon should show the module name through a tooltip or similar UI.

Permission Handling

Sidebar modules must be permission-driven. If a user cannot access a module, it should normally not be shown rather than allowing the user to click into an access error.

7. Dashboard User Greeting

A new personalized welcome panel is shown at the top of the Dashboard. It displays a time-sensitive greeting, the logged-in user’s name, current date, and current time, reinforcing that the Dashboard is a user-specific operational workspace.

• Good Morning
• Good Afternoon
• Good Evening

8. My Data

A My Data action is available from the greeting area to provide quick access to information associated with the logged-in user.

My Data: Provides quick access to information connected to the signed-in user and their work.

9. Ad Approval

Old LOS

Advertisement approval was handled inside the Employee section, which forced administrators to enter employee management for an operational approval task.

LOS 2.0

Ad Approval moves directly to the Dashboard so authorized administrators can access advertisements awaiting approval from their daily workspace.

Access Rules

• Visible only to administrator accounts or users explicitly granted Ad Approval permission.
• Unauthorized users must not see the Dashboard action.
• The underlying page/API must also enforce authorization; hiding the button alone is not sufficient.

10. Dashboard Summary Cards

LOS 2.0 introduces a cleaner set of high-level cards that summarize the logged-in user’s workload and business activity. The values should reflect the correct user, team, branch, or organizational scope according to permissions.

11. Customers

Displays the relevant customer count and, where applicable, a secondary trend or percentage indicator. The count must use an agreed customer-status definition rather than simply counting every historical customer record.

12. Pipeline Volume

Pipeline Volume is a new consolidated Dashboard metric. It represents the monetary volume associated with the user’s active loan pipeline and replaces the need to treat Prospect and Processing as disconnected top-level concepts.

The metric should be calculated from the loan amounts of applicable active files across the defined pipeline stages.

Pipeline Volume: Summarizes active pipeline loan amounts from Prospect through Clear to Close while excluding inactive, cancelled, closed, denied, and withdrawn files.

13. Tasks Due

Displays the number of tasks that currently require the logged-in user’s attention. A secondary value can show overdue items. The number must be calculated from the new Tasks system rather than maintained as a separate Dashboard-only counter.

14. POS Applications

Displays Point-of-Sale application activity and should route the user to the relevant POS application list when selected. Scope should follow the user’s permissions and organizational access.

15. Communication Summary Cards

LOS 2.0 retains key communication metrics in a cleaner card layout.

• Email
• SMS
• Calls
• Video
• Internal

Each card can display unread, total, inbound, or usage values as appropriate for that communication channel. Selecting a card should open its corresponding communication module when applicable, and badges can identify new or unread items.

16. Pipeline Overview

The old pipeline analytics widget is replaced with a more operational Pipeline Overview that presents files by real mortgage pipeline stage.

• Prospect
• Processing
• Submitted
• Approved
• Clear to Close
• Underwriting

The Dashboard displays a count for each stage together with a supporting chart and legend so users can quickly understand pipeline distribution and movement.

17. Pipeline Date Filters

Users can filter Pipeline Overview by predefined time periods. The current design includes:

• This Week
• This Month
• Last 3 Months
• This Year

Changing the filter must update all Pipeline Overview elements consistently, including stage counts, chart data, legend/summary values, and any derived totals. The active period must be visually clear.

18. Attention Required

Attention Required is a major new LOS 2.0 Dashboard feature. It proactively surfaces prospect or loan files that cannot progress normally because an item requires user action.

• Outstanding conditions
• Missing required items
• Pending documentation
• Incomplete prospect requirements
• File items requiring action

Each item should identify the issue, affected file or item count, severity/priority, and a relevant action. Selecting the action should take the user directly to the affected file or required item rather than only to a generic list.

Priority / Severity

• High
• Medium
• Low

View All

View All opens the complete list when more Attention Required items exist than should be displayed on the Dashboard.

19. My Loans

The old generic Loan Files widget is replaced by My Loans. The new section is explicitly user-oriented and shows active loan files relevant to the logged-in user rather than an uncontrolled company-wide list.

Displayed Information

• Borrower
• Loan #
• Loan Amount
• Status
• Next Milestone
• Additional Actions

Selecting a loan opens the corresponding loan file. View All opens the user’s full applicable active-loan list.

User-focused view: My Loans follows the signed-in user’s permitted workspace and only surfaces loan files available within that scope.

20. Live Rates

Live Rates remain visible on the Dashboard but are now connected directly to the LOS 2.0 PPE / Pricing Engine. This removes duplicate rate maintenance and establishes PPE as the source of truth.

Displayed Information

• Product
• Rate
• Rate Change
• Last Updated Time

Examples

• Conforming 30Y Fixed
• FHA 30Y Fixed
• VA 30Y Fixed
• Home Ready 30Y Fixed
• Home Possible 30Y Fixed

Rate movement should be visually indicated, and users can refresh the displayed rates where appropriate. The interface should show when pricing data was last updated.

Connected pricing: Dashboard Live Rates are supplied directly by PPE so users see the same pricing used in the pricing workflow.

21. Today

The Today section is directly connected to the new LOS 2.0 Tasks and Reminder functionality. It acts as a daily schedule summary rather than a separate Dashboard-only task list.

• Tasks
• Reminders
• Meetings where supported
• Recurring items where supported

Creating, completing, or modifying an item in the Tasks/Reminder area must be reflected in Today automatically. When there is no activity, a clear empty state such as “No due Tasks, Meetings or Recurring items” should be displayed.

22. Recent Training

Recent Training replaces the older large training-video widget with a more compact experience that keeps learning content accessible without consuming excessive Dashboard space.

• Video thumbnail
• Duration
• Training title
• Date
• Category / type
• Progress
• Current item / total item count

Users can move through recent items and select training content to open it. View All opens the complete Training section.

23. Recent Loan Files

LOS 2.0 introduces a compact Recent Loan Files section. This serves a different purpose from My Loans: My Loans represents the user’s active operational pipeline, while Recent Loan Files provides quick access to files recently interacted with or updated.

• Borrower
• Loan number
• Status
• Additional action menu

Recent activity: Recent Loan Files are organized around recent access or meaningful file activity for faster return to active work.

24. Dashboard Personalization and Scope

The Dashboard must derive data according to the current user context and access model.

• Logged-in user
• User role
• Permissions
• Assigned loans
• Assigned prospects
• Administrative access

This is necessary to prevent the Dashboard from exposing organization-wide loan, customer, or partner information to users whose permissions are narrower elsewhere in LOS 2.0.

25. Dashboard Data Refresh

Dashboard information should remain reasonably current. Changes performed elsewhere in LOS 2.0 should become visible on the Dashboard without requiring the user to sign out and sign back in.

• Customers
• Pipeline volume
• Tasks
• POS applications
• Communications
• Pipeline stages
• Attention Required
• Loans
• PPE rates
• Today items
• Recent files

26. Empty States

Every Dashboard component must have a clear empty state rather than showing broken tables, null values, 0/0 placeholders, or indefinite loading indicators.

27. Loading and Error Handling

Each Dashboard widget should load and fail independently. A failure in one subsystem must not make the entire Dashboard unusable.

For example, if PPE rates fail to load, Live Rates should show its own retry/error state while My Loans, Tasks, communications, and other widgets continue to function normally.

28. Responsive Behavior

The Dashboard must adapt cleanly to different screen sizes while retaining access to critical actions.

• Cards may stack on smaller screens.
• Tables may become horizontally scrollable or convert to compact cards.
• Sidebar can collapse or hide.
• Header actions may consolidate.
• Global Search must remain accessible.
• Critical actions must not disappear solely because screen width is reduced.

29. Major Old LOS → LOS 2.0 Changes

1. Overview

The Communication module remains the central LOS area for borrower, customer, team, and external communications. LOS 2.0 retains the existing communication channels but replaces the fragmented legacy experience with a more consistent workspace-oriented interface and adds meaningful functional improvements, especially in SMS and Email.

The 2.0 update combines new communication capabilities with a consistent UI/UX refresh while preserving existing communication history, ownership, and access controls.

2. Communication Scope

• Calls and call history.
• SMS/text messaging.
• POS Loan Chats.
• Email.
• Internal team Chat.
• Video recordings and video calls.
• Workspace/team/inbox context and related permissions.

3. Communication Experience

• Consistent page headers with icon, title, and short description.
• Workspace or Team selector where the channel supports scoped communication.
• Consistent search, filters, reset/apply controls, pagination, and empty states.
• Split-screen layouts where conversation context benefits from keeping the list and active item visible at the same time.
• No channel should require a filter merely to display the default available data.
• Loading, error, and empty states should be handled per channel without breaking the complete Communication area.
• All communication records must respect role, team, workspace, assigned number, mailbox, customer, and loan access rules.

4. Calls

4.1 Old LOS Behavior

The legacy Calls section included Internal, Incoming, Outgoing, Missed, Voicemail, and Company Voicemail tabs, plus search and date filters. Records were shown in a basic table with date, caller/callee information, duration, and recording details. A key usability weakness was that users often had to define date filters before useful records appeared.

4.2 LOS 2.0 Changes

• Modern Calls header and workspace selector.
• Summary cards for Total Calls, Incoming, Outgoing, and Missed Calls.
• Retains Internal, Incoming, Outgoing, Missed, Voicemail, and Company Voicemail categories.
• Search supports values such as name, number, or notes.
• From and To date controls remain available but act as optional filters rather than prerequisites for viewing data.
• Dedicated Show Missed toggle, Reset action, and Apply action.
• Table displays Date, From, To, Duration, Recorded File, and Actions.
• Proper empty state displays when no records match the current view or filters.
• Pagination and rows-per-page controls are standardized with the new LOS 2.0 table pattern.

4.3 Calls Behavior

• Default view should show the user-accessible call records for the defined default period or data scope without requiring manual date entry.
• Summary card totals must match the underlying call records for the same workspace/user scope.
• Recorded files must only be accessible to users authorized to access the related call.
• Reset must restore the defined default Calls view and remove user-applied filters.

5. SMS

SMS receives the largest communication workflow expansion in LOS 2.0. The new screen uses a split-screen inbox layout with a conversation list on the left and the selected thread on the right, while adding substantially richer message composition and conversation management tools.

5.1 SMS Inbox and Conversation Management

• Inbox/phone-number selector lets a user switch between permitted SMS numbers or inboxes.
• New Conversation action is immediately available above the conversation list.
• Search supports contact discovery within the SMS workspace.
• Conversation filters include views such as All, Unread, Favorites, and Main.
• Conversation list supports pagination and clearly indicates the selected thread.
• Conversation-level actions can include calling, filters/options, and deletion where permitted.
• Users can pin important content or conversations where pinning is available.

5.2 SMS Templates and Variables

• Users can insert approved/reusable SMS templates.
• Templates may contain supported merge variables such as customer or contact name.
• Variable values must resolve from the selected customer/contact context at send time.
• Unresolved variables should be validated before transmission to avoid sending raw placeholder text unintentionally.
• Template usage must not bypass user permissions or compliance controls that apply to manually typed SMS.

5.3 Voice Notes and Attachments

• Users can send voice notes from the SMS compose area.
• Users can attach/share files through link-based attachment behavior.
• Generated attachment links must respect security, access duration, and customer-facing availability rules.
• Unsupported or oversized files should produce a clear validation message instead of silently failing.

5.4 Scheduled SMS

LOS 2.0 adds the ability to schedule an SMS for future delivery rather than sending it immediately. Scheduled messages should remain associated with the originating conversation and sending number.

• User chooses a future send date/time.
• Scheduled message is stored with a pending/scheduled state until delivery.
• System should prevent scheduling in the past.
• Delivery failures should be surfaced to the sending user according to normal SMS delivery handling.
• Scheduled messages stay tied to the originating conversation, sender number, and configured account timezone.

5.5 Additional SMS Composer Features

• Emoji support.
• eCard option where enabled.
• Character/SMS segment counter.
• Send action and related send options.
• Attachment control and voice-note/microphone control.
• Scheduling control integrated into the compose area.

6. POS Loan Chats

6.1 Purpose

POS Loan Chats remain dedicated to messages from customers using the POS portal. Unlike general SMS or Internal Chat, each conversation must preserve borrower and loan context.

6.2 LOS 2.0 Changes

• Modern split-screen layout with conversation list and active thread.
• Search by loan or customer.
• Conversation views such as All, Unread, and Open.
• Loan/customer card displays context such as customer name, loan number, and applicable status.
• Conversation header and message thread are visually standardized with the rest of LOS 2.0.
• Thread-level search, attachment, and additional actions are available where permitted.

6.3 POS Chat Behavior

• Messages must remain linked to the correct POS customer and loan.
• A user cannot access a POS loan chat solely because they can access the Communication module; loan/workspace permissions still apply.
• Unread/Open indicators must reflect actual conversation state rather than visual-only labels.

7. Email

7.1 Split-Screen Email Experience

LOS 2.0 replaces the legacy email list-centric view with a split-screen email client. The message list remains visible while the selected email opens in a reading pane, reducing navigation and preserving context.

• Left-side message list with search and pagination.
• Right-side message reading pane.
• Selected message is clearly highlighted.
• Message toolbar includes actions such as Forward, Reply, Reply All, Label As, Move To, Trash, and additional options.
• Mailbox/folder navigation remains available through the redesigned interface.
• Team selection remains available where mailbox/team access is supported.
• External-email warning banner identifies messages originating outside the organization where applicable.

7.2 Compose Drawer

New Email no longer opens in the older popup-style compose experience. Selecting Compose opens a dedicated drawer, allowing the user to write a message without losing the email reading context.

• To field with name/email entry.
• Subject field.
• Email Profile/account selection.
• CC and BCC support.
• Secure Email toggle where enabled.
• Rich-text editing and formatting tools.
• Signature/branding support.
• Select Attachment control.
• Drag-and-drop attachment area.
• Send, Draft, Clear, Minimize, and Close actions are available within the compose experience.

7.3 Email Security and Permissions

• Users may only send from email profiles/accounts they are authorized to use.
• Moving, labeling, deleting, or forwarding messages must operate against the selected mailbox/account only.
• External-message warnings are informational and must not be removable in a way that creates a misleading internal-origin appearance.
• Attachments must follow file security, size, and malware scanning rules already defined by the organization/platform.

8. Internal Chat

Internal Chat is redesigned as a team collaboration workspace while retaining direct employee-to-employee messaging.

• Search users.
• Recent Chats view.
• Online/offline presence indicators.
• Create Group action for group conversations.
• Modern conversation list with avatars and latest-message preview.
• Selected chat header with participant/status information.
• Message thread with sent/read state where supported.
• Attachment control and communication shortcuts such as video/meeting actions where enabled.
• Workspace scoping continues to apply.

8.1 Group Chat Rule

Creating a group must not grant access to users outside the creator's permitted organizational/workspace scope. Group membership, participant removal, history visibility, and group deletion/archival should follow defined permission rules.

9. Video

9.1 Existing Functional Scope

• Video Recording.
• Video Calls.
• Search and optional date filtering.
• Send recording by SMS or email where enabled.
• View recording.
• Open/share link.
• Copy link.
• Delete recording where permitted.
• View counts, date, and status.

9.2 LOS 2.0 Usability Change

The most important behavioral improvement is that available Video data should display without forcing the user to enter a From/To date range first. Date filters refine the result set; they are no longer a prerequisite for basic visibility.

This same principle applies to Calls: filters should narrow data, not act as a gate that prevents users from seeing normal default records.

10. Workspace, Team, Inbox, and Permission Scope

Communication data can be sensitive and must remain scoped by the combination of authenticated user, selected workspace/team, assigned communication account/number, and access to the underlying customer or loan where applicable.

• My Workspace and Select a Team controls must only expose scopes the user is authorized to access.
• SMS inbox/phone-number selector must only show numbers assigned or shared with the user/team.
• Email profiles/mailboxes must only show accounts the user can access.
• POS Loan Chats additionally require appropriate access to the related borrower/loan.
• Internal Chat user discovery and group creation must follow organizational/workspace visibility rules.
• Server-side permission validation is required; hiding a selector or button is not sufficient security.

11. Search, Filters, and Default Data Behavior

Search and filtering have been standardized to reduce unnecessary steps. The default state should be useful on first load rather than an empty screen that only becomes meaningful after filters are supplied.

• Search should act on the current channel and current permitted scope.
• Applying filters updates the corresponding list/table without changing authorization scope.
• Reset/Clear returns the current channel to its defined default state.
• Date ranges are optional unless a specific compliance or performance rule requires a bounded default period.
• Pagination and rows-per-page should preserve active filters where practical.
• Empty states should explain whether no data exists or no data matched the current filters.

12. What Changed

13. Old LOS vs. LOS 2.0 Comparison

14. Empty, Loading, and Error States

• Calls: No call records found when the current scope has no matching records.
• SMS: No conversations found / no messages yet as appropriate.
• POS Loan Chats: No POS conversations available or no conversation selected.
• Email: No messages found or no message selected.
• Chat: No recent chats / no selected participant as appropriate.
• Video: No recordings/calls found for the current scope.
• A failure in one channel should not prevent unrelated communication channels from loading.
• Retry guidance should be offered for recoverable service or network failures.

15. Audit & Activity

Because Communication contains customer-facing and internal communications, important actions should remain auditable according to existing LOS compliance requirements.

• Message send time and sender identity.
• Scheduled SMS creation, modification, cancellation, and send result where supported.
• Email sender profile and recipient details.
• Call/recording metadata and access where required.
• POS borrower message association with the related loan.
• Deletion actions where retention rules allow deletion.
• Group-chat creation and membership changes where required by organizational policy.

1. Overview

The CRM remains the LOS system of record for customer relationships, business partners, employees, and recruitment contacts. LOS 2.0 does not replace these workflows; it reorganizes how the same information is presented and managed so that users can understand record status faster and perform routine actions with less visual clutter.

The 2.0 CRM keeps existing validation, ownership, permissions, import/export behavior, communication actions, and record lifecycle logic while presenting the data in a cleaner and more consistent experience.

Change classification: CRM in LOS 2.0 is a UI/UX redesign with data-summary enhancements. Summary cards and grouped tables are derived views of existing CRM records; they are not separate sources of truth or new workflows.

2. CRM Scope

• Customers - customer/prospect/lead/application relationship management.
• Partners - lenders, realtors, accountants, vendors, and other business relationships.
• Employees - employee records, licensing, compliance, employment, package, status, and location information.
• Recruitment - recruitment contacts and recruitment status tracking.
• Shared CRM behaviors - workspace scope, search, filters, imports/exports/templates, pagination, record actions, permissions, empty states, and summary cards.

3. CRM Experience

• Each CRM page uses a consistent header with module icon, title, explanatory subtitle, and My Workspace selector where applicable.
• Summary cards appear below the header to provide high-level counts before the detailed table.
• Search and filters are consolidated into a single toolbar and use consistent styling across CRM areas.
• Tables use grouped information, avatars/initials, status pills, icons, and simplified action controls to reduce horizontal clutter.
• Tables provide consistent pagination, current record count, current page, and selectable page size where supported.
• Empty results show a clear empty-state message and guidance rather than an unexplained blank table.
• All counts, filters, and tables must derive from the same underlying records and workspace/permission scope.
• Existing CRM functions must remain available unless explicitly relocated, such as Ad Approval.

4. Customers

4.1 Old LOS Behavior

The legacy Customers screen was predominantly a large table with Search, Group, Status, Source, Assigned, Template, contact import/export, and New actions. Customer details such as first name, last name, email, phone, status, owner, and assigned state were spread across independent columns, with small row-action icons for email, chat, edit, and delete.

4.2 LOS 2.0 Customer Summary

• Total Customers - total registered customers in the current permitted scope.
• Prospects - customer records currently categorized as prospects.
• Leads - customer records categorized as qualified leads according to existing CRM status rules.
• Applications - customer/application records represented by the existing application relationship logic.

These cards are summary views of CRM data. Unless separately configured, they should not create a new customer state or separate workflow. Card totals must always reconcile with the underlying CRM records for the same workspace and permissions.

4.3 Customer Search, Filters, and Actions

• Search supports customer-identifying information such as name, email, or phone.
• Group and Status filters remain available in a cleaner toolbar.
• Assigned / Only Assigned control allows users to limit results to records assigned according to existing ownership rules.
• Reset clears user-applied filters and restores the defined default customer view.
• Template, Import, Export, and New Customer actions remain available subject to existing permissions.

4.4 Customer Table Redesign

• Customer column combines avatar/initials, customer name, and customer ID.
• Contact column groups available email and phone information.
• Status is displayed using a clearer status indicator/badge.
• Owner is displayed with a compact identity treatment.
• Assigned status is displayed in a dedicated, readable column.
• Actions remain available for email, chat/message, edit, and delete according to permissions.

5. Partners

5.1 Old LOS Behavior

The legacy Partners screen used a very wide table with fields such as Company, AE, Email, Cell Phone, Fax, FHA ID, VA ID, USDA ID, and row actions. Search, Group, Category, Source, Template, Contacts/import tools, and New were displayed above the table.

5.2 LOS 2.0 Partner Summary

• Lenders - lending relationships.
• Realtors - real estate partner relationships.
• Accountants - accounting partner relationships.
• Vendors - vendor relationships.

Partner summary cards are derived from existing partner category/group data and do not create new partner types beyond the configured CRM categories.

5.3 Partner Search, Filters, and Actions

• Search supports company, contact name, email, or phone.
• Group and Category filters remain available and are presented in a consistent toolbar.
• Template, Import, New Partner, and Reset actions remain available based on the existing permission model.
• Any existing export/download behavior required by the prior workflow must remain available even if the control location changes.

5.4 Partner Table Redesign

• Core table columns are simplified to Company, AE, Email, Cell Phone, Fax, and Actions.
• Company and AE information use compact identity/icon treatments for faster scanning.
• Missing values should display a consistent placeholder such as N/A rather than leaving ambiguous blank cells where practical.
• Row actions include existing communication and maintenance operations such as email, chat/message, edit, call, and delete according to permissions.
• Detailed regulatory identifiers and other partner fields remain part of the partner record even if they are not all exposed as top-level table columns.

6. Employees

6.1 Old LOS Behavior

The legacy Employees screen exposed many independent filters and columns, including Role, Status, Classification, Package, AML/BSA, State, Source, NMLS ID, work and personal email, phone, state approval, AML/BSA, package, joining date, classification, status, and location. This preserved detail but made the table difficult to scan and forced extensive horizontal information density.

6.2 LOS 2.0 Employee Summary

• Total Employees - all registered employees in the current permitted scope.
• Active - employees currently marked active by the existing status logic.
• Pending - employees awaiting activation or completion according to existing employee status rules.
• AML Approved - employees whose AML/BSA state is approved according to existing compliance data.

6.3 Employee Search and Filters

• Search supports employee-identifying values such as name, email, and NMLS.
• Role, Status, Classification, Package, AML/BSA, and State filters are presented in a single organized toolbar.
• New Employee remains available to authorized users.
• Reset clears applied filter criteria and restores the default employee view.

6.4 Employee Table Redesign

• Employee combines avatar/initials, employee name, and job role/title.
• Licensing groups NMLS ID and state licensing/approval information.
• Emails groups work and personal email information.
• Phone displays the employee phone number in a compact form.
• Compliance groups AML/BSA status and Package information.
• Employment groups classification (for example Employee or Contract) and joining date.
• Status uses a clear active/pending/inactive presentation.
• Location displays the employee location in a dedicated column.
• Actions retain existing email, chat/message, edit, call, and delete capabilities according to permissions.

6.5 Employee Data Preservation

Grouping fields in the new table is a presentation change only. It must not remove or alter underlying employee attributes. Detailed fields that are no longer shown as standalone columns must continue to be stored, editable, searchable/filterable where applicable, and available in the employee detail/edit experience.

7. Ad Approval Relocation

Cross-module change: Ad Approval was previously exposed from Employees. In LOS 2.0 it is removed from the Employee CRM toolbar and surfaced on the Dashboard for authorized administrator accounts. This is a workflow-location change, not a new CRM feature.

• Normal users must not see or access Ad Approval from Employees.
• Authorized administrators access the approval workflow from the Dashboard.
• The underlying page/API must still enforce authorization; hiding the button alone is not sufficient.
• Moving the entry point must not change existing advertisement approval records, statuses, or audit history.

8. Recruitment

8.1 Old LOS Behavior

The legacy Recruitment screen provided Search, Source, Status, Template, Download Existing Contacts, Import Contacts, New, and a simple table with Name, Email, Cell Phone, and Status. Functionality was limited but sufficient for maintaining recruitment contacts.

8.2 LOS 2.0 Recruitment Summary

• Total Contacts - recruitment contacts in the current scope.
• Prospects - recruiting prospects according to existing recruitment status logic.
• Hired - contacts marked hired according to the current workflow.
• Dead - contacts marked dead/closed according to the existing status model.

8.3 Recruitment Search and Actions

• Search supports name, email, or phone.
• Status filtering remains available in a simplified toolbar.
• Template, Download Existing, Import, New, and Reset actions remain available according to existing permissions.
• No new recruitment lifecycle or automation is introduced by this redesign.

8.4 Recruitment Table and Empty State

• Table remains focused on Name, Email, Cell Phone, Status, and Actions.
• When no records match the current scope or filters, the page displays a clear empty state such as No recruitment contacts found.
• Empty-state guidance may prompt the user to change search or filters rather than showing a blank data region.
• Pagination and page-size controls follow the shared LOS 2.0 CRM pattern.

9. Summary Card Rules

Summary cards are calculated from the same CRM records and workspace scope as the detailed tables, keeping high-level counts and record views aligned.

• Counts update when underlying records are created, edited, reassigned, or change status.
• Counts respect the current workspace and user permissions.
• Counts must not include records that the user is not permitted to see.
• A record should not be double-counted unless the existing business model intentionally permits overlapping categories.
• Clickable summary cards open a filtered view that matches the count shown on the card.

10. Search and Filter Behavior

• Search terms should apply to the record types and fields described for each CRM area.
• Filters should combine predictably using the existing CRM query logic.
• Reset should remove only user-applied criteria and return to the defined default workspace view.
• Changing workspace should refresh cards, filters/results, and tables consistently.
• Search/filter results must preserve permission boundaries and cannot be used to discover inaccessible records.
• Filter controls should not be required simply to display default data.

11. Import, Export, and Templates

LOS 2.0 retains existing data-management workflows. The redesign may reposition or rename controls for clarity, but it must preserve current validation and file-processing behavior unless separately specified.

• Template provides the correct import template for the current CRM record type where supported.
• Import continues using existing validation and duplicate-handling rules.
• Export/Download Existing continues to respect workspace and permissions.
• Import/export operations should report validation failures clearly and must not silently drop invalid rows.
• No redesign control may expose organization-wide data to users who previously had only assigned/workspace-scoped access.

12. Pagination, Empty States, and Table Usability

• Show the number of displayed records and total available records where supported.
• Show current page and total page count.
• Allow page-size selection where applicable.
• Keep table headers readable and aligned while scrolling large record sets.
• Use clear empty states for zero records or zero search results.
• Row action buttons should remain consistently positioned and should not shift unpredictably based on missing data.
• Long values should wrap, truncate with a tooltip, or otherwise remain readable without breaking the table layout.

13. Workspace and Permissions

My Workspace provides a common context for CRM data. It is a presentation/scope control and does not replace the existing authorization model.

• Workspace selection may change which records and summary counts are displayed according to existing access rules.
• Users must not gain access to records solely by switching workspace.
• Create, edit, delete, import, export, communication, and employee-administration actions remain permission controlled.
• Unauthorized actions should be hidden or disabled in the UI and rejected by server-side authorization if invoked directly.
• Assigned-only customer behavior must remain consistent with ownership/assignment permissions.

14. Old CRM vs. LOS 2.0

1. Overview

The Design Center remains the LOS marketing workspace for reusable templates, campaign content, and campaign-performance visibility. LOS 2.0 does not replace the existing marketing model. Instead, it reorganizes the same capabilities into a more coherent and easier-to-use interface.

The 2.0 Design Center keeps existing content records, template categories, visibility rules, ordering, campaign metrics, send statuses, permissions, and approval behavior while introducing the new interface.

What changed: Design Center receives a complete UI/UX refresh while its existing campaign and template workflows remain available.

2. Functional Scope

• Design Center / Marketing Template Library
• Drip Campaign Center
• Campaign Tracking
• Shared Design Center behaviors such as workspace scope, permissions, search, pagination, visibility controls, actions, and empty states.

3. Design Center Experience

• Every major page uses a consistent LOS 2.0 header with icon, title, subtitle, and workspace context where applicable.
• Primary actions are placed in clear, consistently styled buttons rather than scattered across the screen.
• Cards use consistent spacing, titles, category/status indicators, and action controls.
• Search and category navigation are prominent and positioned before the content grid or table.
• Pagination and record-count information clearly communicate the current result set.
• Empty or unavailable previews show explicit fallback states instead of broken/blank visual areas.
• Existing permissions continue to control create, edit, preview, hide/show, delete, upload, tracking, and approval actions.
• Workspace selection changes scope only according to the existing access model and must not bypass record-level permissions.

4. Design Center - Marketing Template Library

4.1 Old LOS Behavior

The old marketing-template library presented a dense grid of flyer/e-card templates with upload controls, category tabs, search, page navigation, and row/card actions. The underlying functions were available, but category navigation, paging, visual consistency, and action placement were less structured.

4.2 LOS 2.0 Page Structure

• Clear Design Center title and description identify the page purpose.
• My Workspace selector appears in the page header where applicable.
• Primary controls include Upload Flyer, Upload Postage, additional options, and Ad Approval for authorized users where retained.
• Search and template-category controls are grouped in a dedicated navigation/filter row.
• Template results appear in a modern grid with clear card boundaries and consistent actions.
• Grid/list display controls and pagination are surfaced in a consistent toolbar.

5. Template Categories

The same marketing-content categories remain available, but they are easier to identify and switch between in LOS 2.0.

• E-Card
• Open House
• Memorable
• Products
• Recruitment
• Info
• Religion
• Market Insights
• Postages

Category navigation changes the visible result set but does not create a new category model. Existing category assignments and template records remain the source of truth.

6. Template Search and Result Count

• Users can continue to search existing marketing templates.
• Search is positioned prominently next to category navigation for easier discovery.
• The result area clearly communicates the visible range and total number of templates, for example, Showing 1-9 of 13 templates.
• Search, category selection, workspace scope, and permissions must be applied consistently to the result count and displayed cards.

7. Template Cards

• Each card shows the available template preview.
• A category indicator identifies the template type where applicable.
• Template name/title remains visible below the preview.
• Existing actions remain available for Edit, Preview or visibility behavior, and Delete.
• A missing or unavailable preview must show an explicit placeholder such as Preview unavailable rather than a broken image.
• Deleting or changing visibility must affect the same underlying template record used by the old Design Center.

8. Grid/List View and Pagination

• Users can switch between supported grid and list presentations where implemented.
• Changing presentation mode must not change the underlying result set.
• Pagination clearly displays current page and total pages and provides Previous/Next controls.
• Page changes must preserve the active search/category/workspace context unless the user resets it.
• Disabled Previous/Next states should be visually obvious when the user is at the first or last page.

9. Upload Flyer and Upload Postage

Upload Flyer and Upload Postage remain existing workflows. LOS 2.0 improves action placement and visual consistency rather than redefining the upload business process.

• Existing file-type and validation rules remain in force.
• Existing permissions continue to determine who can upload content.
• Successful uploads should appear in the correct category/workspace according to existing rules.
• Upload failures should provide a clear error state without affecting unrelated templates.

10. Ad Approval Entry Point

Authorized users can reach Ad Approval from the redesigned experience, with Dashboard and Design Center entry points connected to the same approval queue.

One approval workflow: Dashboard and Design Center shortcuts use the same approval queue, permissions, and advertisement status records.

11. Drip Campaign Center

11.1 Old LOS Behavior

The legacy Drip Campaign Center already allowed users to manage marketing content by type, reorder content groups, create new content, control visibility, edit or delete items, and open engagement data. The main issue was visual density and inconsistent presentation across content columns.

11.2 LOS 2.0 Redesign

• The page uses a consistent header with Drip Campaign Center title, description, New Content, and Engagement actions.
• Content types are separated into modern card-based columns with cleaner spacing and stronger visual hierarchy.
• Counters are displayed prominently for each content type.
• Up/down ordering controls remain visible and use consistent styling.
• Content lists remain independently scrollable where needed.
• Item actions use consistent Edit, Preview/Visibility, and Delete controls.
• Hidden state is surfaced as a clear badge rather than relying on subtle styling.

12. Drip Campaign Content Types

Existing content types remain part of the campaign model. The UI may show only the content types relevant to the current configuration or workspace.

• Image Content
• Flyer Content
• SMS
• Email where configured/available
• HTML Content
• Religion content
• Customer content
• Prospect content where configured/available

No new content type should be inferred solely from visual treatment. Existing configuration and records determine which categories appear and how they behave.

13. Content Counters and Limits

Content columns continue to display counters such as 7/12 or 4/12. These counters must represent the same existing content-count or capacity rules used by the campaign engine.

• The numerator reflects the current applicable item count according to existing business logic.
• The denominator reflects the configured limit or applicable capacity rule where one exists.
• Counts must update after content is added, deleted, or moved in/out of the applicable category.
• If a category uses an unlimited model, the UI may display an infinity/unlimited representation as already supported.

14. Content Cards and Visibility

• Content cards display a thumbnail/icon, content title, visibility state, and applicable actions.
• Existing Hidden/Visible behavior remains unchanged from the prior system.
• Preview/visibility controls must operate on the same content record and must not create duplicate copies.
• A Hidden item remains available for management but should not appear in customer-facing campaign delivery where the existing campaign rules exclude hidden content.
• Delete behavior must continue to use the existing confirmation and permission model.

15. Reordering Content

The existing up/down ordering controls remain available. LOS 2.0 standardizes their visual presentation but does not redefine campaign sequencing.

• Move-up and move-down actions modify the existing stored display/sequence order.
• The new order should persist after refresh and across sessions according to existing behavior.
• Users without content-management permission must not be able to reorder items through direct requests or manipulated URLs.

16. New Content

New Content remains the entry point for adding applicable drip-campaign content. The redesign changes how the action is surfaced but should preserve existing creation rules, validations, categories, and permissions.

17. Engagement

The Engagement action remains a navigation point into campaign-performance information. It should continue to use the existing campaign tracking records rather than maintaining a separate analytics dataset.

18. Campaign Tracking

18.1 Old LOS Behavior

Campaign Tracking already provided sent/pending/failed totals, campaign counts, channel totals, campaign-performance charts, communication-method breakdown, and an engagement-detail table. LOS 2.0 retains those concepts while modernizing the dashboard presentation.

18.2 Summary Cards

• Sent - campaigns/messages successfully sent according to existing tracking rules.
• Pending - campaigns/messages waiting to be sent or processed.
• Failed - campaigns/messages with failed delivery/processing state according to existing rules.
• Campaigns - applicable campaign count.
• Email - applicable email campaign/message count.
• SMS - applicable SMS campaign/message count.

All summary values must be calculated from the same campaign dataset and workspace/user scope as the detailed chart and engagement table.

19. Campaign Performance Chart

• The chart continues to visualize campaign activity over time.
• Existing series such as Sent, Pending, and Failed remain represented.
• The chart must reconcile with the summary-card totals for the same selected scope/time logic.
• Periods with no data should display zero values cleanly rather than broken or missing axes.

20. Communication Method Breakdown

The existing channel distribution is now presented through a cleaner donut chart and supporting channel cards.

• Email
• SMS

The breakdown must be derived from the same campaign records as the campaign totals. A channel total of zero should display as zero without misleading chart percentages.

21. Campaign Engagement Details

The engagement table remains the detailed operational view behind the high-level metrics.

• Campaign Name
• Status
• Source
• Created At
• Sent At

Where the table supports additional views or filters, they should operate on existing campaign records and preserve the same status semantics used by the summary cards.

22. Campaign Status Presentation

• Sent
• Pending
• Failed

LOS 2.0 uses clearer pills/badges for status presentation. Color must supplement the written status rather than replace it so that the table remains understandable for all users.

23. Workspace Scope

Design Center and Campaign Tracking surface My Workspace as a consistent scope selector. Workspace selection must use the existing ownership/access model.

• Changing workspace updates applicable templates, campaigns, or tracking data according to current access rights.
• Workspace switching must not reveal unauthorized records.
• Counts, charts, result totals, and details must all use the same active workspace scope.
• Direct API/page access must enforce the same permissions as the visible selector.

24. Access & Security

• Create/upload permission controls Upload Flyer, Upload Postage, and New Content access.
• Edit permission controls changes to templates and campaign content.
• Visibility-management permission controls hide/show operations where applicable.
• Delete permission controls destructive actions.
• Tracking permission controls access to Campaign Tracking and engagement details.
• Ad Approval remains restricted to authorized administrative users according to the approval permission model.
• UI hiding is not sufficient; backend endpoints must enforce the same authorization rules.

25. Empty, Loading, and Error States

• No templates found - shown when search/category/workspace filters return no templates.
• No campaign content available - shown when a content category has no records.
• No campaign tracking data available - shown when analytics scope has no campaign data.
• Preview unavailable - shown when a template preview cannot be generated or does not exist.
• Loading should be localized so one failing widget or content column does not blank the entire page where practical.
• Errors should provide retry or recovery guidance without altering unrelated records.

26. Accessibility and Responsive Behavior

• Category and action controls should be keyboard accessible and include understandable labels/tooltips.
• Status/visibility states must be communicated with text or icons in addition to color.
• Template cards should reflow appropriately on smaller screens rather than becoming clipped.
• Scrollable content columns should retain usable controls at common desktop resolutions.
• Charts should include textual totals/legends so information is not dependent on visual color alone.
• Grid/list controls should expose a clear selected state.

27. Old Design Center vs LOS 2.0

1. Overview

Essentials is the LOS workspace for the user's day-to-day supporting tools. In LOS 2.0, the module is no longer a collection of visually unrelated utilities. Calendar, Documents, E-Sign, Training, Notes, and Task Management follow a common page structure and interaction model.

Task Management and connected scheduling are new 2.0 capabilities. Documents, E-Sign, Training, and Notes keep their core behavior while moving into the redesigned Essentials experience.

Change classification: Task Management is a new functional subsystem. Calendar receives both workflow integration and a major redesign. Documents, E-Sign, Training, and Notes are primarily UI/UX modernizations with existing functionality preserved.

2. Essentials Scope

• Task Management - new work-management and scheduling capability.
• Calendar - schedules, events, holidays, birthdays, and related work visibility.
• Notes - existing LOS/file notes retained as a separate concept from Tasks.
• Documents - secure file and folder management.
• E-Sign - templates, documents, signers, and e-sign workflow status.
• Training - company and platform learning content.
• Shared behavior - workspace scoping, permissions, search, filters, empty states, and LOS 2.0 UI standards.

3. Major Functional Change - Notes and Tasks Are Separate

3.1 Old LOS Behavior

In the old Essentials area, Notes carried several fields associated with work management, including Assigned To, Assigned By, Status, Priority, Due Date, Department, Loan Number, and Created. Because of these fields, Notes could be used informally as task-like records even though their primary purpose was to capture LOS/file information.

3.2 LOS 2.0 Behavior

LOS 2.0 keeps Notes but creates a separate Task Management section. Notes remain focused on record/file commentary and existing note workflows. Tasks become the correct place for action items, reminders, meetings, due dates, recurring work, and daily planning.

• Notes: record/file information, loan-related comments, internal history, and existing note workflows.
• Tasks: action-oriented work, assignments, due dates, priorities, status, and daily execution.
• Reminders: time-sensitive prompts that can appear in Today's Agenda and Dashboard Today.
• Meetings: scheduled appointments integrated with Calendar.
• Recurring items: work or events that repeat according to a configured schedule.

Notes and Tasks stay separate: Existing Notes remain notes, while Tasks are used for action-oriented work, due dates, reminders, meetings, and recurring activity.

4. New Task Management

Task Management is the primary new Essentials capability. It provides a centralized workspace where users can see what requires attention today, create tasks, set reminders, schedule meetings, and manage recurring work.

4.1 Main Views

• Today - a consolidated agenda for the current day.
• Tasks - full task list and task management.
• Calendar - schedule view integrated with task/meeting activity.
• Recurring - recurring tasks and recurring scheduled items.
• Reminders - quick access to current and upcoming reminders.

4.2 Task Data

• Title and optional description.
• Assignee and creator/assigned-by context.
• Priority such as Low, Medium, or High according to configured values.
• Status such as Pending, In Progress, or Completed according to configured workflow.
• Due date and due time where applicable.
• Type so the system can distinguish Task, Reminder, Meeting, and recurring activity.
• Optional related customer, loan, or LOS record where supported by the existing data model.

4.3 Assignment

Task assignment allows a user to create work for themselves or an authorized team member. The system must preserve who created the task and who is responsible for it. Users may assign tasks only within their permitted workspace/team scope.

5. Today and Today's Agenda

The Today view is designed to answer one question: what needs the user's attention today? It consolidates due or scheduled items into Today's Agenda and presents them in an operational table.

• Tasks due today.
• Reminders due today.
• Meetings scheduled today.
• Recurring items whose occurrence falls today.
• Priority, status, assignee, due time, and type are displayed where applicable.
• View All opens the broader list when the daily agenda contains more items than can be shown comfortably.

Today must derive from the same underlying task/scheduling records used elsewhere. It must not store a separate copy of today's tasks or meetings.

6. Reminders

Reminders are introduced as a first-class scheduling item. A reminder is intended to prompt the user at or before a specific time without necessarily representing a full task workflow.

• Users can create reminders with title, date, and time.
• Reminders due today appear in Today's Agenda.
• The Task Management header can show an active/upcoming reminder count.
• Reminders can also be surfaced in the Dashboard Today summary.
• Editing or completing a reminder must update every view that references the same underlying reminder record.

7. Meetings

Users can schedule meetings from the Task Management/Calendar experience. Meetings become calendar events and should be visible in the user's daily agenda on the scheduled date.

• Meeting title and details.
• Date and start/end time or all-day behavior where supported.
• Participants/attendees where available.
• Optional related customer, loan, or LOS record.
• Calendar visibility and Today's Agenda visibility on the correct date.

8. Recurring Tasks and Events

Recurring items allow users to define work once and have it repeat on a schedule. This eliminates repeated manual creation of the same task or meeting.

• Daily recurrence where supported.
• Weekly recurrence and selected weekdays where supported.
• Monthly recurrence where supported.
• Optional end date or stop condition.
• Recurring schedules can be paused or stopped when they are no longer needed.
• Each applicable occurrence must be represented correctly in Today and Calendar.

Recurring work stays synchronized: Recurring items appear on the applicable dates in Today and Calendar, with reliable status, completion history, edits, and audit visibility.

9. Calendar Redesign and Integration

Calendar becomes an integrated planning surface rather than a standalone date display. It combines manual events with system-generated or system-sourced items such as meetings, tasks, holidays, and employee birthdays.

9.1 Calendar Navigation

• Previous and Next navigation.
• Today shortcut.
• Month, Week, and Day views.
• Event-type filtering such as All Events.
• Add Event action.

9.2 Calendar Data Sources

• Tasks with dates/times.
• Meetings.
• Reminders where the product design calls for calendar visibility.
• Recurring task/event occurrences.
• Company holidays.
• Employee birthdays.
• Manually created calendar events.

Tasks, meetings, reminders, recurring items, holidays, birthdays, and manually created events are brought together in one consistent calendar experience so dates and statuses remain synchronized.

10. Upcoming Events

The new Calendar includes an Upcoming Events area that turns future calendar activity into readable event cards. This provides more context than a basic calendar dot or date marker.

• Event category/type.
• Event title.
• Description or contextual detail.
• Date and all-day indicator where applicable.
• Event actions through an overflow/action menu.

11. Holidays and Employee Birthdays

11.1 Holidays

Company holidays are represented as a dedicated calendar source/category. Users can show or hide holiday visibility without deleting the underlying holiday records.

11.2 Employee Birthdays

Employee birthdays are surfaced from employee data and can be presented in Upcoming Events. Birthday entries may display employee name, date, role/title, email, and age where the source data and policy support it.

Connected employee data: Birthdays and employee details are read from employee records, so Calendar does not require duplicate birthday maintenance.

12. My Calendars / Visibility

The Calendar provides a My Calendars area for organizing event sources such as Holidays and Birthdays. Visibility controls allow the user to temporarily hide a category without changing or deleting underlying records.

• Holidays visibility.
• Birthdays visibility.
• Tasks visibility in the Task Management calendar.
• Meetings visibility.
• Additional user-created or configured calendar groups where supported.

13. Add / Manage Events

Users can create events through Add Event or the calendar/task workflow. The exact fields can vary by type, but the system should support the relevant scheduling information and maintain one source of truth.

• Title.
• Date.
• Start and end time or All Day.
• Event type/category.
• Description/details.
• Participants where supported.
• Related record where applicable.

14. Dashboard Integration

Task Management is connected to the LOS 2.0 Dashboard. The Dashboard Today widget acts as a summary of the same underlying scheduling data managed in Essentials.

• Tasks due today should appear on Dashboard Today.
• Reminders due today should appear on Dashboard Today.
• Meetings scheduled today should appear when supported by the Dashboard design.
• Recurring items occurring today should appear as applicable.
• Completing or editing an item in either location must update the same underlying record.

15. Documents - Complete UI Redesign

15.1 Old LOS Behavior

The old Documents/File area behaved like a simple file explorer. Users could upload files, create folders, and browse categories such as Proposal, Rates, Products, Flyers, and Banners through a flat list.

15.2 LOS 2.0 Behavior

LOS 2.0 retains the same core file-management purpose but reorganizes the experience into a modern document library with folder cards, document search, sorting/filtering, and a structured All Documents table.

15.3 Folder and Document Controls

• Search documents and folders.
• Filter by type.
• Sort/filter by Last Modified.
• Switch between list/grid presentations where supported.
• Upload files.
• Create New Folder.
• Open folders and view item counts.
• Use row-level actions such as View, Move/Manage, or Delete according to permissions.

15.4 Document Table

• Name.
• Category.
• Type.
• Size where available.
• Last Modified.
• Actions.

This is primarily a UI/UX update. Existing file permissions, upload constraints, storage rules, and folder behavior remain intact.

16. E-Sign - Complete UI Redesign

E-Sign retains the existing template/document workflow while being reorganized into a modern LOS 2.0 workspace. Templates and Documents remain distinct views within the same E-Sign area.

16.1 Templates

• Search templates.
• Organize templates by Categories.
• Create New Template.
• Display category sections such as Uncategorized where appropriate.
• Show a clear empty state when a category contains no templates.

16.2 Documents

• User.
• Document.
• Signer(s).
• Status such as Pending or Finalized.
• Request Date.
• Finalized Date.
• Existing view, download, lock/security, reminder, or related actions according to the existing e-sign workflow.

The E-Sign redesign keeps legal workflow semantics, signer status, audit history, finalized-document handling, and permissions intact.

17. Training - Complete UI Redesign

17.1 Existing Functional Purpose

Training remains the company learning library. Existing Company, 1S Platform, Page Videos, Add Video, search, edit, and content-management behavior remains functionally available.

17.2 LOS 2.0 Organization

• Categories sidebar for faster navigation.
• All Videos and Recent Videos views.
• Category groups such as Training Meetings, Processing Training, and Tutorials.
• Search by title, group, or content.
• Group filter.
• Status filter.
• Sort order such as Newest First.
• Grid/list display controls where supported.
• Modern video cards with thumbnail, play action, title, category, edit, and additional actions.

17.3 Permissions

Training content management remains permission-controlled. Admin-only or restricted content must not be available to unauthorized users even if they know a direct URL.

18. Notes

The Notes feature continues to preserve its LOS/file-note purpose, including the existing note details and actions already available to users.

The important LOS 2.0 change is conceptual and organizational: users now have a dedicated Task Management module for work execution. Notes should not be presented as the primary task list.

19. Notes vs Task Management

20. Workspace & Access

Essentials areas that expose My Workspace or team scope must continue to enforce the existing permission model. Workspace selection changes the permitted data view; it must never be a substitute for authorization.

• Users can view only tasks and events within their permitted scope.
• Task assignment targets are limited to authorized users/teams.
• Documents and folders remain permission-controlled.
• E-Sign templates and documents remain permission-controlled.
• Training administration remains restricted to authorized roles.
• Direct URLs and API requests must enforce the same permissions as the visible UI.

21. Empty, Loading, and Error States

• Task Management: show a clear message when no tasks/reminders/events are scheduled.
• Calendar: show a useful empty state when there are no events for the selected view/filter.
• Documents: show no documents/folders found where applicable.
• E-Sign: show No templates found or the appropriate document empty state.
• Training: show no videos available when filters return no content.
• Independent subsystem failures should not make the entire Essentials area unusable where they can be isolated.

22. Old Essentials -> LOS 2.0 Comparison

1. Overview

The HR scope represented in this release is focused on attendance and time tracking. The system records employee clock-in and clock-out activity, calculates worked time, provides employees with their own attendance history, and gives authorized management users visibility into team attendance. LOS 2.0 preserves those core business functions while improving usability and adding operational tools for reporting and attendance correction.

The redesign should not be interpreted as a new payroll system. Unless separately specified, payroll calculations, compensation, leave accrual, benefits, overtime policy, and payroll processing remain outside this documented scope.

Change classification: HR in LOS 2.0 is a UI/UX redesign plus two functional enhancements - attendance export and authorized manual attendance entry/correction.

2. Old HR Baseline

2.1 Employee Attendance History

The legacy HR page displayed the logged-in user's attendance records in a left-side table. The core fields were Date, Check In, Check Out, and Working Time. The user could scroll through historical records but had limited summary information or visual context.

2.2 Admin Panel

The legacy Admin Panel displayed employee attendance in a second table. Management could search/select an employee and use From and To dates. The table displayed User, Day, Clock In, Clock Out, and Worked Time, with a total row for the displayed records.

2.3 Legacy Limitations

• Personal and management attendance appeared as two dense tables rather than a unified HR workspace.
• No summary cards existed for attendance totals or working-hour totals.
• Management could review records but had no dedicated export function.
• There was no direct management workflow to add a missed attendance record when an employee forgot to clock in or out.
• The interface provided limited visual hierarchy and weak separation of employee versus management responsibilities.

3. LOS 2.0 Attendance & Time Tracking Workspace

The redesigned page is presented as Attendance & Time Tracking with the purpose of monitoring employee hours, clock-ins, and attendance. It separates personal attendance from team-level attendance while keeping the most important metrics and management controls visible at the top of the workspace.

3.1 Main Page Areas

• Header with Employee, From, To, and Export controls for authorized management users.
• Attendance summary cards.
• My Attendance panel for the logged-in user.
• Today attendance summary.
• Attendance History list.
• Team Attendance table for authorized management users.

4. Attendance Summary Cards

LOS 2.0 adds summary cards that provide immediate context before a user reviews individual attendance records.

4.1 Total Employees

Displays the number of employees represented by the current attendance scope. The product team should define whether this means all employees available to the logged-in manager or only employees represented by the active filters. The definition must remain consistent across the application and exported reports.

4.2 Attendance Records

Displays the number of attendance records in the selected date range and applicable employee/workspace scope.

4.3 Total Days

Displays the number of recorded attendance days represented by the selected records. The counting rule must avoid double-counting a single employee-day when multiple clock sessions exist on the same date unless the business explicitly defines Total Days differently.

4.4 Total Working Hours

Displays cumulative worked hours for the applicable records. The value must use the same worked-time calculation rules as the detailed attendance table and export.

Summary cards must be derived from the same filtered attendance dataset as the detailed records. They should never be maintained as separate counters.

5. My Attendance

The My Attendance panel gives the logged-in employee a dedicated view of personal attendance. This separates personal time tracking from management reporting and makes the current-day state immediately understandable.

5.1 Today

• Clock In - the current day's recorded clock-in time.
• Clock Out - the current day's recorded clock-out time where available.
• Working Time - calculated current-day worked time.
• Employee avatar/identity for clear context.

If an employee has not clocked out yet, the system should avoid presenting a misleading final worked-time value. The UI should use the existing attendance rule for in-progress sessions.

5.2 Attendance History

Historical records remain available and include Date, Clock In, Clock Out, and Hours. This preserves the old HR functionality while placing it inside a clearer personal-attendance panel.

6. Team Attendance

Authorized managers, HR users, or administrators can review team attendance in a dedicated table. The table includes Employee, Date, Clock In, Clock Out, and Worked Time. Employee identity is presented more clearly using initials/avatar plus employee name.

6.1 Employee Filter

The Employee filter should search or select only employees that the logged-in user is authorized to manage or view. It must not expose other employees merely because a name is entered manually.

6.2 Date Range Filters

From and To filters control the attendance period. Applying the date range should update the Team Attendance table and any summary metrics defined to respond to the selected period.

6.3 Permissions

• Normal employees should primarily see their own attendance information.
• Managers should see only employees within their permitted management scope.
• HR/administrators may receive broader organization-level access according to existing roles.
• The backend must enforce the same access rules as the UI.

7. New Feature - Attendance Export

LOS 2.0 adds an Export action for authorized management users. This is a true functional enhancement rather than a visual redesign.

7.1 Export Scope

• Employee filter, if selected.
• From date.
• To date.
• Current workspace/management scope.
• User permissions.

The exported dataset should match the records the user is authorized to view. Export must not silently include employees or periods outside the selected scope.

7.2 Minimum Export Fields

• Employee Name
• Date
• Clock In
• Clock Out
• Worked Time

Additional fields such as Employee ID, Department, or Attendance Status may be included only if they already exist in the HR data model and are appropriate for the user's permission level.

7.3 Export Permission

Export should be a management-level capability. A user who can view only personal attendance should not automatically gain the ability to export organization-wide attendance data.

8. New Feature - Manual Attendance Entry / Correction

LOS 2.0 introduces an Add action that allows authorized management to create or correct attendance when an employee forgets to clock in or when a clock event was not captured correctly. This resolves a limitation of the legacy HR screen.

8.1 Primary Use Cases

• Employee forgot to clock in.
• Employee forgot to clock out.
• Clock-in time was recorded incorrectly.
• Clock-out time was recorded incorrectly.
• A system or network issue prevented an attendance event from being captured.

8.2 Recommended Manual Entry Fields

• Employee
• Attendance Date
• Clock In Time
• Clock Out Time
• Reason / Notes for adjustment where supported

Worked Time should be calculated from the entered clock times using the same calculation logic used for normal clock records rather than allowing an arbitrary worked-time total to be entered independently.

8.3 Create vs. Correct

Authorized users can add or correct attendance records from the redesigned HR workspace, with management changes kept distinct from employee clock activity.

9. Audit Trail for Manual Attendance

Manual attendance adjustment affects potentially payroll-relevant records. For that reason, the system should distinguish system-generated clock activity from management-entered corrections.

9.1 Recommended Audit Information

• Original value before modification, where applicable.
• New value.
• Employee whose attendance was changed.
• User who made the change.
• Date and time of the change.
• Reason for adjustment where supported.
• Source indicator such as System Clock Record or Manual Entry.

Audit trail is strongly recommended. Without it, a manually corrected record can become indistinguishable from an employee-generated clock record, creating accountability and payroll-dispute risk.

10. Worked Time Calculation

Worked Time continues to be calculated from valid attendance sessions, including the existing handling for multiple sessions and incomplete records.

10.1 Multiple Same-Day Sessions

The data shown in the LOS indicates that an employee can potentially have more than one clock-in/clock-out pair on a date. If multiple sessions are supported, daily Worked Time should aggregate valid sessions rather than simply subtracting the first clock-in from the final clock-out.

10.2 Invalid or Incomplete Attendance

• Clock In exists but Clock Out is missing.
• Clock Out exists without a valid Clock In.
• Clock In and Clock Out are identical.
• Clock Out occurs earlier than Clock In.
• Worked Time calculates to an invalid or misleading value.

Such records should follow the existing attendance exception behavior and should not silently inflate summary totals. Where feasible, management should be able to identify records requiring correction.

11. UI/UX Redesign

Beyond the functional additions, the HR workspace receives a complete LOS 2.0 visual redesign.

• Clear module header and explanatory subtitle.
• Modern summary cards for quick management context.
• Better grouping of employee and management functions.
• Cleaner filters and date controls.
• Improved employee identity presentation.
• Structured Team Attendance table.
• Compact personal Attendance History.
• Consistent buttons, badges, spacing, and table styling with LOS 2.0.
• Improved scrolling and use of available screen space.

12. Old HR vs. LOS 2.0

1. Overview

The Pricing & Product Engine remains the central LOS workspace for building mortgage scenarios, reviewing pricing history, managing rate alerts, and accessing lender rate sheets. LOS 2.0 modernizes these existing areas and introduces a new automated refinance monitoring workflow through Rate Radar.

The PPE update should be treated as two categories of change: functional additions that alter business workflow, and UI/UX modernization that improves access to existing functions without changing their core purpose.

2. Scope of PPE 2.0

• Scenario creation and pricing inputs.
• CRM customer selection and customer search.
• Scenario, Proposal, Verification, Lock Request, and Submission history.
• Rate Alerts management.
• Lender Rate Sheet access.
• New Rate Radar closed-loan monitoring.
• Proposal, Rate Comparison, and Rate Sheet PDF generation.
• Workspace scoping, permissions, search, filtering, pagination, empty states, and error handling.

3. Scenario Redesign

The Scenario page remains the starting point for structuring and pricing a mortgage scenario, but the layout is redesigned into a cleaner three-panel experience: Customer Information, Loan Information, and Property Information.

Customer Information

• FICO Score
• First Time Home Buyer
• Down Payment Assistance / Grant Money
• Limited Income
• Streamline
• Select existing customer action

Loan Information

• Category Type
• Product Type
• Term
• Amortization
• Loan Purpose
• Price
• Appraised Value
• Loan Amount
• LTV
• Subordinate Financing

Property Information

• Occupancy
• Legal Structure
• Units
• Property Type
• Manufactured
• Identifier
• Property ZIP
• State
• County
• Contextual Loan Limit and tax information where available

4. CRM Customer Search Enhancement

Previously, customer selection was primarily initiated from a popup. LOS 2.0 keeps the popup Select action but also adds a prominent customer search field directly on the Scenario page.

Connected CRM search: PPE customer search uses existing CRM customer records and follows the same visibility permissions.

• Search an existing CRM customer without first opening the selection popup.
• Open or begin a scenario directly from the selected CRM record.
• Retain the popup Select workflow for users who prefer browse/select behavior.
• Do not return customers outside the logged-in user's permitted CRM scope.

5. Scenario Calculations and Dependencies

The redesign should not create a second calculation model. Existing PPE calculations and dependencies remain the source of truth. When inputs change, dependent values must recalculate according to existing pricing and eligibility rules.

• Price, Appraised Value, and Loan Amount may affect LTV.
• Property ZIP, State, and County may affect loan limits and contextual property data.
• Loan purpose, term, amortization, category, product type, occupancy, and property type may affect eligible pricing results.
• Calculated values should not become stale when a user edits upstream scenario inputs.

6. PPE Scenario Actions

The redesigned Scenario toolbar continues to expose the established workflow actions. Their business purpose should remain consistent while the interaction and visual hierarchy are modernized.

• New
• Open
• Save
• Save as New
• Request
• Search
• Filters

7. History Redesign

History is visually redesigned and remains the central audit/retrieval area for PPE activity. Existing history categories continue to be available.

• Scenario
• Proposal
• Verification
• Lock Request
• Submission

Users can search by values such as ID, user, customer, or type and can filter by a From/To date range. The result table includes the information needed to identify and reopen prior pricing activity.

• ID
• Date
• User
• Customer
• Product Type
• Loan Type
• Loan Amount
• LTV

Pagination and rows-per-page controls should behave consistently with other LOS 2.0 data tables.

8. Rate Alerts Redesign

The existing Alerts feature is redesigned as Rate Alerts. The business concept remains, but the new page adds summary metrics and clearer filtering so the user can understand alert volume before working individual records.

Summary Cards

• Total Alerts
• Active Alerts
• Inactive Alerts
• Auto Repeat

Search and Filters

• Search
• Status
• Product
• Purpose
• Repeat
• Refresh/reset actions

Rate Alert Table

• Created
• Product
• Customer
• Contact
• Loan
• Purpose
• Status
• Repeat
• Edit
• Delete

9. Rate Sheet Redesign

The Rate Sheet area is modernized but retains its existing purpose: allowing users to find and download rate sheets supplied by lenders.

• Search lenders.
• Filter by From date and To date.
• Refresh the current result set.
• View lender, rate-sheet date/time, relationship, and applicable download action.
• Display a clear No Rate Sheets Found state when the selected criteria return no records.

10. Rate RadarLive

Rate Radar is the largest new functional addition in PPE 2.0. It automatically monitors closed loans and identifies potential refinance opportunities without requiring an MLO to manually re-price every closed file.

Rate Radar is not the same as a manually created Rate Alert. It is a lifecycle-based monitoring service tied to closed loans and current PPE pricing.

11. Rate Radar Eligibility

A loan enters Rate Radar after the file is closed and the configured post-closing waiting period has been met, currently six months.

• Closed loans inside the waiting period are not actively re-priced.
• Loans that have not completed the waiting period remain in the Not Eligible state until the eligibility date is reached.
• Once the eligibility period is reached, the loan can move into active monitoring (Watching).
• The eligibility date is calculated from the loan's closing/closed date rather than a general last-modified timestamp.

12. Daily Automated PPE Evaluation

For each eligible monitored loan, the system automatically reconstructs the applicable scenario from the closed file and evaluates it through PPE once per day.

• The MLO does not have to manually open and re-run the scenario.
• The recurring evaluation uses current PPE pricing while preserving the closed loan's relevant borrower, loan, and property attributes.
• The latest evaluation time and result are recorded so monitoring activity remains traceable.
• A failed pricing attempt is kept separate from a true no-opportunity result and can be retried.

13. Data Used by Rate Radar

Rate Radar uses information from the closed loan together with current PPE pricing so the automated evaluation reflects the same core borrower, loan, and property context used during a manual re-price.

• Existing interest rate and current mortgage payment.
• Current or estimated outstanding balance, as supported by the business process.
• Loan term and amortization characteristics.
• Loan purpose and refinance eligibility inputs.
• Property information and occupancy.
• Customer/borrower information required for pricing.
• Current PPE products, rates, and applicable pricing rules.

14. Opportunity Found Logic

When current pricing produces a result that satisfies the configured refinance-opportunity rule, Rate Radar places the loan into Opportunity Found and surfaces it to the responsible MLO.

Opportunity evaluation: Rate Radar uses current pricing and configured refinance-opportunity thresholds so opportunities are surfaced only when the monitored loan meets the active criteria.

Opportunity evaluation can incorporate the configured rate improvement, payment savings, closing costs, APR, break-even period, term difference, and refinance purpose used by the active pricing rules.

A Rate Radar opportunity is created only when current pricing meets the configured improvement threshold for the monitored loan.

15. MLO NotificationIn Development

Rate Radar already surfaces qualifying opportunities inside the monitoring workspace. The expanded automatic MLO notification experience is still in development and will connect those opportunities to the broader 2.0 Notifications & Action Alerts system.

• Customer name and loan reference.
• Existing mortgage/rate information.
• New pricing opportunity summary.
• Date/time the opportunity was detected.
• Action that opens the applicable Rate Radar record or pricing detail.

16. Rate Radar Status Lifecycle

The new Rate Radar screen exposes statuses that represent where each monitored loan is in the refinance-opportunity lifecycle.

17. Rate Radar Summary Metrics

The Rate Radar page provides summary cards that let users understand the monitored portfolio at a glance.

• Monitored Loans
• Watching
• Opportunities Found
• LO Notified
• Not Eligible

Summary counts are calculated from the same Rate Radar records shown in the page and follow the selected workspace and user access level.

18. Rate Radar Search and Filters

• Search by customer, loan number, address, or other supported identifiers.
• Filter by status.
• Use More Filters for additional supported criteria.
• Clear resets active filters without altering the underlying monitoring state.
• Tab counts (All, Opportunity Found, Watching, Not Eligible, LO Notified, Customer Notified, Paused, Stopped) stay synchronized with the current record state.

19. Proposal PDF Redesign

Proposal PDFs are redesigned from a generic standard layout into company-branded customer-facing documents. The intent is for generated pricing material to look like it belongs to the company using LOS 2.0 rather than a default system template.

• Company logo where configured.
• Company theme/colors.
• Consistent branded headings and typography.
• Configured company/contact information.
• Layout that remains readable when data values are longer than the design examples.

20. Rate Comparison PDF Redesign

Rate Comparison PDFs use the same company branding system and clearly present multiple loan/rate options selected for comparison. The comparison is also enhanced by the new Recommended option capability.

21. Rate Sheet PDF Redesign

Applicable generated/customer-facing Rate Sheet documents also use the company theme so Proposal, Rate Comparison, and Rate Sheet outputs share a consistent visual identity.

Consistent branding: Proposal, Rate Comparison, and supported Rate Sheet PDFs use the same company document theme for logos, colors, typography, and contact information.

22. QR Code on PPE PDFs

LOS 2.0 adds a QR code to supported customer-facing PPE PDFs, including Proposal, Rate Comparison, and applicable Rate Sheet documents.

• The QR code must be generated at PDF creation time.
• The QR code opens the configured destination for the generated document.
• The configured destination is validated and does not rely on an expired or session-only URL.
• The QR code should remain scannable after normal printing and PDF scaling.

23. Customizable User Paragraph

Users can enter a custom paragraph or customer-facing message that is inserted into supported PPE PDFs. This allows the loan officer to add context, recommendations, well wishes, or follow-up guidance without editing the PDF outside LOS.

• User can enter or edit the paragraph before document generation.
• Blank text is allowed and should not leave an awkward empty block in the PDF.
• Line wrapping and page overflow must be handled automatically.
• Special characters and multiple lines should render correctly.
• A reasonable maximum length should be enforced to protect document layout.

24. Recommended Option

In Rate Comparison and applicable rate-option documents, the user can identify the option they recommend to the customer. For example, if three rates are compared and the user recommends the second loan, that option is visually distinguished.

• Display a Recommended label on the selected option.
• Use green visual emphasis for the recommended option.
• Do not alter the product's underlying rate or pricing values when it is marked Recommended.
• Only options included in the current comparison may be recommended.
• One compared option can be marked Recommended in each comparison.

25. My Workspace

The new PPE screens expose a My Workspace selector. Workspace scope should consistently affect the records a user can access in applicable PPE areas such as Scenario, History, Rate Alerts, and Rate Radar.

Workspace selection must not bypass permissions. A broader workspace option can only expose records the user is otherwise authorized to view.

26. UI/UX Modernization Across PPE

The remaining PPE changes are primarily presentation and usability improvements rather than changes to the underlying business purpose.

• Consistent page headers and subtitles.
• Cleaner information cards and section grouping.
• Improved search and filter placement.
• Clearer action-button hierarchy.
• Improved tables, sorting indicators, pagination, and rows-per-page controls.
• Status pills and visual state indicators.
• Purposeful empty states such as No Rate Sheets Found and No records found.
• Reduced unused whitespace and better use of desktop screen width.
• Consistent styling with the rest of LOS 2.0.

27. Access & Security

• CRM customer search must obey CRM access permissions.
• History results must be limited according to user/workspace access.
• Rate Alerts and Rate Radar records must follow assigned-user, team, and administrative access rules.
• Generated documents must not expose borrower information outside the user's permitted scope.
• Server/API authorization must enforce permissions even when UI controls are hidden.

28. Empty, Loading, and Error States

PPE 2.0 combines interactive pricing, history, monitoring, and document generation. Each area should fail independently and communicate its state clearly.

• Show a loading state while scenarios or tables are being retrieved.
• Use meaningful empty states instead of blank tables.
• If current PPE pricing is temporarily unavailable, Rate Radar should record/retry the failed evaluation rather than generating a false no-opportunity result.
• PDF generation failures should preserve the scenario and allow retry.
• Search/filter failures should not erase user input or saved PPE data.

29. Old PPE -> LOS 2.0 Comparison

1. Overview

Company Management is now the central administration workspace for organization identity, branches, users, teams, communication services, LOS/system configuration, website settings, unsubscribe controls, and selected content assets. The familiar capabilities remain available, but the experience is reorganized into a clearer structure with stronger access controls and more consistent page layouts.

2. New Company Management Navigation

The legacy horizontal tab strip has been replaced by grouped left-side navigation so related settings are easier to find.

Only areas available to the company and the signed-in administrator are shown, keeping the workspace focused on the settings that apply to that account.

3. Company Profile, Overview & Setup Status

The Company page remains the main location for organization identity and contact information, including company name, DBA, contact details, NMLS information, website, routing email addresses, TPO processor selection, address, About Us content, disclaimer, company values, and company logo or picture.

• A cleaner structured form replaces the older dense administration layout.
• A Company Overview panel surfaces useful organization context such as branch count, licensed-user count, team count, and LOS company code where available.
• Setup Status provides at-a-glance visibility into company profile completion, branding availability, and LOS configuration.
• A consistent Save Changes action keeps company updates in one clear location.

4. Branch Management

Branches keep their existing business purpose while receiving a streamlined list-and-drawer workflow. Administrators can search and select branches without leaving the list, while create and edit actions open in a right-side drawer.

• Branch: name, code, DBA, contact information, phone numbers, NMLS, taxpayer ID, email, website, and address.
• State: existing state-specific branch configuration.
• Customization: About Us, disclaimer, colors, document branding, and branch imagery.

5. Branch Branding & PDF/Flyer Colors

Branch-level branding has been expanded so supported customer-facing materials can reflect the branch connected to the user, loan, or document.

This allows multi-branch companies to keep generated proposals, comparisons, rate sheets, flyers, and other supported documents aligned with the correct branch identity.

6. User Management

The Users area has been redesigned into a searchable, filterable administration list with clearer identity and organization context. Selecting a user opens a settings drawer rather than replacing the entire page.

• Search by user.
• Filter by Team, Branch, and Role / job classification.
• View user name, email, role/title, branch, and team context.
• Retain pagination and record counts for larger companies.
• User settings remain organized across Profile, Password, Access, Email, Calls, Billing, and Third Party tabs.

7. Account Authority Levels

1 Solution 2.0 separates account authority from the employee's business role. A Loan Officer, Processor, Recruiter, or other role can still have the appropriate User, Manager, or Admin account authority.

8. Workspace Data Scopes

Data visibility is now easier to understand through three workspace scopes.

Workspace visibility and edit authority remain separate. Broader visibility does not automatically turn a standard User account into a Manager or Admin.

9. Granular Section & Subsection Access

Access can now vary by section and subsection instead of relying on one broad company-wide setting. This allows a company to give the same user different scopes across different workflows.

• PPE Scenario can be limited to My Workspace.
• PPE History or Rate Sheet can use Company Workspace when permitted.
• Rate Radar can remain user-specific.
• CRM Customers can use Team Workspace.
• Communication areas can use their own permitted workspace context.

10. Clear Access Hierarchy

The 2.0 access model separates module enablement, section access, workspace visibility, and account authority.

A module disabled for the company remains unavailable across Company Management, the sidebar, search, and direct navigation.

11. Teams

Team creation and maintenance remain part of Company Management. Administrators can continue to create, rename, edit, and delete teams according to their access. Team membership now also plays a clearer role in Team Workspace visibility.

12. Communication Administration

• PBX: company-level telephony configuration remains available.
• Email Groups: shared addresses, labels, and recipient membership remain available.
• Email Whitelist: approved-domain search, add, delete, and pagination remain available.
• Unsubscribe: company and user unsubscribe records, campaign history, contact information, dates, and applicable actions remain available.

13. Systems & Content

• LOS: existing company-level LOS configuration remains available under Systems.
• Website: company website configuration is grouped under Systems with company, branch, and user settings resolving consistently.
• Pre-Approval Images: approved imagery and active/inactive controls remain available under Content.

14. Company, Branch & User Configuration

Company Management now presents a clearer configuration hierarchy. Company settings provide the base organization values, supported branch settings override those defaults for branch-specific identity and branding, and user settings apply where a feature is intentionally personal to the user.

This is especially important for generated customer-facing material, which resolves the appropriate branding source instead of mixing company, branch, and user values unpredictably.

15. Data Continuity, Security & Audit Visibility

The redesign keeps existing company, branch, user, team, PBX, email-group, whitelist, unsubscribe, LOS, website, and pre-approval-image data available in the new experience.

• Existing company and branch information carries into the redesigned pages.
• User role/title, branch, team, status, email, call, billing, and third-party settings remain connected to the same user records.
• Changes to account authority, workspace scope, access, branch assignment, status, disclaimers, and branding remain auditable where applicable.
• Sensitive settings remain protected by the corresponding administrative permissions.

16. UI/UX Modernization

• Grouped left-side navigation replaces the long horizontal tab strip.
• Company settings use consistent cards, forms, and primary actions.
• Branch and user editing use side drawers so administrators keep list context.
• Search and filters sit directly above the lists they control.
• Large configuration forms are divided into logical tabs.
• The section follows the shared 2.0 responsive design and system-wide Dark Mode experience.

17. Company Management: Before & After

1. Overview

Profile & Settings is now the self-service account area for personal identity, account security, communication preferences, approved integration credentials, public website content, and active-device management. The update keeps the familiar profile and security capabilities while expanding the public-facing experience into a configurable mortgage website.

2. Redesigned Profile & Settings Workspace

The updated layout creates a clearer hierarchy around the user's account and public presence.

• Personal
• Communication
• My Website
• Password
• Two-Factor
• Devices for users with multi-device access

The profile header displays the signed-in user's identity, profile picture, role/title, and applicable licensing information, with a direct Change Picture action.

3. Existing Profile & Security Features Retained

• Personal identity and contact information remain editable according to account permissions.
• Communication preferences remain available in the redesigned experience.
• Password management remains available from the Password tab.
• Two-factor authentication remains available for account security.
• Approved third-party credentials, including supported credit, Desktop Originator, and IDS connections, remain available with protected secret values.

4. E-Card Evolves into My Website

The legacy E-Card has been expanded into My Website. Instead of a simple digital business card with limited personalization, users can now manage a full personal mortgage website connected to their approved profile information.

Existing identity, social information, About Me content, and public URL behavior carry forward into the new website experience where applicable.

5. Live Website Preview

My Website includes a live preview so users can review their public-facing content before sharing the link.

• Desktop preview for the full-width website experience.
• Mobile preview for smaller-screen review.
• Preview reflects the same saved content and visibility settings used by the public website.
• Open Full Website launches the public version for review.

6. Profile & Hero Website Imagery

Users can personalize the visual presentation of their website with supported profile and hero imagery. A default image is available, and users can replace supported website images while keeping the profile photo connected to the account profile.

• Supported image uploads are validated before use.
• The preview shows how configured imagery appears in the website layout.
• Removing an optional custom image falls back to the configured default instead of displaying a broken image.

7. Loan Programs

Users can now present the mortgage programs they offer directly on their personal website.

• Enable or hide the Loan Programs section.
• Add program titles and customer-facing descriptions.
• Maintain multiple supported programs.
• Display configured programs as clear cards on the public website.
• Preview program changes before sharing the public page.

Examples can include Purchase, Refinance, FHA, VA, DSCR, HELOC, and other programs made available by the company.

8. Website Section Visibility

Individual website sections can be shown or hidden so each user can control the public content that applies to their business.

When a section is disabled, it is removed cleanly from the public page without leaving an empty heading, broken navigation anchor, or unnecessary blank space.

9. Mortgage Calculator

The personal website can display the approved mortgage calculator as a customer-facing section. Users control whether the calculator is visible from My Website settings.

10. About Me, Links, Value Messaging & Contact

• About Me: expands the existing E-Card description into a full website section.
• Website Buttons & Links: supports approved actions such as Get Quote, Apply Now, Contact Me, and social destinations.
• Why Work With Me: provides a dedicated area for service and value messaging.
• Contact Section: presents approved contact details and the configured customer contact experience.

11. Public Website URL

The customizable E-Card URL continues as the user's public website link. Users can view, copy, share, and open the public URL, and permitted users can update the available link suffix while preserving unique public addresses.

12. Active Devices

Profile & Settings introduces a Devices area for accounts permitted to use multiple signed-in devices.

• View active signed-in devices and sessions.
• Identify the current device.
• Review useful device/browser and recent-activity information where available.
• Sign out an individual other device.
• Sign out all other devices while keeping the current session active.

The Devices tab is shown only to accounts with multi-device access.

13. Profile, Website & Privacy Consistency

Profile & Settings and My Website use the same approved identity data wherever possible so customers see consistent name, title, licensing, phone, email, social links, and profile imagery.

• Private account and security data stay separate from public website content.
• Passwords, two-factor secrets, and saved integration credentials are never exposed on the public page.
• Public identity and licensing information follow the approved account/company data.
• Website-specific content is stored separately from private security information.

14. UI/UX Modernization

• Clear Profile & Settings page title and purpose.
• Improved identity header with role and licensing context.
• Consistent tab navigation.
• Accordion-style website configuration.
• Side-by-side website preview.
• Clear show/hide controls for public website sections.
• Modern buttons, cards, badges, and spacing.
• Desktop and mobile preview modes.
• Responsive behavior and system-wide Dark Mode support.

15. Profile & E-Card: Before & After