Users

The System User functionality is used to create and maintain the Temenos Lifecycle Management Suite users for the organization. The Users page displays all users for the organization. The default view of this page is the All Users view, which lists all users in alphabetical order by username. The following columns display in the Users page:

Column Name	Description
Username	Displays the user name of the user.
Name	Displays the full name (Last, First) of the user.
Active	If checked, the user name is active in the Lifecycle Management Suite.
Logged In	If checked, the user is currently logged into the Lifecycle Management Suite.
Last Login	Displays when the date and time of when the user was last logged in.

From the Users page, administrators can perform the following actions:

Create new users.
Copy existing users.
Edit existing users.
Unlock deactivated users.
Delete users.

User Attributes

The following attributes are defined within the User Edit window when creating or editing a user in the Lifecycle Management Suite:

Show User Information Tab

When creating or editing a user, the User Information tab displays by default.

This tab includes the following three sections:

User Information
Lifecycle Management Suite Authentication
Host Authentication

User Information

The User Information section allows system administrators to enter basic information about the user.

Certain fields within this section can be included within letter and email templates.

The following fields display within the User Information section:

Field Name

Description

First Name

Enter the first name of the user. This is a required field.

Last Name

Enter the last name of the user. This is a required field.

Username

Define a username for the user. This is used to log into the Lifecycle Management Suite, if not using Windows Authentication. This is a required field.

Enter in the user’s email address. This is a required field.

Description

If necessary, enter in a description for the user.

User Type

Define the role of the user within the Lifecycle Management Suite from this drop-down. This correlates to the workflow history colors under System Management > Administrative Settings. The security for the user is not determined by this drop-down.

Time Zone

Define the time zone for the user. This reflects the time that displays in a workflow history screen when an account is worked.

Active

Select this check box to activate the user in the Lifecycle Management Suite. Leave the check box blank to deactivate a user.

Logged In

If checked, this box indicates whether the user is logged in to the Lifecycle Management Suite.

This field can be used as a reference when editing an existing user.

Phone

Enter in the phone number of the user.

Phone Extension

Enter in the phone extension of the user.

Branch

If there are multiple branches, select the branch where the user works. This is system-defined.

Department

Enter the name of the user's department.

Title

Enter the job title of the user.

Lifecycle Management Suite Authentication

Within the Lifecycle Management Suite Authentication section, define the sign-in method of the new user.

By default, System is selected, which requires the user to enter in username and password to sign into the Lifecycle Management Suite. The administrator must define the password in this section.

The value of the password is masked upon entry in the Password and Confirm Password fields.

Once the user details are saved, the encrypted version of the password is populated within the Password field, masked as dots.

Select the Force password on next login check box to prompt the user to change their password on their next login.
Select the Password never expires check box to allow the password never to expire.

Select the Windows method to allow users to sign in using the Windows Authentication icon on the sign-in page. If this option is selected, the system validates the Windows ID and password for the user during the log in process for the Lifecycle Management Suite. Enter the Windows Account for the user in the Windows Account field. The format for the windows account is always DOMAIN NAME\username.

Select the Public API method to establish a dedicated user to communicate with connectors and third party integrations using the Public API DMZ service. Upon selecting this method, complete the following parameters:

These settings are only used for certain connectors that utilize the Public API DMZ service.

Parameter

Description

API Key

Enter the API Key generated by Temenos.

This field is required.

Secret Key

Enter the Secret Key generated by the financial institution.

This parameter provides an added level of security to financial institutions.

The Secret Key may be changed after saving; however, users are unable to edit or view it. If a user attempts to update this field to a blank value, the existing Secret Key is retained in the database.

When saving this screen, the API Key is decrypted and validated against the installation key for the environment to confirm that the key is valid. If the API Key does not match, an error message displays to the user.

Host Authentication

Within the Host Authentication section, define the Host ID, Host ID 2, and Host Password for the host system.

These settings are only used for certain host systems. For more information, please see the applicable core connector guide for the institution.

Show Company Information Tab

The Company Information tab is comprised of two sections: Company Information and Organization Structure.

The Company Information section of the tab provides the ability to define the following information for the user:

The fields within the Company Information section are for informational purposes only.

Field Name	Description
Company Name	Enter the name of the company.
Company Website	Enter the website URL for the company.
Company Email	Enter the email address for the company.
Company Phone 1	Enter in the primary phone number for the company.
Company Phone 2	Enter an additional phone number in which the company can be reached.
Company Fax	Enter in a fax number for the company.
Company Address 1	Enter the first line of the company address.
Company Address 2	Enter in the second line of the company address.
Company City	Enter the city in which the company is located.
Company State	Enter the state in which the company is located.
Company Zip Code	Enter the zip code in which the company is located.
Branch Number	Enter the branch number of the company.

