Application gates

An application gate puts a “tell me about yourself first” step in front of anything you sell. Instead of a Book or Buy button, a gated offering shows Apply — the visitor fills in a form you design, you read their answers and decide, and only an approved applicant can come back and complete the purchase or booking. It’s built for offerings where fit matters more than speed: a teacher training, a small-group program, a members-only class series, a practitioner-level service.

The Pro line, precisely. Application gates are a Professional feature, and the form side lives in Gather Grove Forms (its Applications feature). Booking supplies the gate; Forms supplies the application, the decision workflow, and the applicant emails. Without Forms active, a gated offering falls back to whichever behavior you chose — locked shut, or open as if ungated — so a deactivated plugin never silently sells something you meant to gate.

Two tiers of gate

Booking has had a lighter gate since 1.59: Request Access, where a visitor asks to join and you approve or decline with no form involved. Application gates are the fuller tier, and the two compose by a simple rule:

  • No form attached → Request Access. The 1.59 flow, unchanged: one click to request, you approve, they’re in.
  • Form attached → Application. The button becomes Apply, the visitor completes your form, and the decision panel shows their full answers alongside the approve/decline controls.

Attaching a form promotes the gate from the first tier to the second — you never configure the two separately or worry about them conflicting.

What can be gated

Classes, packages & memberships, and services can each carry their own gate — set the application form (and an application page URL, so denied visitors land somewhere helpful) on the offering’s edit screen. There is also one global fallback setting so you can define a default behavior in a single place. Precedence is what you’d expect: the offering’s own gate wins; the fallback covers everything that doesn’t say otherwise.

The flow, end to end

  1. Apply. On the booking form, package shop, or appointment page, a gated offering’s call-to-action reads Apply and leads to your application page. The applicant fills in the form once — duplicates are guarded, so an eager double-submit doesn’t create two applications.
  2. Decide. The application lands in the Forms entries screen with a decision panel, and the owner notification email carries one-click Approve / Decline links (signed, so they work from your inbox without logging in). Declines can carry a note.
  3. Return. The applicant is emailed on receipt and on decision. An approval email includes the next-step link — straight back to the thing they applied for, where the gate now stands open for them.
  4. Redeem. When the approved applicant completes their purchase, booking, or enrollment, the approval is consumed against that offering — it was a ticket for one door, not a skeleton key.

Free offerings skip step 3’s checkout: if what they applied for costs nothing (a free package, for instance), approval grants it immediately — there’s nothing left to pay for, so the approval and the grant are one motion.

No side doors

A gate that only guards the front button isn’t a gate, so the enforcement is everywhere the offering can be reached:

  • Direct checkout links honor the gate. The linkable course-checkout URLs (the ones the Courses plugin’s enroll buttons use) check the application state before any Stripe session is created — a shared or bookmarked link can’t skip the application. (Closed in 1.62.0; earlier builds gated only the visible buttons.)
  • Gifting refuses gated offerings. Buying a gated package for someone else would hand access to a person who never applied, so purchase-for is declined on gated packages.
  • Guests can’t redeem. Approval is tied to an account; a logged-out visitor is always at the Apply step.
  • REST says no politely. The underlying API endpoints return a proper denial for non-approved users — the gate isn’t just cosmetic UI.

Working with Courses

If a Gather Grove Courses course is application-gated (a certification program, say), the same application follows the applicant across plugins: the course’s enroll buttons answer Apply until approval, and the checkout rail described above asks Courses’ gate before taking payment. One application, one decision, enforced on both sides. See the Courses documentation for the course-side setup.

Good to know

  • Reminders are built in. Pending applications older than a day get a daily nudge to the owner, so nothing goes stale in a busy inbox.
  • Decisions are final per application, not per person. A declined applicant can be invited to apply again — the duplicate guard blocks concurrent applications, not a fresh start.
  • The application page is yours. It’s a normal page with a Forms shortcode on it — style it, add testimonials, set expectations. The gate only needs its URL.

Applies to Gather Grove Booking v1.278.2. Last synced November 11, 2026.