Temenos Lifecycle Management Suite - Origination Product Guide
Users
Administrator Guide > Security and Permissions > 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:

User Attributes

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

ShowUser Information Tab

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

This tab includes the following three sections:        

User Information

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

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.
Email 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 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.

        

ShowCompany 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.

ShowPersonal 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.

ShowCollection 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.

ShowSecurity 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.

ShowPermissions 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:

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

Application Processing
Name of Permission Description

Add and Delete Account Product Fees :

 

Allows a user to add and remove fees that have been automatically or manually added for an account product.

 

 None = Add and Delete buttons are disabled in the Account Product Fees panel. Edit is disabled for the Account Product Fees grid.

Change = Add and Delete buttons are enabled in the Account Product Fees panel. Edit is enabled for the Account Product Fees grid.
Add and Delete Fees on Application:

Allows a user to add and remove fees that have been automatically or manually added to a loan application.

This permission only provides the ability to add and remove loan fees from an application. To allow a user to add and delete fees for an account product, set the Add and Delete Account Product Fees permission to Change for the user.
None = Add and Delete buttons are disabled in the Fees panel. Edit is disabled for the Fees grid.

Change = Add and Delete buttons are enabled in the Fees panel. Edit is enabled for the Fees grid.
Approve Account:

Allows a user to manually approve an account application.

 None = "Approve" button is disabled in the Workflow and Application Toolbar.

Change = "Approve" button is enabled in the Workflow and Application Toolbar if Status is not Incomplete, Disbursed or Not Eligible.
Approve Loan:

Allows a user to manually approve an application.

 None = "Approve" button is disabled in the Workflow and Application Toolbar.

Change = "Approve" button is enabled in the Workflow and Application Toolbar if Status <> Incomplete, Disbursed or Not Eligible.
Bypass OFAC Alert:

Allows a user to override an OFAC alert presented by the OFAC interface on the OFAC screen and continue to disburse the loan.

 None = user does not have permission to override an OFAC hit and is presented with an override pop-up window.

Change = user has permission to override OFAC hit and is not presented with override pop-up. Also allows user to input credentials into the override pop-up for other users.
Change Applicants Receiving Adverse Action Notice:

Allows user to change the field to send an adverse action notice to a particular applicant from the Reject Application & Withdraw Application windows.

 None = applicant check boxes are disabled on Reject Application and Withdraw Application windows.

Change = applicant check boxes are enabled on Reject Application and Withdraw Application windows.
Change Application After Decision:

Allows a user to change data in fields that have been locked down by the system once a decision has been rendered on the application.

 None = the entire application is read-only (includes both fields and actions) if the application has been decisioned (Decision Date is not null).

Change = the entire application is read-only EXCEPT those fields and actions that are identified as editable post-decision if the application has been decisioned (Decision Date is not null).
Change Application After Disbursement:

Allows a user to change data in fields that have been locked down by the system once an application has been disbursed.

 None = the entire application is read-only (includes both fields and actions) if the application has been disbursed.

Change = the entire application is read-only EXCEPT those fields and actions that are identified as editable post-disbursement if the application has been disbursed.
Change Assets on Application:

Allows a user to manually add assets to an application, delete manually added assets and edit assets that have been added either manually or via a core interface.            

 None = Add/Edit/Delete buttons are disabled on Assets screen.

Change = Add/Edit/Delete buttons are enabled on Assets screen.
Change Effective Date on Application:

Allows a user to update the Effective Date field on the application screen that collects loan term information.

 None = user does not have permission to override and is presented with an override pop-up window if the field has been modified.

Change = user has permission to override and is not presented with override pop-up if the field has been modified. Also allows user to input credentials into the override pop-up for other users.

Change Fees from Account Product:

 

Allows a user to modify the amount of a fee automatically added to an account product by the system.

 

 None = User does not have permission to override the fee amount for an account product, and is presented with an override pop-up window when an Account Product Fee field is modified.                

Change = User has permission to override the fee amount for an account product, and is not presented with the override pop-up when an Account Product Fee field is modified. This permission also allows a user to input credentials into the override pop-up for other users.
Change Fees from Sub-Product:

Allows a user to modify the amount of a fee automatically added to a loan application by the system.

This permission only provides the modify the amount of fee added to a loan application. To allow a user to modify the fee amount for an account product, set the Change Fees from Account Product permission to Change for the user.
None = User does not have permission to override the amount for a loan fee, and is presented with an override pop-up window when a Fee field is modified.

