Skip to main content

Guest pass settings

Configuring barcode format, redemption instructions, and how unique pass codes are built.

The Settings page controls how guest passes are presented and how codes are generated (when enabled).

Options

  • Allow Passes to be Shared: Enable sharing to allow members to send guest passes to friends and family.

  • Collect Guest Information: Prompt guests to provide optional contact information that you can use for follow-up communication.

  • More info URL: URL where your members can learn more about guest passes.

  • Redeem Instructions: Short instruction presented to guests when redeeming guest passes. Should be no longer than 100 characters.

  • Barcode Type: (optional) barcode type to display when a pass has been redeemed.

Barcode format

How the pass code is displayed visually.

Option

Behavior

Disabled

No barcode rendered

Code128

Linear 1D barcode

QR

2D QR code

The code value itself is the same regardless of barcode type.

Pass code segments

Pass codes can be built from one or more concatenated segments. This lets you generate guest pass codes that match the exact format your membership system supports.

There are three segment types:

Type

What it produces

UniqueIdentifier

A unique, non-sequential identifier - useful for prefixes, suffixes, or segment separators.

AscendingRange

A sequential number that counts up. Configure Range Start, Range End, and the current position. Each new pass gets the next number; when the range is exhausted, no more passes can be created until the range is extended.

DescendingRange

Same as AscendingRange but in reverse.

Example

If your codes need to look like MEM-2026-000123, you might configure:

  1. Segment 1 (Value: MEM-) — literal prefix.

  2. Segment 2 (Value: 2026-) — literal year prefix.

  3. Segment 3 (AscendingRange, RangeStart: 1, RangeEnd: 999999, padded) — sequential counter.

Tweak as needed. Drag-to-reorder segments to change the concatenation order.

When to use pass code segments

For most orgs, the default (a single UniqueIdentifier segment) is fine — it produces opaque codes that are unique and impossible to guess. Customize segments only when you have an integration or business rule that requires a specific format.

Did this answer your question?