Using Insider/Employee Type Codes: Step by Step
An Insider/Employee Type Code (often referred to as just an “employee type”) is used to flag member accounts which belong to employees, family members, board directors, etc., in order to control employee access to those sensitive accounts.
The purpose of this code is to make it easy to assign similar access controls to a group of accounts, to be honored across the board by all Employee IDs. Exceptions to that rule can be made on an individual employee and account basis.
For example, you might create a code 02 “Board Member” to assign to all of the memberships owned by your credit union board of directors, with access set up so that no employees could perform maintenance or inquiry on those accounts. Then you would make an exception (override the default settings) for a couple of your key employees, such as a head teller and a department manager, so that they could perform inquiries and maintenance as needed, by adjusting the individual account security for those employees, for the board member accounts.
Using Security with Loan Applications
The Allow Account Inquiry and Allow account maintenance check boxes are both required to be checked in order for an employee to be able to create/access a loan application for existing members. These two check boxes do not control whether an employee is able to create/access a non-member loan application.
The Allow Posting to Account check box is required for an employee to be able to book/create a loan account. Please keep in mind that the Loan Underwriting check box within special security settings would also need to be checked in order for an employee to be able to book/create a loan account.
Step by Step Procedure
-
Start by creating the employee type codes using the Insider/Employee Type configuration. This lets you define what the codes mean and what access is allowed, by default, to accounts where the code has been assigned. Click for a list of processes affected by these settings.
-
Next, assign a code to all accounts which belong to employees, family members, etc. This may be done by using the Update Membership Information feature.
-
Finally, access the Employee Security feature select Update Account Security to adjust (override) security settings for individual accounts based on Employee ID. Click for a list of processes affected by these settings.
Processes Affected by Employee Type Security Code Settings
If an Insider/Employee Type Code has been assigned to a membership account, and there are no overrides (exceptions) for the individual employee/account, only the following systems will honor the settings on the Employee Type Code:
|
CBX Feature |
Controlled by this Employee Type Code setting... |
|
Allow inquiry |
|
Allow inquiry |
|
Allow maintenance |
|
Allow maintenance |
|
Allow posting Leave the "Allow Posting" box unchecked to deny this access. (This will NOT prevent posting through Journal Transfer on the first teller posting screen. Use the Update Account Security feature to create an override record if you wish to control access to that transfer feature.) |
|
Both Allow inquiry and Allow posting (i.e., if either is off, this feature is unavailable) (Instead of using the process code, we recommend a teller working in that screen simply use the Time-Out window to perform a quick account inquiry on his or her own account.) |
|
Allow maintenance |
|
Allow maintenance |
|
Allow maintenance |
|
Allow maintenance |
|
Requires Allow inquiry and allow maintenance |
|
Requires Allow inquiry and allow maintenance |
|
Requires Allow inquiry and allow maintenance |
Processes Affected by Account Security (Override) Settings
Whether or not an Employee Type Code has been assigned, if the Update Account Security feature has been used to adjust security settings for an individual employee/account, only the following systems will honor the settings on the override record (in the ACTSEC file):
This applies to the following tools:
|
CBX Feature |
Controlled by this Account Security setting... |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|