# Frequently asked questions about keys in Salto Space
> Frequently asked questions about keys in Salto Space to help you troubleshoot potential issues


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](/space/user-guide/operator/keys/introduction#key-status-icons) for more information about key statuses and the different types of keys available in Space.

## What actions might trigger the 'Re-edition required' status? {#what-actions-trigger-re-edition-required}

{{% warning-panel %}}
These actions apply when a key is presented at a wall reader connected to a controller device (such as the CU42E0) and the solid blue indicator light appears, indicating the "Re-edition required" status.
This status is also displayed on the **Users** screen in the **Key status** column by the "Re-edition required" icon.
{{% /warning-panel %}}

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 {{< glossary_term "encoder" >}}encoder{{< /glossary_term >}}.
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](/space/user-guide/operator/keys/introduction#key-status-icons) and [Updating keys](/space/user-guide/operator/keys/update-keys) for more information.

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

### Changes to a user's profile {#user-profile-changes}

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 **{{< glossary_term "wiegand_code" >}}Wiegand code{{< /glossary_term >}}** value (see also changes to general options below)
- Adding permissions that include a [free assignment zone](/space/user-guide/operator/access-points/zones#free-assignment-zones), 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 {#general-options-changes}

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**

{{% info-panel %}}
Changes to auditing options (openings, discarded openings, and low battery) only trigger re-edition when the user's key is a special card type, such as a Smart card lineal, HID SEOS, or DESFire NFC card.
{{% /info-panel %}}