Capitan Release Notes - April 3, 2026

What's in this release

View and export booking customer question responses
Pagination on customer profile Guest Pass Usage and Shared Passes lists
Proficiency expiration based on days since document approval
Repeating events created at least one year in advance

Plus several fixes — see the end of this article.

View and export booking customer question responses

Booking customer questions (the per-booking questions configured on an Event Type) can now be included in the participant list and export. When configuring columns for an event's participant list or export, staff can now select the booking customer questions alongside the participant-level questions.

This makes it much easier to pull, for example, a single CSV that includes both each participant's allergies and the booking customer's contact info.

Continuing the pagination work from the previous release, the Guest Pass Usage and Shared Passes lists in the Memberships & Passes section of a customer's Staff Site profile now support pagination, bringing them in line with the rest of the lists in that section. This is particularly useful for organizations with members who use guest passes or shared passes frequently and need to look back through historical entries.

Proficiency expiration based on days since document approval

When configuring a proficiency, there is a new option to have the proficiency expire a set number of days after the linked document is approved, independent of the document's own expiration date. Previously, a proficiency's expiration was tied directly to the document's expiration. With this option, organizations can enforce a separate proficiency-validity window — for example, a belay test that must be re-evaluated every six months even if the underlying waiver is valid for a year.

Repeating events created at least one year in advance

Capitan automatically generates upcoming events from each repeating schedule. Previously, the system kept at least 90 days of upcoming events populated; that minimum has been extended to 366 days. Organizations that build out schedules well in advance can now see and manage their events in the Staff Site as soon as the schedule is created, without having to wait closer to the event for them to be generated. This change does not affect the customer-facing booking window, which is still controlled by each event type's existing "how far in advance can someone book this event?" setting.

Fixes

Removing a recurring code discount now actually removes it. Previously, when staff removed an automatic recurring discount from a customer's membership, the system showed a "discount removed" confirmation but the discount remained on the account, with no entry in the activity log. The discount is now actually removed and the activity log records the change.
Partial-payment receipts now itemize account credit and remaining balance. When a customer paid for a purchase using a combination of account credit and another payment method (such as a credit card), the receipt was incorrectly showing the full purchase amount as charged to the external payment method, with the account credit not itemized. Receipts now show the total purchase amount, account credit applied, and the remaining balance charged to the external payment method.
Roster member reservations update immediately when a schedule changes. When a schedule or schedule exception was changed for a roster, the schedule itself updated right away but participants were not added to the newly created events until the next scheduled sync. Roster participants are now updated immediately when the schedule changes.