Automatic & Location-specific Check-ins


Set up Automatic Check-ins

In order to set up automatic check-in functionality, you need to configure the accounting data collected by your infrastructure to be sent to IronWiFi as well. This feature is called RADIUS accounting and allows you to configure where the accounting data captured from the network devices is sent.

Please note that not all network gear has it and enabling automatic check-ins based on WiFi might not be possible with your devices.

As this configuration is done in your network devices, it varies from vendor to vendor. Generally, you need to configure one more host, port, and secret, so that this data is also sent over.

Verify The Configuration

To verify if you've set up the accounting feature correctly, do the following:

  1. Log in to the WiFi network with a new user that has received access through the OfficeRnD integration.
  2. Go to the Users list in the IronWiFi console (Users / Users) and verify if the users last seen has been changed.
  3. Go to the Accounting Data report in the IronWiFi console (Reports / Accounting Data).
  4. Verify if a new record for the same user appears there.
Here are instructions on how this is done in Cisco Meraki.

If the record in the report is missing, this means the accounting data is not received in IronWiFi and you need to troubleshoot the problem. In such a case, please contact IronWiFi support for assistance.

Set up Location-specific Check-ins

Location-specific check-ins provide a way for administrators to enable per-location presence tracking that utilizes the IronWiFi integration.

To enable the functionality, admins need to go to the Location tab of the integration settings and map each of their locations (OfficeRnD entity) to all the access points (IronWiFi entity) that should be associated with the respective location.

Location Rules

  • Each location can be selected only once.
  • Each access point can be mapped to only 1 location.

Once the mapping is done, members will be checked into the location associated with the access point they connect to. If the mapping is not done or some locations do not have access points associated with them, members will be checked in against their home location.


Check-in & Check-out Latency

Check-in & Check-out latency allows administrators to define the amount of time a member should be connected or disconnected from the Wi-Fi Network before check-in or a check-out is registered. The settings could be useful if admins don’t want to charge day passes for customers who are passing by just to pick up something or do not spend more than 30 min in the building.

How It Works

The check-in/check-out information is updated every 15 min. In each update, the time that the user has been connected to Wi-Fi is compared to the settings defined in the Check-ins tab. A check-in/check-out is recorded only if it matches the settings.

Rules For Settings

  • Both settings can be configured with values between 5 and 30 min.
  • The default value for a newly activated integration is set to 5 min.

Note: The Check-ins Latency setting should not be confused with the time it will take OfficeRnD to make the check-in/check-out visible in the system. There is no relation between the automatic 15 min schedule and the latency settings.

Was this article helpful?
2 out of 2 found this helpful
Was this article helpful?



Please sign in to leave a comment.