Change = User has permission to override the fee amount for a loan fee, and is not presented with the override pop-up when an Fee field is modified. This permission also allows a user to input credentials into the override pop-up for other users.
Change Interest Rate on Application:

Allows an Underwriter to manually change the interest rate on an application. This field is only available on the Manual Underwriting screen.

 None = "Actual Interest Rate", "Reason for Interest Rate Change", and "Other Reason for Interest Change" fields are disabled on the Approve Application window.

Change = "Actual Interest Rate", "Reason for Interest Rate Change", and "Other Reason for Interest Change" fields are enabled on the Approve Application window.
Change Introductory Term on Application:

Allows a user to manually change the introductory term that is used for Introductory Rate calculations.

 None = Introductory Term field is disabled on the Loan Terms screen.

Change = Introductory Term field is enabled on the Loan Terms field
Change Liabilities on Application:

Allows a user to manually add liabilities to an application, delete manually added liabilities and edit liabilities that have been added either manually or the credit report & core interfaces.

 None = Add/Edit/Delete buttons are disabled on Liabilities screen.

Change = Add/Edit/Delete buttons are enabled on Liabilities screen.
Change Max Cross-sell Amount:

Allows an Underwriter to set a maximum loan cross-sell amount that the sum of all an application’s new/replacement Cross-sell offers cannot exceed.

This field is only available on the Manual Underwriting screen. This does not affect what is offered/pitched as cross-sells; rather, it just affects the max dollar amount an applicant could accept in cross-sell offers without requiring an override.            

 None = "Max Loan Cross-sell Amount", "Reason for Max Cross Sell Amt Change", and "Other Reason for Cross-sell Amt Change" fields are disabled on the Approve Application window.

Change = "Max Loan Cross-sell Amount", "Reason for Max Cross Sell Amt Change", and "Other Reason for Cross-sell Amt Change" fields are enabled on the Approve Application window.            
Change Non-Loan Cross-sell Product Amount:

Allows a user to change the Amount field in the Cross-sell grid for Non-loan Cross-sell products.

 None = The Amount field in the Cross-sell grid is not able to be updated for Non-loan Cross-sell products.

Change = The Amount field in the Cross-sell grid is able to be updated for Non-loan Cross-sell products.
Change Product on Application:

Allows a user to change the product being applied for on an application prior to a decision being rendered on the application.

 None = Change Product button is disabled in the Properties pop-up box.

Change = Change Product button is enabled in the Properties pop-up box.            
Change Source and Channel on Application:

Allows a user to change the application Source and Channel fields during the application process.

 None = Source and Channel fields are disabled in the Properties pop-up box.

Change = Source and Channel fields are enabled in the Properties pop-up box.
Change Variable Rates:

Allows a user to change the Variable Rate fields (listed below) on the Loan Terms screen.

  • First Rate Change Date
  • Rate Change Frequency
  • Rate Change Margin
  • Max Rate Decrease for Loan
  • Max Rate Increase for Loan
  • Max Rate Decrease per Change
  • Max Rate Increase per Change
 None = user does not have permission to edit fields. If fields have been changed by the user they are presented with an override pop-up window.

Change = user has permission to edit fields and is not presented with override pop-up. Also allows user to input credentials into the override pop-up for other users.
Change Vendor on Application:

Allows a user to change the Vendor/Dealer field during the application process.

 None = Vendor field is disabled in the Properties pop-up box when Dealer Purchase or Indirect are selected as Source.

Change = Vendor field is enabled in the Properties pop-up box when Dealer Purchase or Indirect are selected as Source.
Complete Manual To-Do:

Allows a user to complete a Manual To-Do.

 None = The Complete button within the Manual To-Do's Notification pop-up is disabled. User does not have permission to complete Manual To-Dos.

Change = The Complete button within the Manual To-Do's Notification pop-up is enabled. User has permission to complete Manual To-Dos.
Counteroffer- Add, Edit and Delete:

Allows a user to Add, Edit and Delete a Counteroffer on the Counteroffer screen.

 None = User does not have permission to Add, Edit or Delete a Counteroffer.

Change = User has permissions to Add, Edit and Delete a Counteroffer.
Counteroffer - Approve Application on Counteroffer Acceptance:

Allows a user to accept a Counteroffer.

 None = User does not have permission to accept a Counteroffer.

