---
title: "10. Masters"
space: "CAMS Biometric Integration"
url: "https://docs.navari.co.ke/cams-biometric/key-doctypes-reference-masters"
updated: "2026-05-27"
---

### 10.0 CAMS Biometric Settings

**DocType:** `CAMS Biometric Settings` **Type:** Single (one instance per site)


| Field            | Type     | Description                                      |
| ---------------- | -------- | ------------------------------------------------ |
| `service_tag_id` | Data     | The Service Tag ID issued by CAMS for the device |
| `auth_token`     | Password | 32-character AuthToken for request validation    |
| `start_date`     | Date     | Start date for historical punch log retrieval    |
| `end_date`       | Date     | End date for historical punch log retrieval      |


**Custom Action:** The **Load Punchlog** button triggers the `load_punchlog` server-side function.



### 10.1 Employee (extended fields)

The integration reads from but does not modify the standard FrappeHR Employee doctype. The critical field is:


| Field                  | Description                                                              |
| ---------------------- | ------------------------------------------------------------------------ |
| `attendance_device_id` | The biometric User ID registered on the CAMS device. Must match exactly. |


### 10.2 Employee Checkin

Standard FrappeHR doctype. The integration creates records here. Fields populated:s


| Field                  | Description                                                                  |
| ---------------------- | ---------------------------------------------------------------------------- |
| `employee`             | The matched employee                                                         |
| `time`                 | Punch timestamp (parsed from `LogTime`)                                      |
| `log_type`             | `IN` or `OUT`                                                                |
| `shift`                | Active shift assignment at time of punch                                     |
| `custom_original_time` | *(custom field added by this app)* — preserved original UTC/device timestamp |


### 10.3 Shift Assignment

Standard FrappeHR doctype. After each successful punch log processing, the integration calls `update_last_sync_time()` which updates the `last_sync_datetime` on the Shift Assignment record to reflect when data was last received.