What are the key terms and differences between Transact and LenelS2 NetBox for electronic door access?

Summary

This article provides a standardized glossary to help you translate terms between systems and understand the relationship between Access Plans, Access Levels, and Time Specifications.

Body

Overview

In a dual-system environment, users and administrators may encounter different terminology depending on whether they are working within the Transact (TSDA) interface or the LenelS2 (NetBox) interface. While both systems perform the same core functions—managing who can enter a door and when—the nomenclature (naming conventions) differs.

This article provides a standardized glossary to help you translate terms between systems and understand the relationship between Access Plans, Access Levels, and Time Specifications.


Terminology Comparison

To ensure accuracy during troubleshooting or configuration, use the following mapping to translate terms between the two platforms.

Access & Permissions

Term (Transact)

Term (S2)

Definition

Access Plan

Access Level

The primary tool used to grant a user permission to enter specific doors during specific times.

Permission Schedule

Time Spec

The underlying schedule that defines the allowed hours and days for an access permission.

 

Physical Entry Points

Term (Transact)

Term (S2)

Definition

Door

Portal

The physical entry point where credentials are presented.

Portal Group

Reader Group

A collection of doors or readers used to apply permissions to multiple locations at once.

 

Door States

Term (Transact)

Term (S2)

Definition

Controlled State

Locked

A secured state requiring a valid credential for entry.

Unlocked State

Unlocked

An unsecure state where the door is open to all users.

Access Denial Reason Codes

When a user is denied entry, the system logs a specific reason code. Use this section to understand why access was rejected.

Timing & Schedule Denials

  • [TIME]: The user attempted access outside of their assigned Time Spec or Permission Schedule.
  • [WRONG DAY]: The user attempted access on a day of the week not included in their schedule, or a Holiday is currently active.

Credential & Identity Denials

  • [UNKNOWN]: The credential data is valid, but no record of this credential exists in the system.
  • [EXPIRED]: The credential has passed its assigned end date.
  • [DISABLED]: The credential has been manually marked as inactive (may also be labeled as [LOST], [STOLEN], or [SUSPENDED]).
  • [BIT MISMATCH]: The data format of the credential does not match the reader's configured format.

Permission & Location Denials

  • [LOCATION]: The user's Access Level or the current system Threat Level does not permit use of this specific reader.
  • [NO ESCORT]: The user holds a "Requires Escort"-level access but did not have an authorized escort present.
  • [PASSBACK VIOLATION]: The credential was presented in a region where the user is already known to be.
  • [TAILGATE VIOLATION]: The credential was presented in a region where the user is known not to be.

Summary of Key Concepts

Understanding the Relationship

It is important to remember that an Access Plan (Transact) and an Access Level (S2) are functionally identical. They both act as a "container" that holds together a Location (the Door/Portal) and a Time (the Schedule/Time Spec).

Terminology Tip for Troubleshooting

When reviewing logs or error messages:

  • If you see references to "Plans," you are likely looking at data originating from the Transact side.
  • If you see references to "Levels" or "Time Specs," you are looking at data originating from the S2 side.

Details

Details

Article ID: 2370
Created
Fri 7/31/26 3:34 PM
Modified
Tue 8/4/26 8:00 AM