> ## 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. # Onboarding Checklist > Step-by-step setup from zero to your first confirmed attestation Follow this checklist in order. Each step unlocks the next. ## Phase 1 — Account setup Contact Forager support to provision your company account. A Harbingers team member will set up your company in the system and send an admin invite to your email address. Look for an email with the subject **"You have been invited"**. Click the link inside — your account is verified automatically, no password needed at this step. You will land on a welcome page confirming you are in. You are now the account admin for your company. Log in to the dashboard at [dashboard.harbinge.rs](https://dashboard.harbinge.rs) to continue setup. If you ever need to log in on a new device after the invite link expires, use the **Forgot Password** flow on the login screen to set a password. In the dashboard, go to **Team** and use the **Invite Team Member** card to send an email invite to each field technician. When they click the link in their email, they land on a welcome page with a direct link to download the Forager app from Google Play. They sign in with the email address the invite was sent to — no separate password setup required. On first sign-in, techs will see a **"Biometric lock enabled"** sheet. This is expected — Forager automatically encrypts their session using the device's fingerprint or face unlock. They tap **Got it** to continue. On every subsequent app open, they will be prompted to authenticate before the home screen appears. They can manage this in Profile → Security. Full guide: inviting members, changing roles, and removing users. If your team uses Zebra or Honeywell devices with hardware barcode scanners, set the input mode before techs start scanning. In the app, go to your profile avatar → **Admin** → **Scanner Input**. * **Auto** (default) — the app detects the scanner and uses it if present, otherwise falls back to camera. Works for mixed fleets. * **Hardware** — always uses the hardware trigger. Recommended for dedicated scanner fleets. * **Camera** — always uses the device camera. Use this if you want consistent behavior regardless of device type. See the [Scanner Settings](/dashboard/scanner-settings) guide for details, including the camera fallback option and company-level defaults. New team members have no site access until you assign them. In the dashboard, go to **Sites** and add each technician to the buildings they work in. A tech assigned to a building can see and confirm every asset inside it — all floors and rooms are included automatically. Techs not yet assigned to any site will see an empty screen in the app. If your team works out of a single building, assign everyone to that building. If you have multiple locations, assign each tech only to the buildings they cover. Full guide: assigning techs to buildings, multi-site access, and what techs see. ## Phase 2 — Location hierarchy In the Forager app, navigate to **Manage Locations**. Build out your hierarchy from top to bottom: * Campus or site (optional) * Building * Floor * Room You only need to create rooms you intend to track assets in. You can add more rooms at any time. For each floor node, you can upload a floor plan image (JPEG or PNG recommended). This enables the visual floor plan view in the dashboard and helps techs navigate during Device Hunt. PDFs are supported but interactive pins are not available for PDFs. Convert to JPEG or PNG for the best experience. After uploading, tap each room's pin icon to place it on the floor plan. This only needs to be done once. Once floor plans are uploaded and rooms are pinned, field techs can use the **Floor Map** view — accessible by tapping the map icon next to any floor — to do visual confirmation rounds: walk the floor, tap red pins to confirm rooms, and track coverage at a glance. ## Phase 3 — Survey Survey teaches Forager what each room looks like on the Wi-Fi and Bluetooth spectrum. Without survey, the app cannot determine which room a tech is currently in. For each room: 1. Have a tech stand in the room with the Forager app open 2. Open **Survey Mode** 3. Select the floor and room 4. Tap **Capture** — the app takes 4–6 RF scans over about 30 seconds 5. Move to the next room and repeat A full floor of 10–15 rooms typically takes 20–30 minutes. After surveying, open **Coverage** in the app. Rooms show as: * **Green** — well surveyed, ready for attestation * **Yellow** — thin coverage, consider re-surveying * **Gray** — not yet surveyed All rooms should be green before starting regular attestation work. ## Phase 4 — First attestation Have a tech stand in a surveyed room, open the Forager app, and scan an asset barcode. The app will: * Identify the current room from the RF fingerprint * Look up the asset's recorded location * Confirm a match or flag a mismatch * Write an attestation record That attestation record is now visible in the dashboard. Log into the dashboard at [dashboard.harbinge.rs](https://dashboard.harbinge.rs). Open **Floor Plan** and select the floor where you just scanned. The room pin should show the asset count with a green indicator (confirmed within 7 days). ## Phase 5 — CMDB integration (optional) Rather than adding assets one by one, export a CSV from your CMDB (ServiceNow or equivalent) and upload it from the dashboard **Assets** page. Forager will create every asset in the file in seconds. The import accepts `asset_tag`, `name`, `description`, `serial_number`, `cmdb_id`, and `cmdb_location`. Only `asset_tag` is required. Re-importing is safe — existing records are updated, confirmed location data is never overwritten. Learn how to bulk-import from CMDB and export the current roster as CSV. To push every attestation back to ServiceNow automatically, configure a webhook from the dashboard **Settings → Webhooks** page. Connect Forager to ServiceNow to push location updates to CI records automatically.