Place QR Onboarding and Auto Check-In States
How QR entry moves between onboarding, browse-only, auto check-in success, already-checked-in, and error states on place pages.
Where you see this in the app
These states appear when someone reaches a place through a QR code or QR-style short link.
The main user-visible states are:
| State or label | What it means |
|---|---|
QR onboarding | You need to verify your email before the app can finish the place check-in flow |
Browse this place page | Skip immediate onboarding and just open the place page first |
Completing check-in from QR... | The app is attempting the automatic post-sign-in check-in |
checkedIn=1 style success outcome | Auto check-in succeeded and the place page should now reflect that |
alreadyCheckedIn=1 style success outcome | You were already active at this place, so no second check-in was needed |
checkInError=1 style error outcome | The app could not complete the QR-triggered check-in automatically |
QR onboarding vs browse-only
QR onboarding exists because place chat and place presence depend on an account-aware check-in, not just opening a page.
From an end-user perspective:
QR onboardingis the fast path into email verification plus place activation,Browse this place pageis the lower-commitment option when you want to look first,- the referral badge, when shown, means the QR visit is carrying a referral code into onboarding.
So opening a QR link does not automatically mean you are already checked in.
Auto check-in success, already checked in, and error
After sign-in, the app tries to finish the check-in automatically.
| Outcome | Practical meaning |
|---|---|
| Success | Your featured profile workspace check-in was created or refreshed for that place |
| Already checked in | You already had an active qualifying check-in there |
| Error | The place page opened, but the account-aware check-in did not complete automatically |
The important design point is that the place page still remains reachable even if auto check-in fails.
Why place chat depends on check-in state
Place chat is tied to active place presence, not just page viewing.
That is why the QR flow is opinionated:
- identify the place,
- complete sign-in if needed,
- attempt the profile-workspace check-in,
- then unlock the place-aware experience such as chat.
This keeps place chat tied to actual active presence rather than anonymous drive-by browsing.
What to do when QR state feels stuck
If the QR flow feels confusing, the user-facing recovery path is straightforward:
- open the place page directly,
- confirm you are signed in,
- try the normal place check-in action again,
- if the page says you were already checked in, treat that as success rather than a second action requirement.
In other words, already checked in is not a failure. It is the app telling you the place-presence state was already active.
See it in action
Previous
Places, QR Entry, and Place Chat
How place pages work, what QR entry does, and how active presence affects check-ins and access to place chat.
Next
Place Chat and People at This Place
How place chat unlocks, what anonymous and checked-in viewers can see, how the At location only filter behaves, and what the People at this place list represents.