The public QR display requests a time-limited signed token for its configured point. Depending on the server response it may show a loading state, an inactive point message or an error instead of a valid QR.
What is this option for?
Use this when the shared screen is no longer displaying a scannable code.
Before you begin
- A QR point has been created in ATS Cloud.
- You have the actual Public Link used by the screen.
Understanding the controls
- Inactive
- The saved point is not currently active; the display clears the QR.
- Token missing / Load failed
- The display could not obtain a usable token.
- Refresh Countdown
- Time until the next QR change.
- 90-second expiration
- The display clears an expired token rather than displaying an unusable one.
Step-by-step instructions
- Open the Public Link on the display browser.
- If the screen reports Inactive, sign in to ATS Cloud → QR Code.
- Open the matching QR point and inspect Active; enable it and Save if appropriate.
- If the display reports a loading error, check the browser’s network reachability and the public URL.
- Check whether the QR point has been removed or the Public Link is incorrect.
- Allow the page to retry fetching a token; the Angular code retries after request errors.
- Observe the countdown and verify that a new token appears after the refresh interval.
- If a token expires while refresh fails, expect the QR to clear rather than treating the previous code as valid.
What happens next?
The public display renders a code only when it has an active point and a usable token.
Important notes
- A static screenshot of a QR code cannot be used as a long-running attendance display.
- Do not confuse an employee’s failed scan with a display that lacks a current valid token.