> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/overview/release-notes/october-2026.md).

# October 2026

### October 12, 2026

#### Challenges

* Improved the [challenge settings page](https://docs.perkville.com/features/settings/challenges.md) with search by name or ID, filters for status, type, location, and dates, and additional sorting options. Deactivated challenges can now be viewed with read-only activity and reward details.
* Added a **Disable challenge emails** setting for individual challenges. This stops invitation, progress update, and completion emails, including manual invitations, without preventing customers from joining, making progress, or receiving rewards. Existing challenges continue sending emails unless this setting is enabled. Email-disabled challenges no longer take priority over normal loyalty program invitations.
* Added **Challenge history** for administrators with access to all locations. Review changes to settings, eligibility, progress activities, rewards, launches, and deactivations, with filters for challenge ID, staff member, change type, and dates. History records changes going forward; earlier changes are not backfilled.

#### Customer details

* Businesses using the native ABC Financial integration can now see connected member records on customer details, including home club ID, member ID, membership type, agreement number, statuses, and external last-modified date. Records are limited to the business's ABC clubs and the staff member's permitted locations.
* Added the referral submitter's name and email to the customer's referrals tab, making it easier to see who submitted each referral.

#### Loyalty program

* Added clearly labeled **Perk ID** values and copy buttons to the [loyalty program settings](https://docs.perkville.com/features/settings/loyalty-program.md) list and perk edit pages.
* Inactive locations are now excluded from perk integration displays and their location counts.
* Fixed [birthday points](https://docs.perkville.com/features/earning-rules/birthday.md) for customers born on February 29 so they receive their birthday award on March 1 in non-leap years.

#### API

* Expanded `/v2/locations/` filtering to support registered external location IDs and the optional `external_system_id` filter, including exact and `__in` matches. When no system is specified, matches across external systems are returned with legacy matches first. The `external_location_id` response field continues to contain the legacy ID.
* Added `disable_emails` to challenge API responses so integrations can see whether a challenge's emails are disabled.

### October 26, 2026

#### Memberships

* Added [Membership types](https://docs.perkville.com/features/settings/memberships/types.md) under **Settings → Memberships → Types**. Businesses using membership features can view and filter membership types by name or system ID, with counts of active, inactive, and unknown membership records.

#### Loyalty program

* Updated the [join bonus](https://docs.perkville.com/features/earning-rules/join.md) form with an editable title and consistent reward fields for restricted and unrestricted bonuses. Businesses using membership features can now select existing membership types instead of entering names manually. Restrictions apply to the selected membership names across all systems.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perkville.com/overview/release-notes/october-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
