VECTA Access Control Solutions
Main Applications
Console
Alarm Mode
Cardholder Configuration
Reporter
Badging
Time & Attendance
Subsystems
Security Manager
Permissions
Audit
Event Acknowledgment
Automation

Cardholder Configuration

Cardholder Configuration application is for managing database of cardholders, cards and issues. Module is designed for use as a “Pass Office” workstation.

Tabular display is designed for better browsing, editing and data retrieval. Module contains 4 tabs, used for the following object types:

  • Cardholders
  • Cards
  • Global Access Levels (GAL)
  • Issued Cards

Cardholder Data

For entering cardholder data into database, following fields are used: Last name, First name, Middle name, Photo, Phone number, Gender, E-mail address and also reference fields: Department, Job Position. 10 additional text fields and additional reference fields – Group and Subgroup, can be used besides standard fields.

Card Issue

Cardholder Configuration allows one cardholder to own more than 1 card. Besides this, in future, card may be reissued to other cardholder. Therefore a collection of visitor or single cards can be organized. When card is shown to a cardreader, an access message appears which always captures the present cardholder. Reporter application always permits to know the cardholder at the moment of message appearance even if this card was reissued for other people.

VECTA Cardholder Configuration

To decrease errors in card number entry, specialized cardreaders, supported by Cardholder Configuration application, can be used. That’s enough to show card to a cardreader in this case and its numbers will be automatically shown in a field.

Global Access Levels

Global Access Levels (GAL) subsystem is used for setting cardholder access rights. This allows quick and easy way of card rights unification for all system controllers under one identifier (ID) - Global Access Level. For the next card issue, cardholder must select GAL out of the list and system will make all the necessary changes in all controllers.

Reports

Cardholder data can be selected from database by means of filter applied for any cardholder fields.

Tabular data can be sorted by fields selected. Report process is organized in a separate flow, that’s why user’s interface doesn’t hang on during process. Report process can be always paused/continued or even stopped. Any tabular data can be printed or exported to file for future processing in other programs. Special settings allow tabular data not to be read on application startup – this is comfortable because data output at all layouts may take long time to process because of a big amount of cardholders.