Within the Organization Structure section, select a value from the desired Organization Level field(s) to define how the user is to be grouped for easier reporting purposes. The values in each drop-down populate from the ORG_LEVEL1, ORG_LEVEL2, or ORG_LEVEL3 lookup fields in System Management > Field Configurations.

Show Personal Information Tab

The Personal Information tab provides system administrators with the ability to define the user’s personal information.

The fields within the Personal Information section are for informational purposes only.

The following fields display in this tab:

Field Name	Description
Address 1	Enter the first line of the user’s home address.
Address 2	Enter the second line of the user’s home address.
City	Enter the city in which the user resides.
State	Enter the state in which the user resides.
Zip Code	Enter the Zip Code in which the user resides.
Home Phone	Enter the home phone number of the user.
Other Phone	Enter an additional phone number of the user.
Home Email	Enter in the personal email address of the user.

Show Collection Settings Tab

The Collections Settings tab provides the ability to set collection standards for the user. These fields are used by administrators to track collection performance.

The following fields display within this tab:

Field Name

Description

How contributes to User Performance

Daily Work Hours

Identifies the number of hours per a day that the user is expected to work.

N/A

Total Calls per Hour

Identifies the number of calls that a collector is expected to make per hour.

Used to determine:

Target Number of Calls for Collector Production Dashboard and User Performance Dashboard.

(Total Calls Per Hour x Hours Worked= Target Number of Calls)

Target % Contacts

Identifies the percentage of calls placed by the user expected to result in a successful, valid contact.

Used to determine:

Target Number of Contacts for Collector Production Dashboard and User Performance Dashboard.

(Actual Calls x Target % Contacts= Target Number of Contacts)

Target % Promises

Define the percentage of successful promises the user must meet.

Used to determine:

Promises Made Target for Collector Production Dashboard

(( Target % Promises x Contact Count)/100= Promises Made Target)

Target Number of Promises for User Performance Dashboard.

(Number of Contacts x Target % Promises= Target Number of Promises)

Target % Promises Kept

Define the percentage of successful promises kept the user must meet.

Used to determine:

Target Number of Promises Kept for Promise Monitor Dashboard.

((Target % Promises Kept x Due Count)/100= Target Number of Promises Kept)

Max Promise Days

Identifies the maximum number of days a collector can define for the time period in which the total promise must be fulfilled.

For example, if the max promise days is set to 30 days and the user sets the promise to be completed in 45 days, the promise goes to management for approval.

N/A

Max First Payment Days

Identifies the maximum number of days in advance that a collector can schedule the first promise payment.

For example, if the max first payment days is set to 10 days and the user schedules the first payment in 20 days, the promise goes to management for approval.

N/A

Max promise payments

Identifies the maximum number of payments in which a user is able to divide a promise payment.

When an end-user is running the Promise to Pay workflow step, this determines the maximum amount of promise payments the user can select from the Number of Payments drop-down.

For example, if the max promise days in System Management > Modules > Collection is equal to 4, and the user sets up 5 payments, the promise is deferred to management approval.

N/A

Max % Promise Tolerance

Identifies the maximum percentage of the total promise amount that a user can accept to satisfy the promise payment. A promise payment can be short without being considered broken as long as the payment meets the discount requirement specified here.

For example, if the max % promise is 10% and the total promise amount is $1,000, the promise payment can be satisfied if the borrower pays $900.

If no discounting is permitted, then the value in this field should be set to “0.”

N/A

Min Promise Value As % of DQ Amount

Identifies the minimum % of the total promise amount that the user is allowed to accept.

For example, if this setting is set to 10% and the total DQ amount is $10,000.00, the minimum promise that the user can take is $1,000.00. Otherwise the promise is sent for manager approval.

N/A

For additional information on User Performance, please see the User Performance Web Part topic in the User Guide.

Show Security Groups Tab

Within the Security Groups tab, assign the user to a Security Group. The Security Groups available to assign are defined in System Management > Groups > Security Groups.

A user can be assigned to multiple security groups.

Show Permissions Tab

The Permissions tab enables system administrators to manage a user’s access to several features throughout the Lifecycle Management Suite.

This tab contains two columns: Function and Permission. Click under the Permission column in the corresponding row, and a drop-down appears. Change the value in this drop-down to modify the user's access to the functionality. The following permission options are available for each user:

None: If selected the user does not have permission to view or execute the feature.
Change: If selected the user has full access to the feature. User can view and edit.
View: If selected, the user has the ability to view the function but does not have the ability to change or execute it.

Below is a list of all the permissions that can be customized by the administrator and their description.

Collections

Name of Permission

Description

Edit Expenses:

