Akcelerant Framework Administrator Guide - Collection
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

  • This username is a unique name for the user and links the user to functions in the system.
  • Typically in list grids and other sections of the system, the username does not display. The username is a field that can be displayed for the user and other reports as needed.

Name

  • Displays Last, First name of the user.

Active

  • Indicates whether a user is active or inactive.
  • If a user is active this box contains a green checkmark. If a user is inactive the box is blank.
  • If a user is marked as inactive access to the system is prohibited.

Logged In

  • An automatic indicator to show the status of users in the Productivity Framework.
  • If the user is logged in this box contains a green checkmark. If the user is not logged in this box in blank.

Last Login

  • Displays the last date and time a user logged in.
Filter
  • There is a filter box on the top right corner. As you begin typing in a name (first or last), the list of users will filter to only show the users that meet the criteria.

Users are able to Create, Copy, Edit or Delete users from the Users Listing page.

Create a User

Company Information Tab

Within the Company Information tab the following sections display: Company Information, Organization Structure and Account Restriction Processing.

Columns/Headings

Description

Company Information
  • Define company information for the user.
  • All fields on this page are optional.
  • Use information from this page in formatted letters.
Organization Structure
  • Define the organization structure, if applicable.
Account Restriction Processing
  • If account restriction is enabled, insert restriction code into Restriction Code 1.

Personal Information Tab

Collection Settings Tab

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 Number of Calls for User Performance Dashboard and Collector Production 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. 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.

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

For example, if the max % promise is 10% and the total promise amount is $1,000, the promise payment can be satisfied is 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 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

Permissions Tab

Security Groups Tab

Permissions Tab

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.

  • If the User belongs to a Security Group, the Framework will merge the permissions for the Security Group and the permissions for the Individual User and use the highest permission for each option.
  • There is no need to set individual permissions per user. All Dashboards, Views, Reports and other setting tabs pertaining to permissions can be skipped. 

Screens Tab

Workflows Tab

 

Dashboards Tab

Views Tab

Reports Tab

Areas Tab

Categories Tab

Restrictions Tab

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

Restricted Persons

Send Feedback