Self check-in queue

CampOne can let your guests check themselves in before they reach the campsite by filling in a form on their phone or laptop. When the optional self-check-in feature is set to admin approval mode, every submission lands here in a queue and waits for your team to review it. You see the guest’s name, the booking, what they entered, and you approve or reject in one click. The guests themselves never see this page — they have a separate, simpler page on their device. This screen is the operator’s side of that conversation.

How to find it

In the sidebar under Gäste (Guests), click Self-Check-in. The entry only appears when your tenant has self-check-in switched on and set to admin approval mode. If your tenant runs the auto-HESTA mode, submissions skip this queue entirely; if the feature is off, the entry is hidden altogether.

A small red badge next to the menu entry shows how many submissions are waiting.

What’s on the page

Page header

A page title — Self-Check-in-Warteschlange (self-check-in queue) in German, or Self check-in queue in English. There are no tabs, filters, or date pickers; the page lists every pending submission in one column.

Submission cards

Each pending self-check-in is rendered as a card in a vertical stack. A card contains:

• Gast — the guest’s name, in bold.
• Buchung — the booking reference and pitch number (e.g. CMP-AB12CD · Pitch 14).
• Anreise — the booking’s check-in date.
• Eingereicht — the timestamp when the guest submitted the form.
• Submitted data — a collapsible details block. Click it to expand and see the raw fields the guest filled in (names, ID numbers, country, vehicle plate, signature payload, etc.). It is presented as JSON because the exact set of fields depends on what your tenant has configured to ask for.
• Notizen — a free-text input where you can leave an internal note that travels with the approval / rejection (e.g. “ID photo unreadable, asked for re-upload”).
• Approve button (filled blue) — green-lights the submission, marks the booking as checked in, and removes the card from the queue.
• Reject button (red) — sends the submission back; the card is removed from the queue but the guest is allowed to resubmit later.

Empty state

When the queue is empty, the cards area is replaced by a short message — Keine ausstehenden Self-Check-ins. (no pending self check-ins). New submissions appear automatically as guests submit them; the page polls every thirty seconds in the background.

The companion guest-facing page

Guests use a separate, mobile-friendly page at /checkin/<token> to fill in the form. You will not normally visit that URL — guests reach it through a tokenised link in their pre-arrival email or QR code. It is mentioned here only so you know where their data is coming from.

Common workflows

Approve a submission

1. Open the Self-Check-in queue from the sidebar.
2. Find the card for the guest.
3. Expand Submitted data and skim it. Confirm the names, dates, and any required identification look right.
4. Optionally type a short note in the Notizen field.
5. Click the blue Approve button.
6. The card disappears. The booking is now checked in; the guest is good to go.

Reject a submission

1. Open the queue and find the card.
2. Expand Submitted data and identify what is wrong (illegible photo, missing field, wrong booking).
3. Type a short reason in the Notizen field — this helps your team and the support inbox if the guest contacts you later.
4. Click the red Reject button.
5. The card disappears from the queue. The guest can submit again from the same link if they want to fix the problem.

Catch up on the queue at the start of a shift

1. Open the queue. The badge in the sidebar tells you the number to expect.
2. Work top-down — submissions are listed roughly in the order they came in.
3. Approve the straightforward ones first, then circle back to the ones that need a closer look at the submitted data.

Spot-check a busy arrival day

1. Make sure your tenant is set to admin approval mode (the menu entry is visible only then).
2. As guests submit during the day, new cards appear at the top of the queue automatically.
3. Approve them one by one so the Arrivals screen and the dashboard reflect them as checked in immediately.

Tips and gotchas

• The page polls in the background every thirty seconds. There is no manual refresh button — open and close the page or switch tabs to force an immediate refresh if you need one.
• There is no bulk approve / reject action. Each submission is reviewed and acted on individually, by design — these are legally relevant data submissions.
• Submitted data can include sensitive information such as ID document numbers or photos. Treat the page accordingly: do not screenshot or share these cards.
• A rejection does not block the guest from trying again. If you reject because the data is fraudulent rather than just wrong, contact CampOne support and consider cancelling the booking.
• Approving a self-check-in marks the booking as checked in. It does not take any payment — open the Booking detail page if a balance is still outstanding.
• If the Self-Check-in entry has disappeared from your sidebar, your tenant has been switched to auto-HESTA mode (no manual review) or the feature has been turned off. Check Einstellungen or contact your CampOne onboarding contact.
• The companion guest-facing page (/checkin/<token>) is not intended for staff use. Visiting it would only show the guest’s own form view.

Related pages

• Arrivals — daily check-in / check-out queue for everyone, online or not
• Booking detail — open the booking the submission belongs to
• Registration cards — the Meldescheine generated from approved check-ins
• Settings — switch the self-check-in mode for your tenant