Allows a user to add and edit expenses within the Expenses - Account screen in the workspace.

None = Users cannot add or edit expenses within the Expenses - Account screen. When the screen opens in the workspace, the toolbar is not available, and the screen displays as read-only.

Change = Allows users to add and edit expenses within the Expenses - Account screen.

Edit Letters:

Allows a user to edit the letters assigned to a Send Letter Workflow step.

None = Users are unable to edit letters in the Send Letter workflow step. When View/Print is clicked in the workflow step, the letter opens in a PDF document, which does not permit changes.

Change = Allows users to modify letters in the Send Letter workflow step. When View/Print is clicked in the workflow step, the letter opens in an editable Word document.

Edit Promise Payments:

Allows a user edit existing promise payments made within the person workspace.

None = Users cannot edit promise payment arrangements, or cancel promises in the Promises screen.

Change = Allows users to edit promise payment arrangements, and cancel existing promises in the Promises screen.

Edit Promise Status:

Allows a user to edit the promise status of an existing promise made in the person workspace.

None = Users cannot edit promise statuses in the Promises screen.

Change = Allows users to edit promise statuses in the Promises screen.

This permission should only be given to administrators. Changing the promise status does not update promise reports/dashboards and should not be normal practice.

End Exclusive Rule Authoring Session:

Allows a user to end an exclusive Rule Authoring session in System Management > Collections > Rules Management.

None = User is not able to end the exclusive rule authoring session of another user in Rules Management. The End Session button is disabled within the Rule Sessions tab.

Change = User is able to end the exclusive rule authoring session of another user in Rules Management. The End Session button is enabled within the Rule Sessions tab.

Event Processing:

Allows a user to create and maintain event and action pairings.

None = Event Processing screen within System Management is not available to user.

View = Event Processing screen within System Management can be viewed but not edited by user.

Change = Event Processing screen within System Management screen can be viewed and edited by user.

Recovery Approval:

Allows a user to view and process pending charge offs within System Management.

This permission is only available to institutions using the Lifecycle Management Suite's Recovery module.

None = Users do not have access to the Recovery Approval page in System Management and are not able to respond to charge-offs pending approval.

View = Users have access to the Recovery Approval page in System Management but are not able to accept and/or reject charge-offs.

Change = Users are able to both access the Recovery Approval page in System Management and process pending charge-offs.

Rules Management:

Allows a user to access the Rules Management application. The Rules Management application allows users with proper permissions to view and create rules to apply in various contexts throughout the system.

None = Users do not have access to the Rule Management page in System Management > Collections, and do not have the ability to view/open the rules manager in various other areas in the system that utilize the rules integration.

Change = Allows users access to the Rules Management application throughout the system.

View Masked Fields:

Allows a user to view the value of masked fields in the workspace.

None = User is unable to view the value of masked fields in the workspace. When the user hovers over the icon for a masked field, a tool-tip is presented to the user to identify that permission to unmask the field is not enabled

View = User is able to view the value of masked fields in the workspace. Clicking the icon unmasks the value of the field in the workspace.

Check out the View Masked Fields Permission video to see this permission in action!

Workspace:

Allows a user to perform various functions within the person workspace, such as writing comments or working a queue, as well as grants the user permission to use the Search feature within the Ribbon Bar.

None = Users are not able to perform various functions within the workspace, such as posting a comment, or working a queue, and can not access workspaces from the Queues, Views, and/or Dashboards page. When set to None, the user is also unable to use the Search feature; therefore, the is disabled in the Ribbon Bar.

View = Allows users to view comments and queues in the workspace, but not work queues. When set to View, users are able to access workspaces from the Queues, Views, and/or Dashboards page, and use the Search feature; however, only screens and workflows that the user is assigned permission to are available in the Left Navigation Panel, and no changes can be made to any screens and/or workflows in the workspace.

Change = Allows users to perform various functions in the workspace, such as posting a comment, and working queues. When set to Change, users can access workspaces using the Search feature, as well as from the Queues, Views, and/or Dashboards page, and are able to perform all functions for the selected account or person in the workspace.

In addition to having View or Change permission for the Workspace, a user must also be assigned to the specific queue, view, or dashboard in order to open the workspace for the account or person.

All Custom Searches configured for an institution are available within the Search window for any user who is granted permission to use the Search feature.

For institutions that use both Account Servicing and Origination: There are two separate permissions that control the Search feature for the Account Servicing categories and Origination categories; therefore, it is possible that a permission may be set to View or Change for one, but set to None for the other. When this occurs, the user is only able to use the Search feature for the modules to which he or she is granted permission to access. For example, the Origination Workspace permission under the Application Processing category controls the Search feature for the Origination modules. If the Workspace permission is set to View or Change, but the Origination Workspace permission is set to None, the user is able to click in the Ribbon Bar to perform a full search using the Account Servicing categories, but the Origination categories are not available to the user, and the user is not able to open applications from the Queues, Views, and/or Dashboards page.