Change = User has permission to accept a Counteroffer.
Create New Application:

Allows a user to enter an account application in the system.

 None = New Application icon is not available within the Ribbon Bar.

Change = New Application icon is available within the Ribbon Bar.

Create New Member Account for an Existing Member:

Allows a user to create a new member account for an existing account holder during the application process.

None = Generate button is disabled in the Change Account/Loan Number screen.

The Generate button may also appear disabled if other configurations are not set by the system administrator. For more information, please see the Generating Account Numbers section of the Funding topic in the User Guide.

Change = Generate button is enabled for an existing account holder in the Change Account/Loan Number screen.
Cross-sells In Loan Amount Exceed Approval Tolerance:

Allows a user to override the Approval Tolerance Amount that is set on the sub-product definition (only if it is exceeded because of cross-sells being included in the loan amount, such as GAP & MBC).

 None = user does not have permission to override and is presented with an override pop-up window.

Change = user has permission to override and is not presented with override pop-up. Also allows user to input credentials into the override pop-up for other users.
Decline Account:

Allows a user to manually decline an account application.

 None = The Decline button is not able to be selected in the Application Toolbar and Workflow.

Change = The Decline button is able to be selected in the Application Toolbar and Workflow if Status is not Incomplete, Disbursed or Not Eligible and applicant is not a current account holder.            
Decline Loan:

Allows a user to decline a loan application.

 None = "Decline" button is disabled in the Application Toolbar and Workflow.

Change = "Decline" button is enabled in the Application Toolbar and Workflow if Status <> Incomplete, Disbursed, or Not Eligible.
Disburse Account Product:

Allows a user to disburse and book the account product to the Core system.

 None = The Disburse button is not able to be selected in the Application Toolbar and Workflow.

Change = The Disburse button is able to be selected in the Application Toolbar and Workflow.
Disburse Loan:

Allows a user to Disburse and book the loan to the core system.

 None = The Disburse button is not able to be selected in the Application Toolbar and Workflow.

Change = The Disburse button able to be selected in the Application Toolbar and Workflow.
Do Not Pull Credit:

Allows the user to select to not pull credit for a particular applicant on an application.

 None = “Do Not Pull Credit” checkbox is disabled on the screen used to collect applicant information.

Change = “Do Not Pull Credit” checkbox is enabled on the screen used to collect applicant information.
Edit Adverse Action Reasons:

Allows a user to add Reject & Adverse Action Reasons to an application via the Other Actions button.

 None = "Collect Adverse Actions" is disabled in the Other Actions dropdown.

Change = "Collect Adverse Actions" value in the Other Actions dropdown list is active and can be selected.

Edit All Comments on Application:

 

Allows a user to edit comments added by other users within the Comment History in an application.

Comments added by a third party, or flagged as external cannot be edited.

None = Users are not able to edit comments added by another user within the Comment History in an application. The Edit button is disabled within the Comment History screen and panel when a comment from another user is selected within the grid.

 

Change = Users are able to modify all comments in an application. The Edit button is enabled within the Comment History screen and panel when any comment is selected within the grid.
Edit Disbursement Date:

Allows a user to edit the Disbursement Date field.

 None = Disbursement Date is disabled on the application screen that collects loan term information.

Change = Disbursement Date field is enabled on the application screen that collects loan term information.
Edit Doc Stamps Program:

Allows a user to edit fields in the application related to the Doc Stamps Program.

 None = User does not have permission to edit fields.

Change = User has permission to edit fields.
Edit Finance Charge on Application Fee:

Allows a user to set the flag for a fee to be considered a finance charge.

 None = Finance Charge column is disabled on the Fees grid on the Fees panel.

Change = Finance Charge column is enabled on the Fees grid on the Fees panel.
Edit First Notification, Second Notification and Expiration Dates:

Allows a user to edit these fields on the Loan Terms screen.

 None = User does not have permission to edit fields.

Change = User has permission to edit fields.            

Edit Own Comments on Application:

 

Allows a user to edit their own comments within the Comment History in an application.

Comments flagged as external cannot be edited.

None = Users are not able to edit comments within the Comment History in an application. The Edit button is disabled within the Comment History screen and panel.

 

Change = Users are only able to modify comments added by their user in an application. The Edit button is enabled within the Comment History screen and panel when a comment added by their user is selected within the grid.
Exclude Applicant From Precise ID:

