FAQs about keys in Space

This page provides answers to common questions about managing keys in Salto Space. It explains what triggers the "Re-edition required" status and outlines scenarios that may require you to re-encode a user's key. See also the keys section for more information about key statuses and the different types of keys available in Space.

What actions might trigger the 'Re-edition required' status?

The Re-edition required status appears when a change affects the file structure of a user's key, which requires the key to be re-encoded using an encoder. This is different from the Update required status, which can be resolved at any SVN updater point, such as a wall reader. See Key status icons and Updating keys for more information.

The following changes are common scenarios that can trigger the Re-edition required status.

Changes to a user's profile

These changes on the User information screen trigger re-edition:

• Enabling or disabling Audit openings in the key
• Enabling or disabling Use antipassback
• Modifying the Wiegand code value (see also changes to general options below)
• Adding permissions that include a free assignment zone, when the user has no existing permissions from the same free assignment group
• Adding more permissions, calendars, or timetables than can fit on the key (memory overflow)

Changes to general options

These changes in System > General options > Users trigger re-edition for all affected users:

• Enabling or disabling Include last reject information on keys
• Enabling or disabling Openings are included in the key's auditor
• Enabling or disabling Discarded openings are also included in the key's auditor
• Enabling or disabling Enable Track #1, Enable Track #2, or Enable Track #3
• Enabling or disabling the Wiegand code option (coupled with changes to the user's profile, as described above)
• Changing the GAT Net locker key UID type between Card serial number (ROM code) and In-memory code