webMan EN

# Users - Patrol user management

# User settings

It is used for user registration. Their sampling, setting of their privileges of transitions (also in time intervals), access to readers. The options in the main part of the window change according to the use of the filter on the left side.

User management

# Filters

User management - filter

For a faster search, the filters also display various access and editing options:

Note

The Clear sorting display is a bug, it appears for example if you have open the Unregistered in Patrol filtering and the content of the main part of the window is empty, clicking the button does not change anything (nor should it change)

# Options / Actions

# New record

When creating a new user record in webPatrol, there are several options:

  • Creating a system user
  • creating a system user and a system employee

using one of the modules:

  • System
  • webPatrol

After creating at least a system user, it is necessary to register the user in the webPatrol module by creating a PIN that connects the system user to the webPatrol user. The PIN is normally generated using the button Register users, which is located in the main part of the window when filtering unregistered users. If the user does not have an employment type or has more than one employment type, it is necessary to manually create a unique PIN. Furthermore, it is still necessary to assign a group to the user, with the help of which readers will be automatically assigned.

So it is advisable that you read System - users, System - employee, Creating an employee (webPatrol) before creating a new record.

Note

In the case of creating a new employee using webPatrol, he is initially selected with the letter X, which is automatically replaced by his personal number, after it is filled in and saved.

Warning

In this case, you need to have edit privileges:

System icon User management System icon Employee management

You can find on -> Access rights

# Output

It serves to pre-set the printing of the current content of the main window.

Output

# Actions over all/selected

Actions on users are intended for faster editing of user templates. The difference between Actions over all and Actions over selected is only that in the first case you edit all users at once and in the second case only users that you mark by clicking the box on the left side of their name.

Actions over all/selected

# Copy templates

Copying templates is used if you have several types of readers and use them, for example the same card. After creating templates for one type of reader, you can copy them to another type of reader.

You choose here:

  1. what type of template do you want to copy

    1. do you want to copy the first
    2. or all templates

  2. what type of template do you want to convert the copy to

    1. do you want to overwrite the entire existing template

    2. or add the copied to the original templates

    3. or add the copy as a new template

      2.2.-2.3. 1. In the second and third cases, it is also necessary to select PIN generation

  3. Then you still have to choose which templates you want to copy

    1. card templates
    2. fingerprints
    3. face
    4. hand

Note

Not all template types can be copied to and from all reader types

Copy templates

# Change group

With this, you can change to which user group the selected users will belong and thus which readers will be automatically assigned to them.

Change group

# Add finger to the reader Wizard

In case you want to do the given activity with more than one user, you have the name and PIN of the user you are editing at the top of the window. Marking a finger, then creating a finger template and clicking Yes as an answer to the question will record the changes and send them to the readers.

Warning

Add finger to the reader Wizard only works if the user you want to edit/change fingerprints for has already created, even only an empty template.

# Register users

In the table of unregistered users, users can be registered in several ways:

  1. By double-clicking on the user, filling in his PIN and sending the modified information to the server using the buttonArrow next
  2. By marking the users you want to register and the button Register users icon*1
    1. By agreeing to generate a PIN according to the employee's personal number

User management - user records - PIN generation

Note

*1 PIN generation is possible only if it is allowed in webPatrol settings, in that case, with normal settings, the PIN is generated according to the employee's personal number.

If the user does not have an employment relationship, it will not even be displayed among unregistered users, it will only be displayed in the All table.

# Editing a user template for a reader type

  • Records of a system employee/user as a registered user in webPatrol from those not registered in webPatrol:
    • Without generating a PIN: It is necessary to enter the user's PIN manually, it is advisable to create the same PIN as the employee's number
    • With PIN generation: Register in the patrol

When editing a user record in webPatrol, or after registering a user in webPatrol, the Extended category opens.

User management - a new user or its modification

# Extended

  • PIN - PIN is the registration number of the webPatrol user
  • Group - It is selected from the user group to which the readers are assigned

# Templates

It is used for the registration of different types of templates, for individual reader types

# New record / edit template for reader type

User management - template type by reader type

# Basic

It is possible to create multiple templates of the same type of reader, as well as the same type of template (card, face, etc.). But in case templates of the same type of reader are assigned to one PIN, they should not contain templates of the same kind, because in that case they will be overwritten by the last template when synchronizing with the reader. If, for example, you want to have several cards for one user, under one employment type, it is necessary to create a new template of the same type of reader, with a different PIN (preferably with a common prefix, for all persons using several of the same types of templates), or register the same employee as a new user , with a different classification and a new PIN.