Allows a user to exclude an applicant from being processed through the Precise ID interface.

 None = "Exclude Applicant from Precise ID" checkbox on Applicants screen is disabled.

Change = "Exclude Applicant from Precise ID" checkbox is enabled.
Exclude Payee from OFAC:

Allows a user to exclude a check payee from being checked via the OFAC interface during the Disbursement.

 None = "Do Not Run OFAC" Checkbox is disabled on Edit Payee OFAC Information window.

Change = "Do Not Run OFAC" Checkbox is enabled on Edit Payee OFAC Information window.
Get Vehicle Valuation in Application:

Allows a user to get a book value on a vehicle within an application via the NADA or KBB interfaces.

 None = "Get Valuation" button is disabled on the application screen that collects Collateral information, when Source = NADA or KBB.

Change = "Get Valuation" button is enabled on the application screen that collects Collateral information, when Source = NADA or KBB.
Initial Amount Exceeds Min/Max for Sub-Product:

Allows a user to override the Min/Max Amount values that are set at the sub-product definition. For example: New Auto has a min amount of $1500.00. An application is being submitted and the Requested Amount is $1000.00. An override box pops-up for users who do not have this permission and requires someone with this authority to put in their credentials in order for the user to proceed with the application.

 None = user does not have permission to override and is presented with an override pop-up window.

Change = user has permission to override and is not presented with override pop-up. Also allows user to input credentials into the override pop-up for other users.
LO Approval – Display Adverse Actions:

Allows user to view/edit the Adverse Action panel on the Approve Application screen.

 None = Adverse Action sub-panel is not displayed on the Approve Application screen.

Change = Adverse Action sub-panel is displayed and editable on the Approve Application screen.

Loan Covenants – Add:

 

Allows a user to add loan covenants to a loan application.

None = Add button is disabled in the Loan Covenants panel.

 

Change = Add button is enabled in the Loan Covenants panel.

If a user is granted permission to add loan covenants, the Loan Covenants - Change permission should also be set to Change for the user to ensure he or she is able to set values for the convenant once it is added.

Loan Covenants – Change:

 

Allows a user to modify a loan covenant on a loan application.

 

None = The Edit button is disabled in the Loan Covenants panel, and the fields that support inline editability are read-only in the panel grid.

 

Change = The Edit button is enabled in the Loan Covenants panel, and inline editing is available for the applicable fields in the panel grid.

Loan Covenants – Allow Delete:

 

Allows a user to remove loan covenants that have been automatically or manually added to the application.

None = The Delete button is disabled in the Loan Covenants panel.

 

Change = The Delete button is enabled in the Loan Covenants panel.

Loan Covenants - Waive on Application:

 

Allows a user to mark a loan covenant as waived on a loan application.

None = Waive check box is disabled when editing a loan covenant in the Loan Covenants panel.

 

Change = Waive check box is enabled when loan covenant in the Loan Covenants panel.
Loan Cross-sells Exceed Max Amount:

Allows a user to override the Max Loan Cross-Sell Amount (the sum of all an application’s new/replacement Cross-sell offers) that can be set by an underwriter on the manual underwriting screen.

For example: An underwriter has set the Max Loan Cross-Sell amount to be $10,000.00 on the underwriting screen. The end user gets to the Cross-Sell screen and pitches the Cross-sell products. The applicant wants all the available cross-sell offers, which total $15,000.00. An override box appears for users who do not have this permission and requires someone with this authority to put in their credentials in order for the user to proceed with the application.

 None = user does not have permission to override and is presented with an override pop-up window.

Change = user has permission to override and is not presented with override pop-up. Also allows user to input credentials into the override pop-up for other users.
LTV Exceeds Min/Max for Sub-Product:

Allows a user to override the Min/Max LTV value that is set at the sub-product definition. For example: New Auto has a max LTV of 110%. An application is being processed and the LTV is calculated to be 112%. An override box pops-up for users who do not have this permission and requires someone with this authority to put in their credentials in order for the user to proceed with the application.

 None = user does not have permission to override and is presented with an override pop-up window.

Change = user has permission to override and is not presented with override pop-up. Also allows user to input credentials into the override pop-up for other users.
Manually Disburse Application:

Allows a user to mark an application as being disbursed to core if an error message was returned during the disbursement process. If the box is checked, the system does not try to create the record in core via the interface and the end user needs to manually create the record in the core system.

 None = Disbursement Complete checkbox is available and disabled.