Recovery
Name of Permission	Description
Activate Repayment Plan: Allows the user to activate a repayment plan for a recovery account.	None = Activate Repayment Plan button is not enabled for the user on a Repayment Plan screen. Change = Activate Repayment Plan button is enabled for the user on a Repayment Plan screen.
Cancel Repayment Plan: Allows the user to cancel a repayment plan for a recovery account.	None = Cancel Repayment Plan button is not enabled for the user on a Repayment Plan screen. Change = Cancel Repayment Plan button is enabled for the user on a Repayment Plan screen.
Create Repayment Plan: Allows the user to create a repayment plan for a recovery account.	None = Create Repayment Plan button is not available in the workspace ribbon. Change = Create Repayment Plan button is available in the workspace ribbon.
Finalize Recovery Account / Repayment Plan: Allows the user to complete recovery accounts and repayment plans for a recovery account.	None = Finalize Repayment Plan button is not enabled for the user on a Repayment Plan screen. Finalize Recovery Account button is not enabled for the user on an Account screen. Change = Finalize Repayment Plan button is enabled for the user on a Repayment Plan screen. Finalize Recovery Account button is enabled for the user on an Account screen.
Modify Active Repayment Plan Payments: Controls the availability for the Recalculate button within the Repayment Plan Scheduled Payments panel and allows the user to modify an active repayment plan.	None = Recalculate button is not enabled for the user on the Repayment Plan Scheduled Payments panel. Change = Recalculate button is enabled for the user on the Repayment Plan Scheduled Payments panel.
Modify Charge Off Properties: Allows the user to modify information for an account that was recommended and approved for charge-off.	None = User cannot execute the Charge-Off Account workflow step. Change = User can execute the Charge-Off Account workflow step.
Recalculate Accounting Rule Interest: Allows the user to recalculate interest real-time on a recovery account or repayment plan through the Recalculate Interest button added to a recovery account or repayment plan Interest Rates panel.	None = Recalculate Interest button is not enabled for the user on an Interest Rates panel. Change = Recalculate Interest button is enabled for the user on an Interest Rates panel.

Modules

Name of Permission

Description

RECOVERY:

Allows a user to view and change settings within the Recovery page in System Management. Any changes made within the Recovery page apply to all of Recovery in the Lifecycle Management Suite.

None = Users can not view or access recovery settings in System Management > Modules > Recovery.

View = Allows users to view recovery settings, but not make any changes to the settings in System Management > Modules > Recovery.

Change = Allows users to view and make changes to recovery settings in System Management > Modules > Recovery.

System Management

Name of Permission

Description

Data Purging

Allows a user to view and change the data purge settings for Lifecycle Management Suite database tables.

None = Users can not view or access the Data Purging page in System Management > Data Purging.

View = Allows users to view, but not make any changes to the Data Purging page in System Management > Data Purging.

Change = Allows users to view and make changes within the Data Purging page in System Management > Data Purging.

Field List Configurations:

Allows a user to map values from the BANKRUPTCY_PARTY_TYPE and PARTY_TYPE lookups to up to 10 flattened Bankruptcy Party or Legal Party fields, in order to populate the data in letters, views, and/or reports.

None = Users cannot view or access the Field List Configurations page in System Management..

View = Allows users to view the Field List Configurations page in System Management, but not make any changes.

Change = Allows users to view and make changes within the Field List Configurations page in System Management.

GL Accounts (Recovery Module):

Allows a user to view and change GL Accounts when using the Recovery Module. GL Accounts are used when defining the posting rules on a transaction code to determine how a new transaction is allocated on a recovery account.

None = Users can not view or access the GL Accounts page in System Management.

View = Allows users to view but not make any changes to the GL Accounts page in System Management.

Change = Allows users to view and make changes within the GL Accounts page in System Management.

Letter Barcode Activation:

Allows a user to activate the letter barcode process and define the location where scanned files are to be placed for the institution.

None = Users can not view or access the Letter Barcode Activation page in System Management > Communication > Letter Barcode Activation.

View = Allows users to view, but not make any changes to the Letter Barcode Activation page in System.

Change = Allows users to view and make changes within the Letter Barcode Activation page in System Management.

Letter Barcode Scanning Exceptions:

Allows a user to view exception documents, as well as manually attach the documents to the applicable account or cases.

None = Users can not view or access the Letter Barcode Scanning Exceptions page in System Management > Communication > Letter Barcode Scanning Exceptions.