When creating a new record, it is necessary to correctly set the template for the reader type and only then the user template:

  • Template type -Selection from all types of readers Depending on the type of template, various options are also displayed. For example, ZK type readers can use card, face, hand templates. But it depends on the reader and template settings.
  • Description - optional data (some browsers may try to suggest and auto-fill this)
  • Time-area zone - choice between always and everywhere/never and nowhere; required for spatial readers, must be created in the webPatrol group settings
  • Enable another PIN number - it is used in the case of multiple cards/chips for one user
  • PIN number - another PIN must be different from the user's main PIN, it is best to choose a suitable prefix for everyone, for better identification
  • Password - only for S880
  • Enable password - only for S880
  • Enable hand - allowing the user to use the hand template
  • Enable fingerprints - allowing the user to use the fingerprint template
  • Enable face - allowing the user to use the face template
  • Enable cards - allowing the user to use the template card
  • Validity from - privileges for the user apply from the given period
  • Validity to - privileges for the user are valid until the given period
  • Employment type - it is used if the user has several types of employment and if you want to assign several of the same types of templates for one job
  • Company - it is used if the user has several types of employment and if you want to assign several of the same types of templates for one job

Note

After enabling different kinds of templates and sending the settings to the server using Icon next, various subcategories will be generated in which you can continue setting.

# Extended

