Skip to content

Access control readers and reader groups

Readers represent credential-reading devices. Reader groups collect readers for access-group mappings used by legacy integrations. These two actions are shown on the Physical Access Control card only when the selected site has an active controller other than Azure or AllBox.

Azure readers and access points are normally configured through Controller Hardware Setup.

Readers

Select Reader to filter by interface, search the inventory, add a reader, or synchronize selected readers.

Add or edit a reader

Configure:

  • a required active interface;
  • a required name and System Type;
  • serial number and Bluetooth identifier when used by the integration;
  • reader position or input port;
  • grant-access time and optional hold-open schedule;
  • external ID;
  • remote-open, facility-entry, and facility-exit options.

New readers default to a grant-access time of 6 and position Left (0). Grant-access time must be numeric when supplied.

Type-specific behavior matters:

  • Azure and Keri offer the additional Left (2) and Right (3) positions.
  • Keri hides Grant Access Time and Schedule.
  • Azure and VertX require an unused external ID selected from 1 through 500.
  • Keri requires a manually entered external ID.
  • External IDs must be unique across active readers at the site.

Existing reader number and relationship data can affect controller mappings. Review Change History and dependent groups before editing identity fields.

Synchronize readers

Select one or more rows, choose Sync with Controllers, select an active VertX controller, and select Sync Now. Only the selected readers are sent. Save reader edits before syncing and verify the configuration queue and physical result afterward.

Deleting a reader performs a hard cleanup. The confirmation describes known dependent records; do not continue until you understand which group and access associations will be removed.

Reader groups

Select Reader Group to search, create a group, or synchronize selected groups to an active VertX controller.

Each group requires:

  • a name;
  • an unused external ID from 1 through 500;
  • the active readers that belong to it.

On save, TEKControl updates the group, deletes its previous reader-association rows, and recreates the currently selected associations. This makes the visible selection authoritative. Confirm that no reader was accidentally omitted before saving.

Select the desired groups before Sync with Controllers. Synchronization sends only the selected group records to the chosen VertX controller.

When an expected item is missing

  • Deleted or inactive controllers, interfaces, and readers are excluded from selectors.
  • The Reader and Reader Group buttons are hidden when every active system is Azure or AllBox.
  • Reader synchronization appears only when an active VertX controller exists.
  • An external-ID selector can be empty when all values 1 through 500 are assigned.