View = Allows users to view, but not make any changes to the Letter Barcode Scanning Exceptions page in System.

Change = Allows users to view and make changes within the Letter Barcode Scanning Exceptions page in System Management.

Letters and Forms:

Allows a user to create letters and other forms to be used when working a case within the system.

None = Users can not view or access the Letters and Forms page in System Management > Communication > Letters and Forms.

View = Allows users to view but not make any changes to the Letters and Forms page in System Management > Communication > Letters and Forms.

Change = Allows users to view and make changes within the Letters and Forms page in System Management > Communication > Letters and Forms.

Transaction Codes (Recovery Module):

Allows a user to track payments, adjustments, and expenses on charged off accounts. Multiple transaction codes can be configured to apply funds differently to an account.

None = Users can not view or access the Transaction Codes page in System Management.

View = Allows users to view but not make any changes to the Transaction Codes page in System Management.

Change = Allows users to view and make changes within the Transaction Codes page in System Management.

System Management - Recovery
Name of Permission	Description
Batch Transaction Import Allows a user to process a Batch Transaction Import	None = System Management screen not available to user. View = System Management screen can be viewed but not edited by user. Change = System Management screen can be viewed and edited by user.
Batch Transaction Import Review: Allows a user to review transactions and allow or prevent them from processing.	None = System Management screen not available to user. View = System Management screen can be viewed but not edited by user. Change = System Management screen can be viewed and edited by user.
Debt Cancellation: Allows a user to view, export and mark recovery accounts as reported to the IRS.	None = System Management screen not available to user. View = System Management screen can be viewed but not edited by user. Change = System Management screen can be viewed and edited by user.
Recovery Approval: Allows a user to view accounts recommended for charge-off and either charge-off the account or reject the recommendation.	None = System Management screen not available to user. View = System Management screen can be viewed but not edited by user. Change = System Management screen can be viewed and edited by user.

Show Screens Tab

Within the Screens tab, assign available screens to the user. If a screen is assigned, the user has access to the screen in the personworkspace.

The screens and boxes that display on the User Edit screen are determined by the enabled module(s). For example, if origination is not active, origination screens are not available to be assigned, and the Available and Assigned Origination Screens boxes do not display on the Screens tab. If the institution uses the Account Servicing modules, as well as the Origination modules, boxes display to assign both Collection screens and Origination screens to the user.

If the security group the user is assigned to has access to the screen, by default the user has access to the screen even if they do not at the user level.

Show Workflows Tab

In the Workflows tab, workflows can be assigned to “None,” “View,” or “View & Execute.”

If a workflow is assigned to None, the user is not able to view the workflow history associated to the workflow nor execute the workflow. If assigned to View, the user can view the workflow history associated to the workflow but cannot execute it. If assigned to View & Execute, the user can view the workflow history and execute the workflow on an account, case, or person.

If the security group the user is assigned to has access to the workflow, the user has access to the workflow by default, even if he or she does not have access at the user level.

In order for a user to have access to a workflow on an Area, the following criteria must be met:

The workflow must be assigned to the Area.
The user must have direct security access to the workflow or access through a security group.

For each Workflow, security can be set on the Area and the User or Security Group level. This security only applies when a user enters the Workspace of an Area. For example, if a workflow is not assigned to an Area, the workflow does not appear in the Area regardless of the security applied to the workflow.

When assigning a workflow to an Area or assigning Users and Security Groups to a workflow, there are three levels of security:

None is the lowest level of security, and View & Execute is the highest level of security.

None
View
View & Execute

Show Dashboards Tab

In the Dashboards tab, assign available dashboards to the user. If assigned the user is able to open the dashboard from the dashboard icon in the Lifecycle Management Suite ribbon.

If the security group the user is assigned to has access to the dashboard, by default the user has access to the dashboard even if they do not at the user level.

Show Views Tab

In the Views tab, assign available views to the user. If assigned, the user is able to open the view from the views icon in the Lifecycle Management Suite ribbon.

If the security group the user is assigned to has access to the view, by default the user has access to the view even if they do not at the user level.

Show Reports Tab

In the Reports tab, assign available reports to the user. If assigned, the user has the ability to view/run the reports from the reports icon in the Lifecycle Management Suite ribbon.

If the security group the user is assigned to has access to a report, the user has access to the report by default, even if he or she does not have access at the user level.

Show Areas Tab

In the Areas tab, assign available areas for the Account Servicing modules to the user. These assigned areas are available to the user in the Areas drop-down in the person workspace.

If the security group the user is assigned to has access to the area, the user has access to the area by default, even if he or she does not have access at the user level.

Show Categories Tab

In the Categories tab, assign available categories to the user.

Show Credentials Tab

