Employee IDs
Employee IDs maps the identifier a device knows a person by — a fingerprint slot, a face id, an access card — onto the employee record in the ERP. Without the mapping a punch arrives and the ERP has no idea whose it was.
Where to find it
Go to EdgeBridge > Employee IDs.
Why people and things are separate
A fingerprint id is always a person and an RFID tag is almost always a thing. Splitting them means neither screen asks you a question the other has already answered — see Item Tags for the goods side.
What a mapping holds
| Field | Description |
|---|---|
| Device id | The identifier the device uses. |
| Device type | Fingerprint / face, or access card. |
| Employee | The ERP employee it belongs to. |
| Gateway | Which gateway it applies to, or any gateway. |
| Status | Active or Disabled. |
Three ways to map
| Route | Best for |
|---|---|
| Fingerprint / face id or Access card | One person at a time. |
| Map many at once | A batch already enrolled on the device. |
| Import from a spreadsheet | A list exported from the device software. |
Enrol employee on device
The other direction, and the better one where the device supports it: the ERP assigns the id and sends an enrolment command, so the mapping exists before the first punch. See Outbound.
Enrolling from the ERP avoids the usual mess. Ids created on the device have to be read back and matched to people afterwards, and the ones that match nobody are only discovered when someone's attendance is missing.
When a save is refused
| Message | Meaning |
|---|---|
| Already mapped | That id is bound to someone else on that gateway. |
| Ambiguous — skipped | The import could not tell which employee was meant. |
| matched no employee | Ids in the file correspond to nobody in the ERP. |
Related pages
- Item Tags — mapping things
- Attendance — what punches become
- Events — unmapped ids show as errors