User Ids are assigned Security Codes to determine the security level and roles. These are also used in the system to create permission as well as limit certain features based on the role of each user.
The purpose of the User Id Table is for the addition, configuration and maintenance of all users of Impact, including clients that are configured to access the system via the Client Portal.
User Id Navigation Menu
User Id Maintenance UI Window
Once the Users option is selected, the following window is displayed
User Id Maintenance Window
|Exit -||Navigates back to the main IMPACT window without making any changes|
|Add -||Creates a new record.|
|Edit -||Modify an existing record.|
|UW -||User Windows (User Level)|
|Delete -||Removes an existing record.|
|Print -||Prints the record list to the print queue|
User Id Info Tab
Objective: The pupose of the User Id Info tab is to group all the parameters related to the user.
User Id Info Tab Window
|User Id Code -||Select an alpha-numeric entry of up to six characters in length. Typically the initials of the user or the first initial and the first five characters of the last name are used here. For a Client that will access Impact via the Client Portal, the Client Code is a good option here. If you are using strong passwords, user ids must first be turned on under the MAIN system parameters tab. Then, user id codes must be at least 7 characters in length, up to 12 are allowed.|
|User Disabled:||This option defines what is the current status of the user. Options are “No” for users that are currently active and allowed to access Impact; “Yes” for users that are currently disabled and not allowed to access Impact; and “Lock” for users that are temporarily disabled. Warning: Users should not be deleted from the system but disabled by setting this option to “Yes” when they are no longer needed. You must contact CSS IMPACT! Support to have a disabled user changed from YES to NO.|
|User Id Name -||Enter the full name or description of the user.|
|Expire Date -||This will be the date the password will expire.|
|Expire Password -||This option, in combination with the “Expire Date” field, allows the definition of a date in which the user will be forced to change the password to access Impact. Set this option to “Yes” and leave the “Expire Date” field set to 00/00/00. The first time the user logs in, they will be prompted to change their password, and the Expire Date will be set for that password to expire in 90 days. The first time the user logs in past that date, they will again be prompted to change their password. This option MUST be set to Yes if you are using strong passwords. Setting this option to “No” will never require a password change.
|User Password -||
Select an alphanumeric password of up to twelve characters in length. If strong passwords is turned on, the following requirements must be met by the password entered:
1.Password must be a minimum of 7 characters and can be a maximum of 12 characters long.
2.Password must contain: at least one lower case alpha character, one numeric character, and either one uppercase alpha character or one special character (i.e. *&^%$#@! Etc.).
3.Password is required to be changed a minimum of every 90 days, and the same password cannot be used if it was one of 5 last passwords.
|Mobile App -||If the user is set to Yes then the user will be able to login to the mobile app.|
|Stats Desk -||This option defines what Desk will be the master tracker for the statistics of this user. The statistics can be viewed using the Desk Table for the selected Desk and are displayed in the Stats tab of the Desk configuration screen.|
|Dashboard User -||(currently in development)|
|Individual Queue -||This option defines whether the user will have his/her own individual queue, will have a “shared” queue or have no access to the queue. Select “Yes” from the pull-down menu if this user will have his/her own individual queue. They will have access in their print queue only to reports they generated. (The queue can be found in “Impact – Queue”). Select “No” from the pull-down menu if the user may view reports that everyone in the system has requested or executed. Select “None” if this user will not have access to the print queue.|
|Security Code -||Select a Security Code from the pull-down menu. The Security Code will drive the permissions and rights of this user as defined in the Security Code table settings.|
|Hipaa Certified -||If a user is designated as HIPAA CERTIFIED = YES, then they will have access to accounts designated as CREDITOR CLASS = 02 Medical/Health care. (This is set on the coding tab of the client set up table)|
|Group Code -||Select a Group Code from the pull-down menu. The Group Code will assign this user a group as defined in the Group Code table settings. Groups are useful in areas like Reports and State Compliance tables.|
|Enable Marcos -||A “macro” is a tool that allows the execution of up to three Result Codes simultaneously while in the Work Card. These can be defined in the Tables – Collection Tables – Macro Code Table. Selecting “Yes” from the pull-down in this option will allow this user to have access to view and execute macros in the Work Card. Selecting “No” will turn-off this option for this user.|
|Maximum Daily Letters - Credit Reports -||Enter the maximum number of daily letters and credit reports this user is able to request. The range is from 001 - 998. Use of 000 or 999 will allow unlimited.|
|Email Access -||
There are 8 options for this field
1 - None: User has no permissions to use the email application.
2 - User ID Table: User has permissions to send emails only to internal users with an email address in file. This option prevents the user from updating the auto-populated “Subject” line.
3 - FwdAty Contacts: User has permissions to send emails only to Forwarding Attorneys and Companies with contacts that contain an email address in file. This option prevents the user from updating the auto-populated “Subject” line.
4 - User ID & FwdAty: User has permissions to send emails to both internal users and to Forwarding Companies and Attorneys that contain an email address in file. This option prevents the user from updating the auto-populated “Subject” line.
5 - Unrestricted: User has permissions to send emails to all entities including any email address. This option allows the user to edit the auto-populated “Subject” line.
6 - Dem Only: User has permissions to send emails to demographics that contain an email address in file. This option prevents the user from updating the auto-populated “Subject” line.
7 - Dem and UserID:User has permissions to send emails to both demographics and to internal users that contain an email address in file. This option prevents the user from updating the auto-populated “Subject” line.
8 - Dem and FwdAty: User has permissions to send emails to demographics and to Forwarding Attorneys and Companies with contacts that contain an email address in file. This option prevents the user from updating the auto-populated “Subject” line.
|Salesperson Code -||If the user that is being defined is a Salesperson, this option allows the linking of this user id to a specific Sales Code (Impact – Company Tables – Salesperson Table) for reporting purposes.|
|Skip Tracking Requests - Bankruptcy Requests -||Enter the maximum number of daily skip tracing and bankruptcy requests this user is able to request. range is from 001 - 998. Use of 000 or 999 will allow unlimited.|
|Adhoc Reports -||
AdHoc Report is a powerful tool that allows for the customization of a wide variety or reports. This option can be located in Impact – Reports – Actuary Reports. This option defines whether or not the this user will have access to this tool. Select “Yes” from the pull-down menu to allow access. Select “No” to restrict access to this tool.
|Department Security -||Assign access to accounts based upon either DEPARTMENT SECURITY or DESK SECURITY, not both. Select “Include” or “Exclude” from the pull-down menu to define which of these two parameters will apply to the Department selection below.|
|Fwd Company / Attorney -||If the user that is being defined is a Forwarding Company or an Attorney, this option allows the association of the Forwarding Company or Attorney code with the user id. These codes can be defined from the Tables – Forwarding Tables – Forwarding Company/Attorney Table menu. In the Legal Portal, this user will then have access to accounts that have been forwarded to this code.|
|Departments -||Select from the pull-down menu which Departments this user has permissions (or not, depending on the selection above) to access. Since all accounts must belong to a Desk and a Desk must belong to a Department, this selection ultimately defines the set of Desks that the user is restricted or has access to based upon the department the desk is in.|
|Internal Attorney -||If the user that is being defined is an attorney, this option allows the linking of this user id to an internal attorney for reporting purposes.|
|Release Note Notify -||Impact is continuously updated with new releases and features through frequent deployments. When a new version of the software has been deployed to your server, the Release Notes are updated with the changes introduced to the system. Setting this option to “Yes” will notify this user when a new release was deployed to the system via a dialog box that will pop-up when the user logs in. Selecting “No” will restrict the user from this feature.|
|Desk Security Desks -||Assign access to accounts based upon either DEPARTMENT SECURITY or DESK SECURITY, not both. The Desk Security pull-down field works in conjunction with the Desks fields immediately below. The options from the pull-down field are “Include” and “Exclude” and make reference to the Desk selection below. The purpose of these two fields is to define which Desks the user is allowed to access and which he/she is restricted from. Use “Include” or “Exclude” and then select the Desks that you wish to allow or restrict access to this user from the Desks options below.|
|View Restricted Desks -||This option allows the user to view accounts on Desks that have been restricted in the option above. Selecting “Yes” from the pull-down menu will allow limited access to this user to Desks that are in the list of restricted Desks (not included in the option Desk Security – Desks). Selecting “No” will prevent this user from any access to restricted Desks. Limited access means they can work the account, enter activity and result codes and notes. However, they will not be able to change the status, desk and other important aspects of the account. The main purposes of this limited access is to allow collectors to handle accounts for others when they are not available or to do Talk Off's for others/|
|View Jdmt Acnts -||This option defines whether the user can view accounts that have a judgment entered in them. This option works in conjunction with the option below as to the number of days this user is restricted from viewing judgment accounts.|
|Days to Restrict -||Enter the number of days the user will be restricted from viewing judgment accounts. This field works in conjunction with the View Jdmt Acnts field above. Once a judgment is entered on an account, access is restricted XX number of days from the date of the judgment to the current date. (IE. an account with a judgment of 1-15-2012 would not be accessible until 4-15-2012 if this field was set to 90.)|
|Allow Split Credit -||There are 2 options for this field Yes and No. When the option is set to Yes the user will be included on the split 1 - split 10 fields under the commission credit.|
|Change Comm Credit -||There are 4 options for this field:
|Email Address -||Enter user’s email address. This is strictly for informational purposes only at this time. You are discouraged from using this for any other purpose.|
Client Portal Tab
Objective: The purpose of this tab is to configure how the user will be able to interact with the client portal
Client Portal Tab Window
|Client Portal User -||This option defines whether the user will be accessing the system via the Client Portal. Typically Clients are configured to access Impact via the Client Portal. Selecting “Yes” from the pull-down menu will allow access to this user via the Client Portal. Selecting “No”, which is the default setting, will deny access to the Client Portal to this user. Client Portal users have limited access to the system.
The table immediately under the Client Portal user field is used to define what accounts the user has access to on their client portal. Access can be defined based on a single client code (or up to 5 single client codes), a range of client codes (or up to 5 different ranges of client codes), or using the Clt_Consolidate_To field found on the REPORTING tab of the client set up table (up to 5 different combinations of consolidate to codes - up to 20 codes per line).
|Allow View History -||There are 2 options for this field Yes and No. When this field is set to Yes, the user has the ability to view the history on the account being reviewed in the client portal|
|Receives Messages -||There are 2 options for this field Yes and No. When this field is set to Yes, the user has the ability to receive messages via the messaging feature.|
|Comp -||Fill in with the company code that will apply to this single client, client range, or consolidate client to field selections.|
|Client -||For single client code access, fill in with the client code this user has access to. For access to a range, fill in with the beginning client code of the range. Leave blank if using access based on CLT_CONSOLIDATE_TO field.|
|Thru -||For single client code access, fill in with the client code this user has access to. For access to a range, fill in with the ending client code of the range. Leave blank if using access based on CLT_CONSOLIDATE_TO field.|
|Or -||Just a reminder, you can do either a single client code or range, OR base access on CLT_CONSOLIDATE_TO fields. You may not do both on the same line.|
|Consul1 (thru) Consol 20 -||Here you can list up to twenty CONSOLIDATE_TO client codes either by listing up to twenty such specific codes on each line OR by using the Oracle wild card character to indicate the LIKE function. NOTE: Please do not combine specific client codes with LIKE function client codes. This will not work.|
|Clt Svc Correl -||This option allows you to define what Client Service Correlation rep is assigned to the client codes that this Client Portal user has access to. The options from this pull-down menu are entries from the Client Service Correlation table. Select from the pull-down menu what CSR in the system will be notified (via IMPACT message) if this user of the Client Portal drops a new business file for processing.|
|Portal Path (Use/) -||This path is to define what directory in the main server will be used to archive new business files that the user of this Client Portal may drop.
The following section (set of fields) directly relates to the ACCOUNT MASS UPDATE on the menu in the Client Portal. The purpose of this function is for the client to be able to pull a list of accounts based on the designated statuses, and then choose which ones the indicated result code (AT-ResCd field) should be applied to.
|Mass Update Name -||Allows the designation of a descriptive name for the update - IE. APPROVE_ACCOUNTS_FOR_CLOSE. (No spaces are allowed in the name!).|
|Status IE -||Choose if the client account update list for review will be pulled based on INCLUDE the following status(es) or EXCLUDE the following status(es)
STS 1: These seven fields allow for INCLUDING or EXCLUDING up to seven different statuses.
STS 2: These seven fields allow for INCLUDING or EXCLUDING up to seven different statuses.
STS 3: These seven fields allow for INCLUDING or EXCLUDING up to seven different statuses.
STS 4: These seven fields allow for INCLUDING or EXCLUDING up to seven different statuses.
STS 5: These seven fields allow for INCLUDING or EXCLUDING up to seven different statuses.
STS 6: These seven fields allow for INCLUDING or EXCLUDING up to seven different statuses.
STS 7: These seven fields allow for INCLUDING or EXCLUDING up to seven different statuses.
AT-ResCd - enter here the result code (shown on the drop down with it's activity type) to be entered on the accounts the client approves for the mass update.
The following section relates directly to the REPORTS function on the Client Portal Menu. This function works in conjunction with the ADHOC report writer and allows for the creation of reports that a client can run on demand that are limited to pulling only the accounts this user id has access to on their client portal.
|Report Name -||The name of the report to appear on the drop down list of the client to choose from
URL PATH: this field requires custom set up for each IMPACT client. Please refer to the document in the Support site document library and contact Support for assistance in using this feature.
Dialer Parameters Tab
Objective: The purpose of this tab is to configure how the user will be able to interact with the dialer
Dialer Parameters Tab Window
|Nailup PSTN-||To use if the method of connecting to the dialer is via a Public Switched Telephone Network instead of the default value of VoIP (Voice Over Internet Protocol). To use PSTN, enter the DID (telephone number) that you wish to use to establish a bridge with the CSS Dialer.|
|Nailup Pbx -||To use if the method of connecting to the dialer is via your existing PBX instead of the default value of VoIP. Please consult with CSS Support for the parameters needed here to connect via your PBX.|
|Ani -||Enter the Automatic Number Identification ("ANI") that you wish to display as the caller ID on the recipients' telephone device for outbound calls placed by this user.|
|SkillSet Pty -||Use the drop-down to select one of the three possible skill set priorities (1, 2 or 3). The selected value can be used by an inbound dialer strategy on demand ("DLRSOD") to route calls to a specific agent based on criteria defined in that SOD.|
|Aci Role -||Use the drop-down to select either "User" or "Manager". A "User" role restricts access to only the "ACI" tab in the Dialer Console whereas the "Manager" role allows access to the entire Dialer Console. A User is also known as "the clicker" that manually selects which telephone numbers that the dialer SOD prequalifies and displays in a grid format will be called.|
Objective: This function controls which statistics this user has access to under the VIEW STATISTICS function found on the COLLECTIONS menu. Choose YES to allow access, NO to restrict access.
Stats Tab Window
|Company -||This option defines whether this user has access to view statistics at the COMPANY level.|
|Client -||This option defines whether this user has access to view statistics at the CLIENT level.|
|Department -||This option defines whether this user has access to view statistics at the DEPARTMENT level.|
|Desk -||This option defines whether this user has access to view statistics at the DESK level.|
|Salesperson -||This option defines whether this user has access to view statistics at the SALESPERSON level.|
Audit Trail tab
Objective: Records all the changes were done to the Security Code Table
Audit Trail Tab Window