User Credentials enable administrators to assign the user specific IDs required for certain functionality throughout the Lifecycle Management Suite.

Credentials may be used as a prerequisite when activating certain third party connectors within the Lifecycle Management Suite. For more information on whether credentials are required for a connector, refer to the applicable Connector Guide.

Administrators can add and remove credentials for a user by means of the Credentials toolbar. Once a credential is added, the below attributes may be assigned in the grid displayed:

If desired, the Connector Credentials Import Process can be manually run on demand from the server where the Lifecycle Management Suite is installed to import user level connector credentials from an Excel file, and automatically populate the credentials within the Credentials tab for each user in the file. Reference the Connector Credentials Import section below for more information on this functionality:

Show Connector Credentials Import

The Connector Credentials Import process provides the ability to easily import third party credentials for all users with access to a connector's functionality, rather than separately adding credentials for each user within the Credentials tab. A system administrator or IT Support representative for the institution can manually run this process on demand from the server where the Lifecycle Management Suite is installed.

The following section provides an overview of the steps to take to import connector credentials for each active user in the Lifecycle Management Suite:

This process does not create new users in the database. In order to import credentials for a user, the user must be active in the Lifecycle Management Suite, and have access to the applicable connector.

Step One: Create and Export Report of Active Users

Prior to running the Connector Credentials Import process, system administrators can create a report from the Reports page in the Ribbon Bar that identifies the username for each active user in the Lifecycle Management Suite. The following fields can be added to the report within the Fields tab of the Report Configuration window to generate a list of the usernames:

User > Username
User > First Name
User > Last Name
User > Is Active

Once created, the report can be run, and then exported to Excel.

If desired, system administrators can also configure a View to include the above fields, which generates a list of the usernames for all active users, and is able to be exported to Excel in the same manner as a report.

After the Excel file is created, system administrators can save the file locally, and use it as a base to create the import file for the Connector Credentials Import process.

Step Two: Create the Import File for the Credentials Import Process

The Excel file of active users from the Lifecycle Management Suite can be used as a base to create the file for the Connector Credentials Import process. System administrators can export an Excel file with credentials from the applicable third party, and then add the credentials to the Excel file created with the user information from the Lifecycle Management Suite.

Each file must include the following three columns of information, and a row for each active user having credentials imported for the connector:

If the Import file is not structured in the following format, the credentials in the file are not able to be imported, and an error is recorded in the Log File during the Import process.

Column

Description

LMS User Name

The username assigned to the user in the Lifecycle Management Suite. This value is used to map the third party credentials to the correct user in the Lifecycle Management Suite during the import. The system populates the associated Connector User Name and Connector Password from the file in the Credentials tab for the user once the Import process completes.

Connector User Name

The username assigned to the user for the third party connector. This value populates within the ID column of the Credentials tab for the user once the Import process completes.

Connector Password

If a password is required, this column includes the value assigned to the user as a password for the third party connector. If a password is not required for the connector, this column can be left blank. The system populates this value within the Password column of the Credentials tab for the user.

For information on whether a password is required for a specific connector, please see the Configuring the Connector topic in the applicable Connector Guide.

Step Three: Run the Connector Credentials Import Process

After the Import file has been created and saved for the connector, the LMS.Core.CredentialsImport exe file process can be manually run from the institution's server.

To run this process:

Open File Explorer on the server where the Lifecycle Management Suite is installed for the institution.
Select the exe folder.
Within the exe folder, right-click on the LMS.Core.CredentialsImport process, and select Run as Administrator.
A window appears to import the file for the Connector Credentials Import process.
Within the window, click Browse... to navigate to the location where the Credentials file is saved. Once the file is selected, the path populates within the File Location box in the Import window.
After the file is located, select a value from the Credential Type drop-down to identify the connector for which the credentials are being imported. This drop-down includes a list of all active connectors for the institution, and identifies the Credential Type to be added to the Credentials tab for each user in the file.
Once the File Location and Credential Type are identified, click Import.

During the import, the system attempts to add a connector credential instance to the Credentials tab in System Management > Users for each user, or row, in the Import file. A Log File is also created on the Share Path to provide an overview of the Import results, including the reasons for any errors.

If the process is successful, a message is received to inform that all credentials were imported successfully, and the following information populates within the Credentials tab for each user in the file:

Type is populated with the value identified in the Credential Type drop-down for the import.
ID is populated with the value of the Connector Username listed in the file for the user.

Password is populated with the value of the Connector Password listed in the file for the user.

If a password is not required for the connector, a blank value populates within the Password column for the user.

If any credentials cannot be imported due to errors, the process does not fail, but a message is received to inform that all records could not be imported successfully.

Step Four: Review Log File

