Skip to content
EntryWick documentation

EntryWick documentation

One page per screen, written before the screen was designed and kept with it since: who opens it, what they came to do, and what must be true when they leave. Start where your question is.

Getting started

From signing up to an event people can register for.

Setting an event up

The event itself, its days, and the ways in.

Registration

What happens after somebody signs up, and what they can change.

Tickets and check-in

Getting people through a door.

  • Ticket — `/t/{code}`

    For an attendee at a gate, or twenty minutes before they leave home.

  • Wallet tickets

    For attendees on their phones, the night before or in the queue.

  • Check-in points (event page)

    For an organizer with `checkin.manage_points` (Owner, Admin), setting an event up or re-pinning the day.

  • Scanning devices (event page)

    For an organizer with `checkin.manage_devices` (Owner, Admin) — the evening before, handing out phones,.

  • Scanner app (entrywick.app)

    For check-in volunteers and staff, usually on their own phones, often with weak signal, often before.

  • Self check-in kiosk (scanner app, week 20)

    For an attendee walking up to the tablet, alone, who has never seen the app and may not have their ticket.

  • Help desk

    For registration-team members and admins at a laptop, with a queue in front of them.

  • Badge runs

    For an organizer or group lead the week before, on Events → Badge runs. Somebody limited to a group (a.

  • Live dashboard

    For organizers and group leads on event day, often on a laptop at the registration table, sometimes on a.

  • Reports

    For organizers the morning after, group leads counting their own people, finance and viewers answering.

Telling people things

Email, text and the copy that goes out.

Making it yours

Your brand, your address, your roles.

Money

What you pay, what you charge, and where it goes.

Connecting other software

The API, webhooks, and the apps built on them.

Running it yourself

A licensed install on your own server.

Keeping the record

Who did what, and when.

When you need us

Whether it is us or you, and how to ask.