Skip to content
English
  • There are no suggestions because the search field is empty.

Program and Field Level Security Questions

There are a few different ways that Credit Unions can secure their systems by limiting access to certain programs, limiting tellers individually, or locking down specific functions within programs. The three kinds of security are: Teller Configuration Program Security Configuration Field Level Security Thankfully FLEX gives clues whenever one of these programs is preventing a teller from taking a specific action.

There are a few different ways that Credit Unions can secure their systems by limiting access to certain programs, limiting tellers individually, or locking down specific functions within programs.  The three kinds of security are:

  1. Teller Configuration
  2. Program Security Configuration
  3. Field Level Security

Thankfully FLEX gives clues whenever one of these programs is preventing a teller from taking a specific action.

Teller Configuration Example:

Check in Teller Configuration to make sure teller ID is authorized to perform transactions on Charged Off Accounts and/or Charged Off SSN.  CMC cannot make changes to Teller Configuration, aside from rare cases when no one is available at the Credit Union to change a password or reset invalid attempts to zero.

Program Security Configuration Example:

If a teller is not authorized to access a program in Program Security Configuration this error will appear and tell them the specific program name.  They’ll need to request access to it from someone at the Credit Union, as we are not allowed to determine who can access certain programs (except in the ultra rare case of a Credit Union preventing anyone from accessing Program Security Configuration.)

Field Level Security Example:

The yellow lock symbols note when Field Level Security is preventing a teller from accessing a specific field.  The teller will need to request access to the field from someone at the Credit Union.  CMC cannot make changes to Field Level Security for any reason.

Teller Configuration

Teller Configuration is where a Credit Union can give permission to perform various actions, set limits on transaction or loan amounts, exclude tellers from using Transaction Codes or Op Codes, or prevent tellers from maintaining types.



The Privileges tab is where the Credit Union can authorize tellers to grant or require overrides.  Most of the settings on this tab have at least three options, Yes, No, Dual.  

Yes – Can perform an action or grant an override to another teller.

Dual – Requires an override from a teller with Dual or Yes.

No – Can not perform the action without an override.

Common issues on this tab are the Accounts Payable settings, frozen and dormant account maintenance, and why a teller can’t see a member’s name in Tran Entry.