After sending the first setup Arrow next, or changes Save icon, the Extended category is generated on the server, which contains more detailed settings divided by reader type. In this category you can:

  • Authority` - selection of privileges in the reader, usually user, administrator and super administrator; it differs according to the type of reader, it is related to the access to the menu and settings of the reader
  • Enabled - enable / disable the use of user templates
  • Verification type - setting in which sequence it is necessary to verify in which way
    • By access group - set in readers
    • FP/PW/RF
    • FP
    • PIN
    • PW
    • RF
    • FP/PW
    • FP/RF
    • PW/RF
    • PIN & FP
    • FP & PW
    • FP & RF
    • PW & RF
    • FP & PW & RF
    • PIN & FP & PW
    • FP & RF / PIN
    • FACE
    • FACE & FP
    • FACE & PW
    • FACE & RF
    • FACE & FP & RF
    • FACE & FP & PW
    • VEIN - reserved
    • FP & VEIN - reserved
    • VEIN & RF - reserved
    • VEIN & PW & RF - reserved
    • PALM
    • PLAM & RF
    • PALM & FACE
    • PALM & FP
    • PALM & FP & FACE
    • OTHER - reserved
  • Creating photos after verification - setting after which verification the photo should also be created; Only for reader type APIS Reader
    • According to the system - according to the reader setting
    • Enabled - always
    • CARD
    • FP
    • PIN
    • CARD or PIN
    • CARD or FP
    • FP or PIN
    • CARD or FP or PIN
    • Disabled - never

After sending the first extended setup again Arrow next, or extended settings changes Save icon to the server, categories of allowed template types will be generated.

Description

FP - fingerprint

PW - password

RF or CARD - card

PIN - personal identification number

FACE - face

VEIN - vein

PALM - palm

OTHER - other

& - and

/ or or - or

Note

In the case of the ZK - iClock S880 type reader, it is also possible to log in using:

  • Password
  • PIN In both cases, a new template type is not generated, it is set in the basic template settings of the reader type.

# Creating, editing and deleting templates according to the type of template

Only one template of the same type can be created in one template of a reader type at a time. For example, before changing the card, it is necessary to delete the template card first. For finger templates, they can be replaced directly.

  • Hand: To insert a hand template on the server, it is necessary to use the import of templates from the ZK - ProFace and SpeedFace reader

ProFace and SpeedFace readers

  • Face: To insert a face template, it is necessary to use the import of templates from the ZK type reader - ProFace and SpeedFace

SProFace and SpeedFace readers

  • Fingerprint: To insert a fingerprint template, it is necessary to use the import of templates from an ApisReader type reader, or to use the ZK9500 reader, which requires installation by a software technician.

Fingerprint reader ZK9500 and Apis reader

  • Card: To insert a card template, it is possible to import templates from a ZK type reader - ProFace, SpeedFace, ApisReader type readers - Zpad, Biopad, or use a CR20 reader

Card reader

Note

Since it is possible to copy templates from one type of reader to another, this step is always added to the procedures, but it is not required and not all options are possible at this moment (e.g. we do not use other readers for face, palm verification, such as ProFace/SpeedFace)

# Hand/Palm and Face

To create a hand and face template, administrator privilege is required on readers of the ZK type, ProFace/SpeedFace type. In this case, the administrator can access the reader menu and edit user templates. There are several ways to proceed:

  1. From the server
    1. creation of an empty user template of type ZK
    2. synchronization with ZK type reader, ProFace/SpeedFace type
    3. creating a palm and/or face pattern
    4. loading users from the reader
    5. importing user templates by overwriting the original ones on the server
    6. synchronization of user templates to other readers
  2. From the reader
    1. creating a user on the reader
    2. creation of user templates on the reader
    3. loading users from the reader
    4. importing user templates by creating a new one/overwriting the original employee on the server
    5. copying a template from one type of reader to another
    6. synchronization of user templates to other readers

# Fingerprint

To create a fingerprint template, it is possible to use a fingerprint reader or a reader with a fingerprint reader (ApisReader, or ProFace/SpeedFace, with a fingerprint reader). There are also more options than creating templates.

  1. From the server through the fingerprint reader
    1. creating a user template of the ApisReader/ZK type
    2. creating a blank fingerprint template
    3. creating a fingerprint template using a fingerprint reader
    4. copying a fingerprint template to another type of reader
    5. synchronization of user templates to other readers
  2. From the server through the reader
    1. creation of an empty user template of type ApisReader/ZK
    2. synchronization with an ApisReader type reader, or ZK with a ProFace/SpeedFace type
    3. creating a fingerprint template
    4. loading users from the reader
    5. importing user templates by overwriting the original ones on the server
    6. copying a template from one type of reader to another
    7. synchronization of user templates to other readers
  3. From the reader
    1. creating a user on the reader
    2. creation of user templates on the reader
    3. loading users from the reader
    4. importing user templates by creating a new one/overwriting the original employee on the server
    5. copying a template from one type of reader to another
    6. synchronization of user templates to other readers

# Card

Under normal circumstances, the customer buys a larger number of cards, and this involves loading the cards onto the server by a software technician. In that case, it is enough:

  1. assign a card to an employee
  2. copy templates to another type of readers
  3. synchronize with readers Otherwise, the card needs to be loaded and saved on the server. Loading cards can also be done in different ways:
  4. From the server through the card reader
    1. creation of a user template of the Apis Reader/SK type
    2. creating a blank template card
    3. creating a template card using a simple reader
      1. loading the card number into the selected part of the window (you must have an English keyboard or a keyboard that has priority numbers in the line above letters)
      2. manual addition of the card's external number
    4. copying the card template to another type of reader
    5. synchronization of user templates to other readers
  5. From the server through the reader
    1. creation of an empty user template of type ApisReader/ZK
    2. synchronization with an ApisReader type reader, or ZK with a ProFace/SpeedFace type
    3. creating a template card
    4. loading users from the reader
    5. importing user templates by overwriting the original ones on the server
    6. copying a template from one type of reader to another
    7. synchronizácia užívateľských vzoriek na ostatné snímače
  6. From the reader
    1. creating a user on the reader
    2. creation of user templates on the reader
    3. loading users from the reader
    4. importing user templates by creating a new one/overwriting the original employee on the server
    5. copying a template from one type of reader to another
    6. synchronization of user templates to other readers
  7. From the server using the ApisReader manually
    1. creating a user template of the ApisReader type
    2. creating a blank template card
    3. reading the card's internal number from the reader by placing the card on the reader and writing down the displayed, read, unrecognized card number in the decimal system
    4. filling the empty card template with the read value to Internal card's number according reader's type
    5. filling in the external card number
    6. copying a template from one type of reader to another
    7. synchronization of user templates to other readers

# Delete selected

Deletes selected user templates of the selected reader type

# Readers

It serves to synchronize the user's templates from the server to the readers. readers are automatically displayed here according to the group to which you assigned the user template. If the group does not contain a reader, the reader must be assigned, otherwise it will not be possible to send templates to any of your readers and the user will therefore not be able to authenticate.

# Assign the readers

After clicking on the option Assign readers, a window will open in which you can mark all the readers on which you want the user to be able to authenticate, in case the user has created templates of the given type of reader. Then click on Assign selected.

# Delete selected

Removes the selected readers from the readers assigned to the user.

# Synchronize changed/selected

Replaces/creates templates from server on readers.

# Delete from selected

Deletes user templates from selected readers.

← _Actual presence_ →