Settings — Token Conversions
Token Conversions define rules for transforming raw access credential (Wiegand) byte data into the decimal values that the access control system compares against stored credentials. Each conversion specifies a name, a conversion type, and a byte extraction configuration.
Add New Token Conversion
Clicking + (requires token-conversion:create) opens the Add New Token Conversion dialog:
| Field |
Description |
| Name |
Required — human-readable label |
| Conversion Type |
Required — defaults to HEX TO DECIMAL |
| Configuration |
Structured byte-extraction form (see below) |
| Field |
Description |
| Byte Start |
Zero-based index of the first byte to extract |
| Byte End |
Inclusive index of the last byte to extract |
| Reverse Byte Order |
Whether to reverse bytes before conversion |
A live summary is shown below the form, e.g.: “This configuration will extract bytes from position 0 to 3 (reversed) and convert them to decimal.”
Token Conversion Detail Panel
| Property |
Editable |
Permission |
| Name |
Yes |
token-conversion:update |
| Conversion Type |
Yes |
token-conversion:update |
| JSON Data (byte config) |
Yes |
token-conversion:update |
A Delete Token Conversion button (requires token-conversion:delete) opens a confirmation before permanently removing the conversion.
Permissions
| Action |
Permission |
| View token conversions |
/settings/token-conversions route |
| Add conversion |
token-conversion:create |
| Edit name / type / config |
token-conversion:update |
| Delete conversion |
token-conversion:delete |
← Back to Settings