Change = Disbursement Complete checkbox is available and enabled.            

Origination Workspace

 

Allows a user to access and use the Search feature in the Ribbon Bar.

 

 None = Users are unable to use the Search feature, and the  is disabled in the Ribbon Bar. Additionally, users are unable to open applications from the Queues, Views, and/or Dashboards page.

View = Users can use the Search feature, and open applications from the Queues, Views, and/or Dashboards page; however, the selected application opens as READ ONLY in the workspace, and no changes can be made. Only a comment can be added to an application while in this state.

Change = Users can access applications using the Search feature, as well as from the Queues, Views, and/or Dashboards page, and can perform actions within the selected application when open in the workspace.

In addition to having View or Change permission for the Origination Workspace, a user must also be assigned to the specific queue, view, or dashboard in order to open applications.
               
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 Workspace permission under the Collections category controls the Search feature for the Account Servicing modules. If the Origination Workspace permission is set to View or Change, but the Workspace permission is set to None, the user is able to click  in the Ribbon Bar to perform a full search using the Origination categories, but the Account Servicing categories are not available to the user, and the user is not able to open person workspaces from the Queues, Views, and/or Dashboards page.
Override Identity Results:

Allows a user to override the Precise ID interface results.

 None = User does not have permission to override Precise ID results and is presented with an override pop-up window.

Change = User has permission to override Precise ID results and is not presented with override pop-up. Also allows user to input credentials into the override pop-up for other users.
Pin Application to Queue:

Allows a user to manually Pin and UnPin applications from queues.

 None = Pin to Queue and Un-pin buttons are disabled on the application toolbar.

Change = Pin to Queue and Un-pin buttons are enabled on the application toolbar.

Recurring Fees - Add and Delete:

 

Allows a user to add recurring fess to a loan application, as well as remove recurring fees that have been automatically or manually added to the application.

None = Add and Delete buttons are disabled in the Recurring Fees panel.

 

Change = Add and Delete buttons are enabled in the Recurring Fees panel.

Recurring Fees - Change Recurring Fees:

 

Allows a user to modify a recurring fee on a loan application.

None = Fields are read-only in the Recurring Fees panel, and cannot be modified.

 

Change = Inline editing is available in the Recurring Fees panel, and users are able to modify field values within the grid.

Recurring Fees - Waive on Application:

 

Allows a user to mark a recurring fee as waived on a loan application.

None = Waive check box is disabled when editing a fee in the Recurring Fees panel.

 

Change = Waive check box is enabled when editing a fee in the Recurring Fees panel.
Remove Decision on Application:

Allows a user to remove the decision that has been rendered on an application and reprocess the application.

 None = Remove Decision button is disabled in the Application Toolbar.

Change = Remove Decision button is enabled in the Application Toolbar.
Remove Withdraw Status From Application:

Allows a user to remove the withdraw status from the Other Actions menu on the Application.

 None = The Remove Withdraw button is disabled in the Application Toolbar.

Change = The Remove Withdraw button is enabled in the Application Toolbar.
Send Custom Emails:

Allows a user to send a custom email from the Other Actions drop-down within an Application.

 None = The Compose Email button is disabled on the Other Actions drop-down menu within an Application.

Change = The Compose Email button is enabled on the Other Actions drop-down within an Application.
Stipulations - Add/Clear:

Allows a user to manually add stipulations and mark a stipulation as being met.

 None = User cannot add stipulations. Met checkbox is disabled when editing stipulations in the Stipulations panel.

Change = User can add new stipulations. Met checkbox is enabled when editing stipulations in the Stipulations panel.
Stipulations – Allow Delete:

Allows a user to delete stipulations.

 None = User is not able to delete stipulations.

Change = User is able to delete stipulations.
Stipulations – Change stipulations:

Allows a user to modify the stipulation that was added and modify if the stipulation is required for approval or disbursement.

 None = Stipulation and Required For fields are disabled when editing stipulations in the Stipulations panel.

Change = Stipulation and Required For fields are enabled when editing stipulations in the Stipulations panel.
Stipulations – Do Not Require Comments:

Allows a user, who has permission to mark stipulation as met or waived, to proceed without adding a comment on the stipulation.

 None = User must enter a comment if they select waive/met.

Change = User is able to select waive/met without entering a comment.
Stipulations - Waive on Application:

Allows a user to mark a stipulation as being waived.

 None = Waive checkbox is disabled when editing stipulations in the Stipulations panel.

Change = Waive checkbox is enabled when editing stipulations in the Stipulations panel.
Suggest Decline for Application:

Allows a user to suggest an application be declined.

 None = "Suggest Decline" button is disabled in the Decline Application window.

Change = "Suggest Decline" button is enabled in the Decline Application window if Status <> Incomplete, Disbursed, or Not Eligible.

Unmask Lending Fields TIN and DOB:

 

Allows a user to view unmasked values for the TIN and Date of Birth fields in an application.

None = User is unable to view an unmasked value of the TIN and Date of Birth fields in an application. When the user hovers over the  icon for the TIN or Date of Birth field, a tool-tip is presented to the user to identify that permission to unmask the field is not enabled.

If this permission is set to None, but the View Masked Fields permission is set to View, the user is able to view an unmasked value for TIN and Date of Birth fields when the  icon is clicked.

 

View = User is able to view the full unmasked value of the TIN and Date of Birth fields in an application.
Update Application From Core:

Allows a user to update the Application From the Core by selecting the Core Update from the Core drop-down in the Application toolbar.

 None = The Last Core Update button is disabled in the Core drop-down in the Application toolbar.

Change = The Last Core Update button is enabled in the Core drop-down in the Application toolbar.

View Masked Fields:

 

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

 

None = User is unable to view the value of masked fields in an application. 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.

If this permission is set to None, but the Unmask Lending Fields TIN and DOB permission is set to View, the values of the TIN and Date of Birth fields are fully visible in the application.

 

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

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

Allows a user to withdraw an application from processing.

 None = Withdraw button is disabled on workspace toolbar.

Change = Withdraw button is enabled on workspace toolbar.

 

Origination Tools
Name of Permission Description
Ad-hoc Credit Report:

Allows the user to pull a credit report without starting an application.

 None = Credit Report Tool not available on Desktop ribbon.

Change = Credit Report Tool available on Desktop ribbon.

Ad-hoc Loan Calculator:

 

Allows the user to perform calculations from the Loan Calculator in the  Desktop Ribbon.

 

 None = User is not able to access the Loan Calculator in the Desktop Ribbon. Upon trying to access the calculator, the user is presented with a Permission Denied error.                

Change = User is able to access and perform calculations from the Loan Calculator in the Desktop Ribbon.
Ad-hoc Vehicle Valuation:

Allows the user to get a book value for a vehicle without starting an application.

 None = Vehicle Valuation Tool not available on Desktop ribbon.

Change = Vehicle Valuation Tool available on Desktop ribbon.
Application Lock Management:

Allows the user to view and/or unlock applications that are currently in use/locked by another user.

 None = Application Lock Management Tool not available on Desktop ribbon.

View = Application Lock Management Tool available on Desktop ribbon in a view only mode

Change = Application Lock Management Tool available on Desktop ribbon in view and edit mode.
Promotions:

Allows a user to view and work the offers for each promotion as well as provides the ability to create an application from an offer.

 None = Promotions icon not available on Desktop ribbon.

Change = Promotions icon available on Desktop ribbon.

 

Modules
Name of Permission Description
ORIGINATION:

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

None = Users cannot view or access origination settings in System Management > Modules  > Origination.

 

View = Allows users to view origination settings, but not make any changes to the settings under System Management > Modules  > Origination.

Change = Allows users to view and make changes to origination settings under System Management > Modules > Origination.

 

System Management
Name of Permission Description
Alerts:

Allows a user to view and edit system-wide alerts that appear each time a user logs into the system.

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

 

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

Change = Allows users to view and make changes within the Alerts page in System Management.
Configuration Export:

Allows a user to view, edit and change Configuration Manager Exports.

 None = Users can not view or access the Export Configurations page in System Management > Configurations.

Change = Allows users to view and make changes within the Export Configurations page in System Management > Configurations.
Configuration Import:

Allows a user to view, edit and change Configuration Manager Imports.

 None = Users can not view or access the Import Configurations page in System Management > Configurations.

Change = Allows users to view and make changes within the Import Configurations page in System Management > Configurations.
Connectors:

Allows a user to access connectors that the institution utilizes within System Management.

None = Users do not have access to the Connectors folder in System Management.

 

View = Allows users to access the connector pages but not save any changes within the page.