When the Connector Credentials Import process is run, a Log File is automatically created on the Share Path to provide an overview of the Import results for each Credential Type.

The Log file for the Connector Credentials Import can be accessed by navigating to the share folder on the server where the Lifecycle Management Suite is installed, selecting the Log folder, and then opening the Connector Credentials Import file.

This file contains a section for each credential type imported during the Connector Credentials Import process, including the date and time the import was run, as well as the following information about the results of the Import:

Count of the total number of records in the file.
Count of the number of records successfully created.
Count of the number of records with errors.

If a failure occurs, a separate "Failed" entry appears in the file for each record that failed to import for the credential type. This entry lists the number of the record that could not be imported, the LMS username associated with the failed record, the connector username associated with the failed record, and an error message that identifies the reason for the failure. Reference the table below for an overview of the error messages that may appear for a failed record in the Log File for the Connector Credentials Import:

Error Message	Received When
User Name not found	The LMS User Name column does not match an existing user in the Lifecycle Management Suite.
Multiple matches found for User Name	The LMS User Name matches multiple users from the Lifecycle Management Suite.
Password required	A password is required for the Credential Type, and no password is supplied in the file.
Invalid file format	The Import file is in an incorrect format.
The Microsoft Access database engine cannot open or write to the file. It is already opened exclusively by another user, or you need permission to view and write its data.	The Log File is open while the Connector Credentials Import process is being run on the server.

Field

Description

Type

Select the type of user credential being added for the user. Credentials may be system-defined, or specific to a connector. The following credentials are system-defined:

License Number - Used to identify the user that creates a loan application. This value is stored on an application when it is created.
NMLS - Used to identify the users that have obtained an NMLS license.

Enter the ID, or username, assigned to the user for the third party connector.

Password

If a password is required, enter the user's password for the third party connector.

Not all connectors require a password for their user credential; however, if a password is required for a connector, a value must be entered within this field, or an error is received when trying to save the User Edit screen.

For the system-defined credentials, License Number does NOT require a password, while the NMLS credential does require a password to be entered. For information on whether a password is required for a specific connector, please see the Configuring the Connector topic in the applicable Connector Guide.

Confirm Password

If a password is required, re-enter the password defined in the Password field.

Show Restrictions Tab

Restriction Codes are used to identify accounts containing personal information for individuals employed by or related to a financial institution.

This section allows system administrators to restrict users from accessing specific accounts within the Lifecycle Management Suite. System administrators can assign codes to a user, which grant the user access to accounts that are restricted. Additionally, system administrators can prevent users from accessing a person's account by adding the person's identifier to the Restricted Persons grid.

In order to view an account, the user must be granted permission based on both the Restriction Code and Restricted Persons.

Restricted Account

Account Restriction allows access to restricted accounts to be controlled on an account by account basis. Permissions are set on each user to give access to restricted accounts.

To enable Account Restriction in the Lifecycle Management Suite, select the "Enable Account and Person Restrictions" check box on the Security Tab in System Management > Administrative Settings.

The restriction level on an account is determined by the Account Restriction Code field in the Lifecycle Management Suite. If Account Restriction Processing is enabled in the Lifecycle Management Suite, then a user must be given the appropriate permissions in order to view restricted accounts.

By default, all users have access to accounts with a 0 or no Account Restriction Code. To grant a user access to restricted accounts, enable access within the Restricted Account section by entering a value in each applicable Restriction Code field. The possible value for the Restricted Access field on each account are 0-6. The numeric values represent the following types of restricted accounts:

(0) Normal
(1) Restricted
(2) Sensitive
(3) Employee
(4) Employee Family
(5) Employee Sensitive
(6) Employee Sensitive Family

In order for a user to view an account with a Restricted Access level of 1 or higher, the user must have an Account Restriction Access of an equal or greater value. For example, if an account has a Restricted Access level of 3, then a user must have a 3, 4, 5, or 6 entered in the "Restriction Code 1" field in order to view the account.

Restricted Person

System administrators can restrict persons from a user, which prevents that user from gaining access to the person’s account workspace. When a person is restricted, all of the person's related accounts and cases are also restricted. If the user tries to access a restricted person through a search, or when working a queue, a message appears stating that the person/account requires special permission to view.

The system uses the following logic to populate accounts for restricted and non-restricted persons in the workspace:

If a person is restricted, accounts related to the person are not displayed in the workspace, regardless of whether the person is primary or joint.
If an account includes a joint owner, and both the primary and joint are restricted, accounts related to both persons are not displayed in the workspace.
If the primary is not restricted, but the joint is restricted, only accounts related to the primary that do not include the joint owner display in the workspace.
If the primary owner is restricted, but the joint owner is not restricted, only accounts related to the joint owner that do not include the primary are displayed.

