System Administration Guide > System Management > Users |
Utilize the system User functionality to create and maintain the Akcelerant Framework users for the organization. The ‘Users Listing’ 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.
Users are created for Administrators and End Users. Individual Users can have permissions that differ from other users. These differences can be easily maintained by adding users to a variety of Security Groups. From these Security Groups, permissions can be set on the group level rather than changing a specific permission for every user.
Column/Heading Name |
Description |
Username |
|
Name |
|
Active |
|
Logged In |
|
Last Login |
|
Filter |
|
Users are able to Create, Copy, Edit or Delete users from the Users Listing page.
Create a User
Certain fields within this section can be included within letter and email templates. The following fields display within the User Information section in the tab:
The below table describes the fields listed under the User Information heading:
Field |
Description |
First Name, Last Name, Username, Email | Fill in the First Name, Last Name, Username and Email. All of these fields are required. |
Description | Fill in a description of the user (position held). |
User Type | Select the user type of Administrator, Casual User, Collector or Manager. The user types do not control the security for the user within the Framework. The User Type is not applicable to the lending solution. |
Time Zone | Specify the time zone where the User works. This value defaults to Easter Standard Time Zone. |
Active | Elect to make the user active in Akcelerant Framework checkbox. If a User is not marked as Active, they will not be able to log in to the system. |
Logged In |
The Logged In checkbox shows if the user is currently logged into the system. If the user becomes ‘stuck’ in the application, simply open a new session of the Akcelerant Framework and log in. A message is returned asking to replace the current session. Click "OK" and the application reopens. |
Phone, Phone Extension, Branch, Department, Title |
If applicable fill in the phone, phone extension, branch, department and title. |
The below table describes the fields listed under the 1st Framework Authentication heading:
Field | Description |
Method | Specify the user’s security type as System. |
Password, Confirm Password |
Insert the password and confirm the password. These Field Values must match and satisfy the length requirements specified. If the password entered is a temporary password, select the checkbox for ‘Force Password Change on next Login’ to direct the user to select a password. |
Force password change on next login |
The ‘Force Password to Change on Next Login’ may be used at any time to force the user to change their password the next time they login to Framework. |
Password never expires | Check that the user's password will never expire. |
The below table describes the fields listed under the 2nd Framework Authentication heading:
Field |
Description |
Method | Specify the user’s security type as Windows. |
Windows Account | The format for this field is Domain\Username. This allows the user to utilize their network login rather than creating a separate system password. |
Within the Company Information tab the following sections display: Company Information, Organization Structure and Account Restriction Processing.
Columns/Headings |
Description |
Company Information |
|
Organization Structure |
|
Account Restriction Processing |
|
The Collections Settings define the parameters to monitor the performance of a user. These settings should be configured for users whose performance is being tracked within the Framework. For users whose performance is not being tracked, these numbers can be left at 0.
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 % Contacts | Identifies the percentage of calls placed by the user expected to result in a successful, valid contact. |
Used to determine:
|
||
Target % Promises | Define the percentage of successful promises the user must meet. |
Used to determine:
|
||
Target % Promises Kept | Define the percentage of successful promises kept the user must meet. |
Used to determine:
|
||
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. to management approval. |
N/A | ||
Max promise payments |
Identifies the maximum number of payments in which a user is able to divide a promise payment.
For example, if the max promise days in System Management>Solution>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.
|
N/A | ||
Min Promise Value As % of DQ Amount |
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 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 |
Security Groups Tab
Within the Security Groups tab, assign the new user to a Security Group. The Security Groups that are available are defined in System Management>Groups>Security Groups.
![]() |
A user can be assigned to multiple security groups. |
Permissions Tab
Within the Permissions tab, manage the new user’s access to several features throughout the Framework. This tab contains two columns: Function and Permission. Click under the Permission column in the corresponding row of the screen and a drop down appears. Change the value in this drop down to change the user's access to the screen. The following are permission options that are available through the permission drop down:
Permissions provide the ability to define individual user access to various areas within the Akcelerant Framework. Select the dropdown for each permission level granted for each option. Users will be presented with None, View and Change. Not all permissions will have all three options.
![]() |
|
This section allows System Administrators to restrict users from accessing specific accounts within the Framework. System Administrators can assign codes to a user that will give 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.
Restricted Account
(0) Normal
(1) Restricted
(2) Sensitive
(3) Employee
(4) Employee Family
(5) Employee Sensitive
(6) Employee Sensitive Family
Restricted Persons
In order to view an account, the user must be allowed based on both the Restriction Code and Restricted Persons.