Xangle
Xangle Portal
Sign in

Product

Xangle Sharing Server

Deliverables & delivery

Outputs & sharing

Use Outputs and Share Settings to decide what guests receive, how they open it, and what information is collected at handoff.

Plan deliverables

Define the output set before opening Share

  • Decide which outputs are actually needed at handoff: image, video, combined media, thumbnail, and any print-specific version.
  • Keep output naming clear so operators can quickly identify what is guest-facing versus archival.
  • Use Process recipes to lock branding, overlays, framing, and ratio choices before the first live capture.
  • Keep the output list lean. Too many variants slow down review and increase wrong-action clicks at the station.

Match outputs to the delivery path

  • QR and direct download should point to files that are light enough for phone delivery on event Wi-Fi.
  • Email delivery should use the same branded files guests expect from QR, unless you intentionally send a different variant.
  • Printing should have its own prepared source strategy (input, processed, both, or auto) so print quality is predictable.
  • Portal delivery is best when links must stay valid after the booth machine powers down.

Operator checklist before doors open

  • Confirm one complete flow for each promised action: QR, email, print, and portal link when enabled.
  • Confirm filenames and sorting make sense when multiple outputs are attached to the same capture.
  • Confirm terms and custom fields only collect what the event actually needs.

QR sharing

When to use QR sharing

  • Use QR sharing when guests scan from the station and complete delivery on their own phone.
  • Use it for single captures or multi-select batches from the Share screen.

Configuration points that matter

  • Choose QR placement for operator clarity: overlay on media preview or hidden from inline cards.
  • Tune QR size and overlay position so the code stays readable on your actual sharing display.
  • Keep direct download enabled when guests should save files immediately after opening the share page.
  • Enable "require email before QR" only when your event needs contact collection before phone handoff.

Live-operation checks

  • Confirm Share is enabled and relay status is connected when using cloud QR mode.
  • Scan from at least one Android and one iPhone device on the event network.
  • Confirm both single-item and bulk QR flows if operators will share multiple captures together.

Offline QR sharing

What offline QR mode changes

  • Offline QR mode bypasses cloud relay delivery and serves files from the local machine.
  • The share modal shows two QR codes: one for joining Wi-Fi and one for opening the local download page.
  • This mode is intended for venues with unstable internet or fully offline operations.

Setup requirements

  • Configure a dedicated sharing hotspot and set the expected Wi-Fi SSID in Share Settings.
  • Keep the sharing station and guest phones on that same local network segment.
  • Test with real phones before doors open. Do not rely on desktop browser simulation for this mode.

Operational cautions

  • If guests cannot join Wi-Fi, the download QR will still fail even if the code scans correctly.
  • If the station sleeps, reboots, or changes network, retest both QR codes immediately.
  • Use portal delivery instead when links must remain reachable after the local station is gone.

Printing

Enable printing in the right places

  • Turn on printing in Share Settings, then enable the print action in the Share preset used at the station.
  • Refresh the printer list and choose a preferred printer before the event starts.
  • Set paper size and copy limits so operators cannot accidentally overload a printer line.

Choose print source strategy

  • Input: fastest path from original files.
  • Processed: uses branded outputs from recipes.
  • Both or auto: useful when some captures have processed files and others do not.
  • Enable fallback to input when processed files might not be ready in time.

Live print workflow checks

  • Test single and bulk print flows from the actual Share station.
  • Verify quantity prompts only if your team needs per-job copy overrides.
  • Watch print job status (queued, printing, completed, failed) during early event traffic.

Email sharing

Core email flow

  • Use email sharing when guests should receive a delivery link after operator confirmation.
  • Keep templates, subject line, and reply-to aligned with the event brand before the first capture.
  • Use required terms and custom fields only where compliance or follow-up needs justify the extra steps.

Controls that affect delivery quality

  • Enable multiple recipients only when operators are expected to send one capture to several contacts.
  • Keep direct download available when email inbox access may be delayed on site.
  • Verify SMTP sender configuration and test against real inbox providers before launch.

Queue operations

  • Monitor queue state for sent, pending, uploading, and failed jobs.
  • Use queue details to inspect dataset path, attached files, subject preview, and rendered email body.
  • Retry failed items from queue actions after fixing config or connectivity issues.

Download email list

What this export contains

  • Export from Share Settings Logs to download a CSV of email queue recipients.
  • Each row includes recipient email, dataset folder, status, sent date, plus configured custom fields.
  • The export reflects queue history and filters, so apply your date and state filters before exporting.

Why teams use it

  • Post-event handoff to marketing or CRM systems.
  • Delivery auditing for sent versus failed batches.
  • Field-level analysis when custom form data is captured during sharing.

Good practice

  • Export at least once during rehearsal to validate field mapping.
  • Keep a final export snapshot at event close for reporting and recovery workflows.

Portal delivery

When portal delivery is the right choice

  • Use portal delivery when links must remain active after the local sharing station is offline.
  • Use it for events where guests often open media later, not only on-site.

Dependencies to verify

  • Confirm internet reachability and relay connection from Share Status.
  • Confirm the app has a valid login session. Invalid or expired sessions can block relay startup.
  • Keep offline QR mode disabled when you need cloud relay behavior, because offline mode bypasses relay delivery.

Operational notes

  • Run a full phone test from scan to final open link before guests arrive.
  • Keep one operator check focused on relay and portal status after any network change.

Run a test share

Full pre-event test sequence

  • Capture one real sample and verify all expected outputs exist.
  • Run one QR share from the station screen and open it on a real phone.
  • Run one email share and confirm inbox delivery, template rendering, and link behavior.
  • Run one print job if printing is enabled, including copy-count behavior when quantity prompts are enabled.
  • Run one portal delivery validation when cloud relay mode is expected.

Validate details, not only success

  • Confirm filenames and output variants are understandable to operators.
  • Confirm terms, custom fields, and required email gates match the event policy.
  • Confirm timing is acceptable under normal venue network conditions.

Record and fix before go-live

  • Log every mismatch (wrong branding, missing output, failed queue item, broken QR, print error).
  • Fix settings first, then rerun the same test path until results are stable.