Product Release - Acre Access Control - Classic Client v26.8.1 & Universal Client v26.8.1

New Features & Improvements

User Commands at the Reader

Operators can now trigger pre-defined system actions directly from a Keypad card reader, without returning to a workstation. This gives on-site staff a fast, controlled way to change the security state of an output, area, or a reader.

How it works

A user command is a short numeric code entered at the reader (for example, *101#). Each command is linked to a pre-configured procedure, so a single entry at the reader carries out the action set up for that command. A command runs only at the readers where it has been authorized; an attempt at a reader that isn't authorized for that command is rejected.

An example: A manager coming into the building for the day. He can present his credential and then enter *1975# to activate outputs that the building's lights and at the end of the day enter *1976# to deactivate the output to turn off the building's lights.

What a command can do

A command can be configured to carry out one or more of the following actions:

• Change a reader's mode - to No Access Method, Card Only, PIN Only, Card and PIN, Card or PIN, Facility Code Only, Unlock, or Lock Down
• Activate or deactivate an output
• Pulse an output for a specified duration (or the default), or pulse a reader
• Enable or disable an area
• Enable or disable logging of forced-open alarms
• Enable or disable logging of held-open alarms
• Mask an input to stop logging of its events and/or actions, or unmask an input to resume logging

This is well suited to environments where the security posture of a space needs to change quickly and locally - for example, changing a reader's mode and securing an area during a sensitive activity, then returning it to normal afterward.

Guided setup

In the Classic Client, user commands are configured through a step-by-step wizard that walks you through each stage of setup, reducing complexity and the chance of configuration errors.

Compatibility

User commands are supported on Mercury-based controllers. One user-command per Mercury controller

Assign a Supervisor to a Person (Classic Client)

The Classic Client Person editor now lets you assign a Supervisor to a person, bringing it in line with the Universal Client.

• Assign a supervisor using a searchable person picker, scoped to the relevant folder.
• Change or clear a person's supervisor at any time.
• Available both when creating a new person and when editing an existing one.
• Supervisor assignments stay consistent across clients - a supervisor set in the Universal Client appears in the Classic Client, and the reverse.

For further information about this release, or for clarifications, please contact your account representative.

This maintenance release contains bug fixes and other improvements. Full release notes can be found at https://acre.my.site.com/knowledgearticles/s/article/acre-Access-Control-Release-Notes.