How day permits work

A day permit gives a visitor access for one selected visit date, subject to the community's rules and configured gate window. It is not a membership, does not renew, and is not a generic 24 hours measured from payment.

What a completed permit can produce

Depending on how it was sold and which contact details were captured, the visitor can receive:

• A secure permit page showing the visitor, date, route, party details and gate state.
• A printable PDF with a tear-off stub and QR code, downloaded from that page.
• An emailed permit link when an email address was captured and delivery succeeds.
• An At the Gate code and PIN when the community uses that integration and the visitor requests access for a gated venue.

A phone-only counter or claim flow can create the person and permit without an email. Staff must then give the visitor the permit or claim link through the supported route; the system cannot email an address it never received.

The buyer becomes a visitor record

JollyBee first tries to match a trustworthy existing identity. An exact email can identify a person. A phone match is treated more cautiously because lines can be shared or recycled; an ambiguous phone does not silently merge two people.

Hosted /day-permit checkout currently requires both email and mobile. Some counter and off-platform flows can create a phone-only visitor. A phone-only record is useful for operations and permitted messaging, but it cannot sign in until it is linked to a login identity.

Day permits, session passes and active weekly or monthly temporary passes are normally classified as day visitors for communication audiences. They do not become full members unless the offering's holder type was deliberately changed.

The purchase routes are not identical

• Hosted day-permit checkout collects the visit and party details, applicable terms and payment through JollyBee.
• The community's own PayStack storefront sends payment into a claim/callback flow that creates the permit after the missing visit details and terms are completed.
• SnapScan settles to the community's merchant account and sends the buyer through a confirmation claim.
• Web Admin counter sale requires a mobile number, takes a visit date and optional route, and creates a gate grant.
• Mobile or offline POS records a walk-in sale for today. It can complete without a phone, but a permit link or gate grant is created only when the item is a day pass, gate access is enabled and a phone was supplied.

These routes can therefore produce different delivery records even when they sell the same offering. Read Permits sold on your storefront, a SnapScan board or at the counter before printing instructions.

What owners see

Open Admin → Day permits for the permit, visit, payment rail, contact, delivery and gate state. Labels such as No gate needed, Needs code, Code issued, Withdrawn or Expired are a prioritised console view, not steps every permit passes through in one fixed order. For example, a permit explicitly marked No gate needed can keep that operational label after its date.