At Mapiq, we strive to help organizations optimize their offices and workdays by providing reliable attendance data. While our platform offers detailed graphs and overviews of booked shifts, it only presents part of the picture. To address this, we've introduced the manual check-in feature, enhancing the accuracy of attendance data and offering valuable insights into real estate needs and no-shows.
Enabling Manual Check-in
Follow the steps below to enable manual check-in for your end users.
Log in at https://admin.mapiq.com.
Go to the "Settings" tab.
Select "Check-in" in the left-side menu.
Toggle the button next to "Manual check-in."
Viewing check-in data
Check-in data can be visualized in the admin portal and on the end-user side. In the admin portal, data is displayed on the "Shifts" tab, with a new column called "Checked-in," indicating Yes or No for manual check-ins. Check-in data is also available in the shifts selection export and remains visible in shift history for as long as the retention period allows (see "Data & Privacy" section).
Booking policies and manual check-in
Upon enabling manual check-in, users can confirm their presence at the office, even without a booked shift. However, it's essential to consider the booking policy. End-users may encounter two types of notifications in the app regarding check-in:
Button to acknowledge being at the office.
No button to accept being at the office.
The button is only available to users who can book a shift on the same day. Pressing it reserves a workday for the user. If users can't see the button, it may be due to full office capacity, reaching the limit of bookable shifts, or organizational policies prohibiting same-day bookings.
Mapiq recommends enabling a booking policy that allows users to delete their shifts on the same day, freeing up space for others.
Manual check-out and connections check-in
The check-in feature lets users share their presence at the office with a green dot next to their avatar. After checking in, their status changes to "At the office" in their personal overview.
Users can adjust this status to "Not at the office," considered a check-out event. Changing the status doesn't free up shifts by removing bookings; it serves as a status indicator.
Data & Privacy
Mapiq stores check-in and check-out event data, including timestamp, UserId, BuildingId, EventType, and IntegrationType. This information is used to determine office attendance during shifts.
Data is stored for the retention period specified in the admin portal's "Settings" tab.
It's displayed in multiple ways:
End-users can view their check-in status and details.
Connections see checked-in connections with a green dot.
Admins with access to the "shifts tab" and analytics report can view check-in data.
Users with an API service account can retrieve all individual check-in events for users within their subscriptions via the API.
Regarding personal data, Mapiq is the processor, while our clients serve as controllers. Mapiq is not responsible for how customers handle the data.
