The Attestation Log shows every confirmation your team has recorded — matches, mismatches, and new assets discovered. Use it to verify that your scans were recorded, review what happened during a session, or look up when a specific device was last confirmed.Documentation Index
Fetch the complete documentation index at: https://docs.harbinge.rs/llms.txt
Use this file to discover all available pages before exploring further.
Opening the Attestation Log
From the Forager home screen, tap Attestation Log.Reading the log
Each entry shows:| Field | Description |
|---|---|
| Asset tag | The barcode that was scanned |
| Type | Match, mismatch confirmed, mismatch dismissed, or new asset |
| Location | The room recorded at the time of the confirmation |
| Tech | Who performed the scan |
| Time | When the confirmation was recorded |
Searching
Type in the search bar to find entries by asset tag or location. Results update as you type. Tap ✕ to clear the search and return to the full list.Filtering
Tap a filter chip at the top of the screen to narrow the list by result type:- Match — confirmed in expected location
- Mismatch — asset found in unexpected location
- New asset — first time this asset tag was seen by Forager
What the log is used for
Day-to-day: If a scan did not seem to register, check the log to confirm the record was written. Look for the asset tag and the timestamp matching when you scanned. Compliance reviews: Your IT director or manager can pull a full attestation history from the web dashboard Reports page, including CSV export. The in-app log is a quick reference for individual techs. Mismatch follow-up: If you dismissed a mismatch earlier in the session, you can find the record here to confirm the asset tag and original location in case you need to follow up.The in-app log shows recent records. For full historical reporting, filtered by date range, location, or tech, use the Reports page at dashboard.hiveriselabs.com.