> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tixfix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Scanning FAQ

> Answers to common questions about scanners, the scanner app, and check-in

<AccordionGroup>
  <Accordion title="What's the difference between Admin and Scanner Plus?">
    **Admin** has full access — events, payments, promoters, communication, reporting, settings.

    **Scanner Plus** can only check attendees in, and only for the events you assign them. They can't see your revenue, change prices, or touch your Stripe connection.

    Give door staff Scanner Plus. It's the right level for someone working one night.

    See [Team members and roles](/get-started/team-and-roles).
  </Accordion>

  <Accordion title="Can a scanner cover more than one event?">
    Yes — assign as many as you like under `Select Events` when you add them, or edit their row later with the pencil icon.

    A new event is never automatically visible to existing scanners. Adding a show to a run means going back and adding it to your door team.

    See [Add a scanner](/scanning/add-a-scanner).
  </Accordion>

  <Accordion title="A scanner can't see the event they're supposed to work.">
    They haven't been assigned to it. An admin opens `Settings → User & Role`, clicks the pencil on their row, and adds the event under `Select Events`.

    Worth checking the day before rather than at the door.

    See [Add a scanner](/scanning/add-a-scanner).
  </Accordion>

  <Accordion title="It says 'already scanned'. What does that mean?">
    That code has been checked in before. Usually one of:

    * **A forwarded screenshot** — two people holding the same ticket.
    * **A double scan** — the reader caught it twice in quick succession.
    * **Re-entry** — they left and came back.

    Almost always honest. Decide your house rule before doors open and apply it consistently.

    See [Troubleshoot scanning](/scanning/troubleshoot-scanning).
  </Accordion>

  <Accordion title="How do I check someone in without a ticket?">
    Look them up on the [guest list](/attendees/guest-list). If they're there, they hold a valid order and can be checked in manually.

    If they can reach their email, [resending the ticket](/attendees/resend-a-ticket) gives them a scannable code in under a minute — usually faster than a manual check-in.

    If they're not on the list, they don't have an order.
  </Accordion>

  <Accordion title="Can attendees leave and come back?">
    Not by rescanning — a second scan of the same ticket reports as already scanned.

    Handle re-entry physically with a wristband or stamp, and brief your door team on it before doors open.

    See [Troubleshoot scanning](/scanning/troubleshoot-scanning).
  </Accordion>

  <Accordion title="Does scanning work with several entrances at once?">
    Yes. Assign every door staff member to the same event and they all scan into one shared record, so a ticket checked in at one entrance shows as already scanned at the others.

    That shared record is exactly what stops one ticket being used at two doors.

    See [Troubleshoot scanning](/scanning/troubleshoot-scanning).
  </Accordion>

  <Accordion title="How do I see the attendee's meal choice at the door?">
    Mark that registration question **shown when scanning** when you set up the event. The answer then appears to the scanner when they check that person in.

    Use it for anything staff act on at the door. Two or three at most — more and the queue slows while people read.

    See [Questions at check-in](/scanning/scan-questions).
  </Accordion>

  <Accordion title="How do I know how many people have actually arrived?">
    **Tickets Scanned** on your dashboard, shown against tickets sold. It updates as people come through, so you can watch arrivals from anywhere.

    The gap between sold and scanned is your no-show rate — useful for planning the next event's capacity.

    See [Sales reports](/reporting/sales-reports).
  </Accordion>
</AccordionGroup>

<Info>
  Still stuck? Email [contact@tixfix.ai](mailto:contact@tixfix.ai) with your event name and a screenshot.
</Info>