The Security tab is where the Credit Union can limit a teller from inquiring into accounts (with specific accounts in Accounts Excluded From Inquiry field, or from inquiring into any accounts that is flagged as being an employee.  Tellers can also be excluded from maintaining or doing transactions on specific accounts.  This is also where the Document Security Level and Security Level fields are located.


The Limits tab is where the Credit Union can set specific transaction type limits on the teller.  Leaving the field blank, or entering 0 or 99999 means there is no limit for that type.  Any value between 2 and 99998 would be the dollar amount limit.  Entering an amount of 1 prevents access to this transaction type.

The Miscellaneous tab is where the Credit Union can exclude tellers from using certain Tran Codes, maintaining specific Account Groups, or accessing Suffix Types.  This is also where the password can be changed and invalid login attempts can be reset back down to zero.  Entering an email address on this tab will allow the teller to receive certain notifications from other programs, such as Accounts Payable.  And there are Receipt Printer options, such as prompting the teller to print a receipt.  The Single Login setting here can be changed per teller, overriding the default setting found in Miscellaneous Information~.


The Operation Codes tab is where the Credit Union can limit tellers from using certain Op Codes.  Leaving the Selection Operation Codes pane blank will give the teller access to all codes, moving any codes into this pane will prevent the teller from using any code not in the pane.


The Loans tab is where the Credit Union can mark a teller as a Loan Officer, Insurance Sales Officer, or Collection Officer, or limit the amount of a loan a teller can process, or exclude specific loan types.


The FLEX Ten tab is where the Credit Union can require a member’s keyword to be typed in, as well as the # of characters that must be typed, and can require Critical Notes to be Opened for Validation before proceeding further into a member’s account.


An easy way for a Credit Union to update a teller with the permissions of another teller, such as in the case of a promotion to a new job, is to use the Update button in the top right of the screen.




For creating a new teller ID the Credit Unions can Copy an existing teller on the main Teller Configuration page.  Highlight the teller to be copied from and click the Copy button, which will bring up this new window.

The Copied To field will be the new teller ID, and the Credit Union can copy the Teller Program Security to give the new teller the permission to use programs without having to set each program individually in Program Security Configuration.


When a teller leaves the Credit Union, voluntarily or not, it is recommended that the teller ID be marked inactive and not deleted.  This will make it possible for the Credit Union to reactivate the teller if a drawer is still open.  Credit Unions can also blank out the name, change the password, and leave that already created teller profile for a new teller if they want.


Program Security Configuration



Program Security Configuration is where the Credit Unions can lock down specific programs to prevent unauthorized use.


Credit Unions can use the search functions to look up programs, the box with three dots will allow to search using keywords for program names if the Credit Union is unsure of the program name itself.  They can search by Teller, and by Security group as well.



The Program Name can not be changed, but the Credit Union can change the description.  If the Security Enabled box is checked the program is locked down, and only tellers in the Authorized Groups field are allowed to use the program.  The Use Suspended box is to prevent anyone from accessing the program at all.  Credit Unions can set a program to only work from specific Workstations.


Highlight a group or teller from the All Groups on the left, click the arrow pointing to the right to move the highlighted group or teller to the Authorized Groups pane.



Using Group Maintenance can make changing teller permissions a lot easier and quicker.  Using Groups the teller can assign groups to be authorized for programs, and then can move tellers in and out of groups based on their position within the Credit Union.


Again, CMC does not make any changes to Program Security Configuration, even if no one is available to make the change at the Credit Union.


Field Level Security


Field Level Security allows the Credit Union to lock certain fields or buttons to limit access to them.  As in the example on Page 2, anything locked with Field Level Security will be grayed out and a lock symbol will be present.  Tellers authorized to use the Field Level Security program FLDSEC in Program Security Configuration can add or remove Field Level Security, and can add or remove tellers from the Authorized Groups that have permission to use the field or button that is locked.  This works exactly like Program Security Configuration:

There are some fields/buttons that may also require a teller to have access to the HIDDEN program in Program Security Configuration to be able to access a field that is locked with Field Level Security.


Credit Unions can see a list of the fields with Field Level Security enabled with the Field Level Security program from the FLEX Main Menu.


As mentioned above, there are some global teller settings found within Miscellaneous Information~.



Single Login determines how long a teller has to enter their password while moving between programs.  Each time a new program is accessed a teller will have to enter their password, but within the time frame for this setting a teller won’t be required to enter their password again.  The only exception to this is Transaction Entry, which is not affected by the Single Login setting.

TE Override if Pay Delq Loan, Display Balance in TE Juice Only, Mask Cr Bureau Juice Only and Allow Override of Fully Blocked Acct are all global settings that will apply to each teller


Reports:


Teller Configuration Report

Userdata: CT5351RA

The report can be limited to specific tellers with the From and To options, as well as the option to include Inactive Tellers.  This report will list each teller and their settings from Teller Configuration.  This report is frequently requested by auditors of the Credit Union, using the term ‘access to CORE’.


There is a similar report for Program Security Configuration, Print Security By Teller~.  This report has no options, and will take the teller into Telnet quickly before logging them out almost immediately.  The report still generates into Document Manager.

Userdata: SCTBYTLID




Open Tickets:

829129 – Teller Configuration Cannot Exclude More than 20 Tran Codes

815099 – Inactive Tellers can’t be removed from Group Maintenance.

787994 – FLEX Ten not recognizing Dormancy flag.

799766 – Excluded account mysteriously added to teller ID.

794058 – Create method to reset password outside of Teller Configuration to limit the number of people with access to Teller Config.