Change = Allows users to have access to all Connectors in the Connectors folder in System Management.
Custom Field Management:

Allows a user to create custom fields that are used to extend the Lifecycle Management Suite database. Custom fields can be used throughout the entire system.

None = Users can not view or access the Custom Fields page in System Management.

 

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

Change = Allows users to view and make changes within the Custom Fields page in System Management.
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.
Exports:

Allows a user to view and change export settings within System Management. 

None = Users cannot view or access the Exports page in System Management.

 

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

Change = Allows users to view and make changes within the Exports page in System Management.
Security Groups:

Allows a user to view and change Security Groups in System Management. Security Groups are designed so that managers can set Temenos Lifecycle Management Suite access for a group rather than every individual user.

 

None = Users can not view or access the Security Groups page in System Management > Groups > Security Groups.

 

View = Allows users to view but not make any changes to the Security Groups page in System Management > Groups > Security Groups.

Change = Allows users to view and make changes within the Security Groups page in System Management > Groups > Security Groups.
Users:

Allows a user to view and change existing users within the system, as well as create new users.

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

 

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

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

 

 

System Management - Loan
Name of Permission Description
Cross-sell Product Management:

Allows a user to create and maintain the products that are available for cross-sell offers.

 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 Protection Plan Management:

Allows a user to maintain the user friendly descriptions and core codes for credit insurance/debt protection options that are imported from the calculator rate file.

 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.            
HMDA Reporting Management:

Allows a user to generate a properly formatted FFIEC HMDA-LAR file. The administrator has the ability to review/exclude specific applications, validate data, correct incorrect or missing data, and generate a summary report.

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.
Loan Application Type Management:

Allows a user to define a hierarchy of products (Categories, Products and Sub-Products).

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.

Loan Covenants Management:

 

Allows a user to create and manage loan covenants for the institution.

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.
Promotions Management:

Allows a user to create and manage promotions.

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.
Risk Model Management:

Allows a user to define a naming convention for risk tiers (e.g. A+, A, B, Platinum, Gold, Silver), and to create/maintain the risk models.

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.
Vendor Management:

Allows a user to create and manage a list of Vendors/Dealers that the financial institution does business with.

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.
Workflow Model Management:

Allows a user to configure the workflow screens that are presented for a loan application. Also enables a user to assign Validation rules.

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.

 

System Management - Origination
Name of Permission Description

Applicant Types:

 

Allows a user to create and maintain the applicant types available to assign within an applcation.

 

None = Applicant Types screen is not available to the user.

 

Change = Applicant Types screen can be viewed and editied by the user.

Base Rate Tables Management:

 

Allows a user to create and maintain the base interest rate table for pricing applications.

 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 Disbursement Management:

Allows a user to view and reconcile batches disbursed to credit card processors for fulfillment.

 None = Batch Disbursement Management screen is not available to user.

View = Batch Disbursement Management screen can be viewed but not edited by user.

Change = Batch Disbursement Management screen can be viewed and edited by user.
Batch Queue Processing:

Allows a user to view and schedule Batch Queuing process to run ad-hoc.

 None = User is not able to schedule the Batch Queuing Process to run.               

Change = User is able to view and schedule the Batch Queuing Process.
Decision Model Management:

Allows a user to create and maintain the decision models used to underwrite an application.

 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.
Document Template Management:

Allows a user to create and maintain Document Templates for use with third party connectors such as DocuSign and Silanis.

 None = System Management screen not available to user.

View = System Management can be viewed but not edited by user.

Change = System Management screen can be viewed and edited by user.
Editability:

Allows a user to create and maintain Field, Collection and Action Editability rights.

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

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

Change = Editability screen within System Management screen can be viewed and edited by user.
Email Template Management:

Allows a user create and maintain Email Templates for use within the Application.

 None = System Management screen not available to user.

View = System Management can be viewed but not edited by user.

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

End Exclusive Rule Authoring Session:

 

Allows a user to end an exclusive Rule Authoring session in System Management > Origination > 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.
Field List Configurations:

Allows a user to map up to 20 commonly-used Aggregates and Ratios and 10 commonly-used Scores for reporting.

 None = Field List Configurations screen in System Management is not available to user.

View = Field List Configurations screen in System Management can be viewed but not edited by user.

Change = Field List Configurations screen in System Management can be viewed and edited by user.
Notification Groups:

