Set up day permits for your club

Create the permit offering

Open Admin → Memberships & access → New offering and choose Day pass. Set the price, holder type, description and status. A day pass is valid for its selected visit date and, when a gate is involved, the community's configured gate window; it is not settlement time plus 24 hours.

Use separate offerings when adult, junior, senior or venue-specific permits have different prices or rules. The offering name is customer-facing and helps reporting, but it does not select the At the Gate category.

Configure gated venues

Open Admin → Settings, add each meeting location, and place the correct ATG category ID on every gated venue. A location without a category is not offered as an ATG gate destination.

The permit page can use a confident route match or ask the visitor which gated venue they are using. Categories come from that route-matched or selected location. The data model has an offering-specific gate-location field, but the current offering editor does not expose it, so do not rely on a venue restriction that owners cannot configure.

Add the right terms

Create active documents under Admin → Waivers. A document can be required community-wide, at signup, for every day-pass offering, or for selected offerings. More than one document can apply to the same permit.

The offering's Terms of use picker is a convenient direct link to one document, but it is not the only way to apply terms. JollyBee writes the acceptance evidence when the server accepts the permit checkout submission, against the version presented in that flow—not merely when a checkbox changes on screen and not only after payment succeeds.

Test the public form

The hosted route is /c/your-slug/day-permit. It can collect a permit tier and quantity, party arrival choice, companion identities, email, mobile, visit date, route, applicable agreements and guardian relationship where required. Recognition or verification can add an identity step.

Complete the exact mix a real visitor will buy. Confirm the resulting visitor, party members, terms versions, visit date, route, permit page, PDF and payment.

Follow up after the visit

Under Admin → Communications → Automations, the after a day-permit visit trigger supports:

• Once per visitor — the default, enrolling the person for the first eligible visit after activation.
• Run again on every visit — a new eligible permit can enrol the same visitor again.

The web builder has an effective minimum delay of one day; entering zero is saved as one. The scan uses the activation calendar date, so a visit earlier on that same date can still qualify; older visit dates are excluded. An automation WhatsApp step sends free-form text and does not select an approved Meta template, so use it only inside an open 24-hour customer-service window. Merely having an approved template on the account does not change that automation behaviour.