Built for your team on site.
On the tablet, your team can scan credentials, record attendance and submit accreditation requests for artists and their crews. Event setup stays in the web platform.
Installing the appiOS
TestFlight, by invitation
Not published on the App Store. The invitation goes to the crew member’s own address, per event, and is withdrawn at close-out.
Android
APK, from us
Not published on Google Play. The file goes only to crews accredited on the event, straight from us.
The app does not work without an authentication token. The token is issued at sign-in and travels with every request; without it, any query comes back empty. On top of that, the account has to hold a role on that event: a valid account on another event sees nothing here.
- Platforms
- iOS and Android
- With no signal
- Local queue, synced on reconnect
- Access
- Sign-in and an account assigned to the event
- Scan
- Credentials
- Talent and backstage
- Shifts
- Attendance
- Sync queue
- Terminal
Scans the credential
The QR code contains the credential identifier, which is different from the number printed on the badge.
Records badge collection
When the badge reaches its holder, the credential moves to collected, with the time and the source written to the audit trail.
Records the shift
Check-in and check-out times are recorded against the person’s shift, keeping attendance in one place.
Sends backstage requests
The backstage manager adds the people and submits an accreditation request. The organiser reviews and approves it in the web platform.
Stores records offline
Records are stored locally until the connection returns. Resending a record does not duplicate the operation, and the first scan takes priority during synchronisation.
Measures the clock drift
Each record stores the tablet time, server time and the difference between them, along with a sequence number for that device. These details help preserve the order of records when a device clock is incorrect.
- It does not issue credentials. Issuing stays with the organiser, on the web.
- It does not decide who enters a zone. It displays the credential details; entry checks remain the responsibility of the event security team.
- It does not create accounts. An account is granted on the web, by an administrator, and has to be assigned to the event.