Local check-in for Custom Resources lets administrators require users to be physically at the office location to check in to their custom resource reservations, such as parking spots, lockers and iPads.
It works like desk local check-in and supports 2 methods: WiFi check-in and Badge check-in. This article lists the key differences between desk and custom resource local check-in.
It also explains how to set up local check‑in for custom resources with badge swipes and Wi‑Fi connections, and what your employees see.
Related articles:
- Set up automated desk check-ins with Wi-Fi
- Use local desk check-ins only
- Access Control integrations
Local check‑in types
Custom resources support 2 types of local check-in.
Badge‑based local check‑in
Badge-based local check-in uses events from your access control system, such as door readers and turnstiles, to mark a user present. A successful badge swipe at a configured reader checks the user in for the day at that location.
Wi‑Fi‑based local check‑in
Wi-Fi-based local check-in uses a user’s connection to your corporate Wi‑Fi as the signal. The first successful Wi‑Fi connection from a known network checks the user in for the day at that location.
What “local check‑in” does
Local check‑in marks someone as “checked in” for the day at a location when they swipe their access badge at a configured reader, or when they connect to your corporate Wi‑Fi from a configured network.
The check-in applies for the full day, in the location’s local time zone:
- Check‑in is not limited to the reservation window.
- If a user connects early or late (outside reservation times), Robin still shows them as present for that day.
With custom resources, such as parking spots:
- If the user has a reservation, the local signal checks them in to that reservation.
- If the user has no reservation, they can still show as present in the space (depending on configuration).
Cross-building check-in
If a user has a desk in Building A and a parking spot in Building B, and they connect to the Wi-Fi, Robin marks both resources as checked in under a single campus-level visit.
Building set-up
You can turn on this setting for whole office buildings or for specific resource groups.
Enable on the office building level
- Go to Manage > Offices > and select a building.
- On the Administration tab > select the resource from the resource policies menu at the top.
-
Turn ON the Local Check-Ins Only setting.
Resource set-up
In the layout, open your resource groups. In each template, make sure local check‑in is on.
End‑user experience
How “all‑day” check‑in behaves
One event sets presence for the full day. The first qualifying badge swipe or Wi‑Fi connection sets the user’s presence status for the whole day at that location, whatever the reservation time.
If the user connects 30 minutes before or 2 hours after their scheduled resource time, the check‑in:
- Still marks them present for the day.
- Still satisfies any check‑in requirement tied to that resource (abandoned resource protection rules, etc.).
Leaving and coming back does not remove the day’s check‑in. Later swipes, and Wi-Fi disconnects and reconnects, do not change it. Once a user checks in, Robin shows them as present for that day.
Warning
- The Local Check-In Only policy does not apply to desk reservations that already exist. It applies only to reservations made after you turn on the policy.
- Wi-Fi check-ins do not work with a VPN or with products that mask user IP addresses.