Allows a user to view and change the notification groups in System Management. The Notification Group page allows administrators to group users together into functional groups that are able to receive notifications about Applications based on Lifecycle Management Suite events.

None = Users can not view or access the Notification Groups page in System Management > Groups > Notification Groups.

 

View = Allows users to view but not make any changes to the Notification Groups page in System Management > Groups > Notification Groups.

Change = Allows users to view and make changes within the Notification Groups page in System Management > Groups > Notification Groups.
Origination Queue Management:

Allows a user to create queues, which provide a way to manage applications throughout the loan process.

 None = System Management screen is not available to the user.

View = System Management screen can be viewed, but not edited by the user.

Change = System Management screen can be viewed and edited by the user.

Portfolio Simulation:

 

Allows a user to create, manage, and run portfolio simuations in the Lifecycle Management Suite.

 

 None = Portfolio Simulations page is not available to the user.

View = Portfolio Simulations page can be viewed, but users are unable to create, delete, start, and/or stop simulations.

Change = Portfolio Simulations page can be viewed, and users are able to create, delete, start, and/or stop simulations.
Pricing Model Management:

Allows a user to assign pricing rules that determine the final rate for a product.

None = System Management screen is not available to the user.

 

View = System Management screen can be viewed, but not edited by the user.

Change = System Management screen can be viewed and edited by the user.
Rules Management:

Allows a user to author and maintain a library of all business rules needed by the loan and account origination modules (e.g. decisioning, data validation).

 None = System Management screen is not available to the user.

View = System Management screen can be viewed, but not edited by the user.

Change = System Management screen can be viewed and edited by the user.            
Screens:

Allows a user to author and maintain screens.

 None = System Management screen is not available to the user.

View = System Management screen can be viewed, but not edited by the user.

Change= System Management screen can be viewed and edited by the user.            
Summary Screens Management:

Allows a user to create and manage the summary panels that are available as part of Loan Application Types.

None = System Management screen is not available to the user.

 

Change = System Management screen can be viewed and edited by the user.
Validation Model Management:

Allows a user to create and manage validation models.

 

 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.
WebLoan:

Allows a user to configure the workflow models, settings and panels for WebLoan applications, and administrator to configure header and footer messages to be used on the various pages of the WebLoan.

 None = System Management items not available to user.

View = System Management items can be viewed but not edited by user.

Change = System Management items can be viewed and edited by user.

 

Virtual Capture
Name of Permission Description
Blacklisted IP Addresses

Allows a user to view and edit the Blacklisted IP Addresses screen in System Management.

 None = System Management screen not available to the user.

View = System Management screen can be viewed, but not edited by the user.

Change = System Management screen can be viewed and edited by the user.
Virtual Capture Screens

Allows a user to view and change screens in System Management. 

 None = System Management screen not available to the user.

View = System Management screen can be viewed, but not edited by the user.

Change = System Management screen can be viewed and edited by the user.
Virtual Capture Settings

Allows a user to view and change the settings for each instance of Virtual Capture, as well as the cross-sell products and loan/account products available in Virtual Capture. This permission controls a user's ability to access and modify information within the following System Management screens:

  • Virtual Capture Settings
  • Virtual Capture Products
  • Virtual Capture Cross-Sells
 None = System Management screens are not available to the user.

View = System Management screens can be viewed, but not edited by the user.

Change = System Management screens can be viewed and edited by the user.
Virtual Capture Workflow Model Management

Allows a user to configure the workflow screens presented for a web application.

 None = System Management screen not available to the user.

View = System Management screen can be viewed, but not edited by the user.

Change = System Management screen can be viewed and edited by the user.

ShowScreens 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 application workspace.

The screens and boxes that display on the User Edit screen are determined by the enabled module(s). For example, if loan or account 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.

 

ShowWorkflows 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

ShowDashboards 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.

ShowViews 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.

ShowReports 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.

ShowAreas 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.

ShowCategories Tab

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

ShowCredentials 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:

ShowConnector 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.
ID 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.

ShowRestrictions 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  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:

ShowNotification 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.

ShowAssignment Groups

       

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. 

ShowScheduling

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.

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.

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

ShowLending Settings

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

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:

Copy Existing Users

To copy an existing user:

Edit Existing Users

To edit an existing user:

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:

Delete Users

To delete a user:

 

 

©2020 Temenos Headquarters SA - all rights reserved.

Send Feedback