Reference the example below for an overview of this functionality:

John is an employee of ABC Financial. He has two accounts at the institution, under membership #12345, on which he is primary, and his wife Jane is a joint owner. Jane also one account of her own under membership #67890. Since John is an employee, users are restricted from accessing his accounts in the workspace; however, Jane is not a restricted person. When Jane contacts the Call Center for ABC Financial, she is only able to conduct business on the one account under her membership #67890 that does not include John; any accounts related to John are not displayed, as they are restricted from appearing in the workspace.

To add a person restriction for a user:

Click within the top of the Restricted Persons grid.
A screen appears asking for the Person Identifier of the person to be restricted.
Select the Identifier Type, and enter the Person Identifier for the person being restricted.
When complete, click .
Upon clicking , the person’s name appears under the Person Identifier.
If correct, click . The Person Identifier is added to the grid.

Show Notification Groups

In the Notification Groups tab, assign available notification groups to the user. If assigned, the user has the ability to receive notifications when a comment is added to an application via email or from the Notifications icon in the ribbon bar.

Show Assignment Groups

This tab is available for all users, but is only used to assign Assignment Groups for use in the Origination modules.

In the Assignment Groups tab, assign the user to the applicable Assignment Groups.

Application Assignment Parameters

Field

Description

Max Number of Applications Assigned

Enter the maximum number of applications that can be assigned to the user.

This is a required field. By default, this parameter is set to 25.

If the assigned user has reached or exceeded the Max Number Applications Assigned, a notification is sent to the Notification Group associated with the Assignment Group.

Available/Assigned Groups

Assign available assignment groups to the user. If assigned, the user is able to have applications automatically assigned.

For more information on Assignment groups, please see the Assignment Groups topic in this guide.

Show Scheduling

The Scheduling tab enables administrators to identify a user’s scheduled time off, so that applications are not assigned to the user during a time that he or she is not available to work applications.

This tab is available for all users, but is only used to set a schedule for users who work in the Origination modules.

The Scheduling tab includes a calendar that displays the days and times that the user is not available to work applications.

At the top of the calendar, administrators are able to click to go back to the previous month, and click to advance to the next month.

To establish a user's schedule, hover over the desired day, and click Add to open the Calendar pop-up window.

Within the Calendar window, use the Date/Time controls to set the user's schedule.

Click the

to open the calendar control. Select the Start/End Date.

Administrators are able to select a date range to set the schedule for multiple days at once.

In the field beneath the date, click the to select the Start/End Time.
Click Save to retain the Time/Date, or Cancel to discard the Time/Date.

Once a schedule is set, the Start/End Time displays in the calendar within Scheduling tab.

Show Lending Settings

Lending Settings enables administrators to assign Application Sources and Restricted Account Types to each user working in the Origination module.

This tab includes the following multi-grids that allow system administrators to determine which application sources and restricted account types a user is able to process applications for in the application workspace:

Grid	Description
Available Application Sources	Contains a list of the values configured for the APPLICATION_SOURCE lookup in System Management > Origination > Field Configurations. Assign application sources to the user by dragging and dropping the desired item(s) from the Available grid to the Assigned grid, or by using the arrow keys.
Assigned Application Sources	Contains a list of all application sources that have been assigned to the user.

Grid	Description
Available Restricted Account Type	Contains a list of the values configured for the RESTRICTION_CODE lookup in System Management > Origination > Field Configurations. Assign restricted account types to the user by dragging and dropping the desired item(s) from the Available grid to the Assigned grid, or by using the arrow keys.
Assigned Restricted Account Type	Contains a list of all restricted account types that have been assigned to the user.

Create New Users

To create a user:

Click . The New User screen appears.
Complete the desired attributes within each tab.
When finished navigating through all of the tabs, and correctly entering information, click to retain the new user, and return to the Users page.
The new user populates in the Users page, and can now be assigned to features throughout the Lifecycle Management Suite.

Copy Existing Users

To copy an existing user:

Select a user within the grid on the Users page, and click .
Modify the information on each tab as needed.
Once all attributes have been defined, click .

Edit Existing Users

To edit an existing user:

Select a user within the grid on the Users page, and click .
Modify the information on each tab as needed.
Once all attributes have been updated, click .

Unlock Deactivated Users

When a user is deactivated, the Active check box on the General tab is disabled.

To unlock a user that has been deactivated, perform the following actions:

Select the deactivated users within the grid on the Users page, and click .
Within the User Information section of the User Information tab, select the Active check box.
Click to retain the user settings.

Delete Users

To delete a user:

Select a user within the grid on the Users page, and click .
A confirmation message appears to confirm that the user should be deleted. Click Yes to delete the user, or No to retain the user.