> 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/august-2026.md).

# August 2026

### August 3, 2026

#### Customer-facing page settings

* Added the ability to customize the names, title tags, and more for customer-facing pages

#### Locales

* Added support for the following locales:
  * Spanish (Mexico)
  * Spanish (Spain)
  * French (France)
  * French (Canada)
  * Portuguese (Brazil)
  * Dutch

#### Accessibility

* Updated text color and size on the Business Dashboard for better readability

#### [ABC Ignite](https://docs.perkville.com/integrations/integration-reference/abc-ignite.md)

* Updated integration to populate a member's birthday in Perkville, if not already present
* Small change to more gracefully handle temporary 500 errors when completing OAuth

### August 10, 2026

#### [Locations](https://docs.perkville.com/features/settings/location-setup/locations.md)

* Added the ability to associate multiple External Location IDs to a single Perkville location

#### General

* Fixed an issue where the upper date range was not inclusive for the Points by Location report
* Fixed a misaligned checkbox when displaying agreement terms
* Rewards shown on the Levels page are now restricted to the currently selected location

### August 18, 2026

#### Accessibility

* Further readability updates on the Business Dashboard

#### [Reports](https://docs.perkville.com/features/reports.md)

* Updated documentation and links to documentation

### August 20, 2026

#### [Staff permissions](https://docs.perkville.com/features/settings/staff-members.md#staff-member-roles)

* Added the ability to customize permissions for Employee and Front Desk staff

#### Referral

* Fixed a UI issue with the location dropdown when displaying long location names

### August 25, 2026

#### Vouchers

* Redesigned vouchers to better highlight redemption instructions, and generally spruce up the page
* Also updated the referral offer email to better highlight the redemption instructions

#### General

* On the [Loyalty program settings page](https://docs.perkville.com/features/settings/loyalty-program.md), added a Middle icon next to perks that are integrated to Middle
* Various bug fixes

### August 27, 2026

#### [Customers](https://docs.perkville.com/features/customers.md)

* Added the ability to search for a customer using an [External Member ID](https://docs.perkville.com/features/customers/customer-identifiers.md) from a connected system.

#### Referrals

* Added a customizable [ineligible referral offer message](https://docs.perkville.com/features/settings/advanced/referral-offer-claim-options.md) for people who cannot claim a referral offer.
* Added the **Block customers and prospects connected to your business from being referred** setting, allowing businesses to choose whether an existing Perkville business connection blocks a referral. See [Allowing past customers or members to be referred again](https://docs.perkville.com/features/referrals/configuring-your-referral-program/allowing-past-customers-or-members-to-be-referred-again.md).


---

# 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/august-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.
