Credential User Flag Descriptions
Overview
This article provides descriptions of the User Flag options on a person Credential.
Generally speaking, these flags should only be modified if explicitly told to do so. The "Active Cardholder Record" flag is added automatically and should always be used. Most of the other flags require additional configuration within BluSKY, the Mercury Controllers, and/or destination dispatch elevator vendor server in order to be functional. Without the additional configuration, the Mercury flags should be ignored, however we have seen incorrect behavior or errors when incorrect use of the Destination Dispatch Elevator flags are used and the elevator server has not been previously configured to accept these flags. If you have any questions about the use of these flags, please reach out to BluB0X Support before making changes.
Mercury Controller Flags:
Active Cardholder Record
- This flag must be present for this credential to be recognized as Active. It is the default setting automatically applied by BluSKY any time you add a new credential to a profile. For best practices, we recommend always leaving this flag in place. If you wish to deactivate a card, the preferred method would be to set a Start/End Date on that credential, or to set an End Date on the user profile (Basic Info tab) if you want to disable the entire profile and all credentials that are assigned. The End Date method is preferred as it is a more obvious restriction on the card and/or profile than a deleted User Flag would be.
Allow One Free Antipassback Pass
- If Area-Based APB is enabled in a controller configuration, this allows an initial free pass for the first use of a new card as it establishes the initial area location for the person. The flag is ignored if Area-Based APB is not configured on a Mercury controller.
Card Anti-Passback Exempt
- If APB is implemented on a controller configuration, this card will be exempt from APB rules. The flag is ignored if an APB mode is not configured on a Mercury controller.
Use ADA Timing Parameters
- If portals have been configured with different unlock/open times for ADA, the portal can recognize this card as someone who needs that longer unlock time.
PIN Exempt Card
- Exempts this cardholder from being required to enter a PIN on a reader that is in a Card AND PIN configuration.
Do Not Change Antipassback Location
- If Area-Based APB is configured in a controller, this flag will prevent the area location information from being clear/reset when a card update is sent down to the controller. The flag is ignored if Area-Based APB is not configured on a Mercury controller.
Do Not Change Antipassback Counter
- If Card Use/APB Use is configured use of this flag will prevent either the original Use Count (base) or the current Use Counter from being updated. The flag is ignored if Use Count functionality is not configured on the Mercury Controller.
Do Not Change User Card Usage Count
- If Card Use/APB Use is configured use of this flag will prevent only the current Use Counter from being updated. The flag is ignored if Use Count functionality is not configured on the Mercury Controller.
BluSKY Function Flags:
Duress
- A special Duress feature may be implemented whereby use of a credential with this flag will trigger a discrete/silent Duress notification process. This requires additional configuration within BluSKY, otherwise the use of this flag is ignored.
Destination Dispatch Elevator Flags:
Each the flags below are intended for use to indicate to a destination dispatch elevator server that a special operation is requested. The special operation functionality must be programmed into the elevator control logic by the elevator vendor. Not all elevator vendors will recognize all flags or perform the same operations. While the flags have no meaning unless support is configured into the elevator logic by the elevator vendor, we do recommend NOT using them unless you have been explicitly instructed to do so by BluB0X or the elevator vendor. If the flags are included in the credential User Flags, the flag will be passed to the elevator server when the credential is used. If the elevator control logic has not be configured to use these flags, sending them could lead to undesired effect or an error conditions in the elevator logic.
VIP
- Typical special operation might be to assign a specific elevator car or assign express operation for users assigned the VIP flag.
Vertigo
- Typical special operation might be to slow down the speed and/or acceleration of an elevator car to minimize the potential for triggering distress for someone.
EAP/Fire Warden
- Typical special operation might be to assign express operation to the person.
Special Operations
- General use special operation flag for the cardholder.
Special Operations 2
- General use special operation flag for the cardholder.