Skip to content

Credential and read details

Select a linked Credential Number in the transaction grid to investigate the credential behind a read. The panel is read-only and reflects the current credential configuration together with the selected transaction's most recent read information.

Review a matched credential

When TEKControl finds the credential record, the panel can show:

  • credential number and card format;
  • credential type and active, inactive, or deleted status;
  • current host, vendor, or alternate-name association;
  • valid-from and valid-to dates;
  • maximum-use count, when configured;
  • the selected transaction's read time and location;
  • assigned access groups, schedules, readers, access points, and door-contact, request-to-exit, or relay targets.

Use Change History to review recorded changes to the credential. History helps distinguish the configuration that exists now from what may have been configured when an older transaction occurred.

Review an unmatched read

A transaction remains useful even if its credential was deleted, replaced, or cannot be resolved. In that case, the panel shows the values preserved with the read, including the credential number, event, date, location, association snapshot, raw hexadecimal value, facility code, and card imprint when those values were received.

An association snapshot is the text saved on the transaction. It may differ from a person's or credential's current name or assignment.

Investigate unexpected access

For an unexpected grant or denial:

  1. Confirm the transaction date, location, reader, and exact event type.
  2. Open the credential details and check current status and validity dates.
  3. Review access groups and the schedules and targets within each group.
  4. Open Change History when the current settings do not explain an older transaction.
  5. If there is no matching record, capture the preserved facility code, imprint, and raw read values for an administrator or support team.

Important

A current credential configuration does not prove that the same configuration was active at the transaction time. Use the transaction snapshot and credential history together when investigating older activity.