In GiveCampus Events, available controls depend on your permissions and the interface used by your institution.
First identify the event email interface. In the legacy Email Settings flow, Include QR Code For Check-in controls the registration-details QR; clear it to omit the code from that flow or select it to include it. In the configurable email-template flow, the registration token picker includes $QR_CODE$, which is replaced with the registration-specific check-in image. Add/remove the token in the relevant supported template and preview/test the message. These are different controls; not every template, particularly waitlist messages, has the same token list. Changing a setting does not remove an image from emails already sent.
The code contains an administrator attendance URL identifying the registration. Staff use the event's QR scanner with check-in permission and camera access. The scanner decodes image pixels and validates the school's check-in URL format; it does not require that the code be displayed inside the original email. A clear, complete screenshot of the same code can therefore be scanned. Image quality, crop, print size and device can affect scanning. Test the image and use attendance search if necessary.
Scanning opens the relevant attendance records rather than automatically marking every person attended. RSVP status and checked-in state are displayed separately. An attendee marked Not attending can still be present when their registration remains eligible for the attendance list; review the current records. A canceled/ineligible registration is a different case. Do not assume that scanning an old code restores admission, changes RSVP or checks in a guest automatically.
Comments
0 comments
Please sign in to leave a comment.