Overview
This guide provides comprehensive information for administrators responsible for setting up and maintaining the SEAtS Mobile Application.
Access Profiles and External Keys
Map Azure AD / ADFS user groups (e.g. Admin, Lecturer, Students) to SEAtS access profiles using the external key field. Students in the same group in source authentication will access the mobile app using the same login credentials that were passed in on the student import (Student Login ID field). Ensure site access = mobile app is enabled for the student access profile.
Lecturer Access
Lecturers can download the app to view their schedule and use their device as a beacon. Ensure: the Timetable file includes TUTOR_ID and TUTOR fields; the Staff file has mandatory fields completed with staff type LECTR; and the Staff Beacon permission is enabled in the lecturer access profile.
Adding Devices in the Admin Site
Navigate to the Devices tab in the Admin site to add beacons, card readers, QR devices, and GPS devices.
Adding a Beacon: Click Add, enter description, serial number, asset tag (optional), tick the Beacon checkbox, associate to room(s), and save.
Adding a QR Code Device: Add a device named exactly Scheduled QR Mobile App Checkin and associate it to all rooms where QR check-in will be used.
Adding a GPS Device: Add a device named exactly Scheduled GPRS Mobile App Checkin following the same steps as QR.
Adding a Lecturer's Phone as a Device: Add the phone as a device with a GUID-generated serial number, tick Beacon and Is Active, and associate to the relevant rooms.
Beacon to Room Quantity
The number of beacons required depends on room capacity. Refer to the BLE Beacon Set Up Guide for detailed guidance and test within the venue to optimise range.
QR Code Check-In
Requires two access profile permissions: Lecturer and Student mobile app permissions. Associate a QR device (Scheduled QR Mobile App Checkin) to every room where QR check-in will be used.
Fault Diagnosis — Common Issues
All students unable to check in: Check that the room has a device associated; verify the device is powered and associated to the correct room; check for timetable import failures.
Some students unable to check in: Verify student is in the import file and correct authentication group; check student is on the schedule for the event; check lesson type cut-off configuration.
Device-level checks: Enable location services (precise), Bluetooth, camera permissions; disable Airplane mode; enable automatic updates; ensure latest iOS/Android version.
Mobile App Security
A configuration is available on request that ties a student to their specific device, preventing shared device check-ins.
Error Logging
Enable error logging for an individual student in the Admin site (Users > search for student > enable error logging). The student can then send an error report from the app settings.