> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/information-de-mise-a-jour/rapport-de-maj-2025/mise-a-jour-yoplanning-juin-2025.md).

# Mise à jour Yoplanning - Juin 2025

This month, Yoplanning is getting a host of new features, UX/UI improvements, and essential bug fixes for even smoother management of your activities. Here's a summary!

***

### ✅ New products

#### 🧠 AI for team creation

* When **creating a new team**, you can activate an **AI option** to automatically pre-fill information from the **client's website** (email, phone, address, social networks...).
* AI also attempts to **automatically create products** with name, description, price, min/max participants and category.
* This option is offered during registration, or via the `Create a team` menu.

#### 🧾 Promotions and tags management

* It is now possible to **link a session tag to a promo code** to target your promotions more precisely.

#### 📦 New data type: checkbox

* A new type of custom field is available in extra data: **checkbox** ✅

#### 💸 Billing per team

* Added the option to **export the fees** of a team, useful for internal billing.

#### 📚 Customizable words

* In the products, you can **replace the word "Participant"** with a custom label (e.g., "Pilot", "Boat", etc.).
* Useful for products with **price per session**.

***

### 🛠️ Fixes

#### 💳 Payments and orders

* Fixed bugs when purchasing gift vouchers if the configuration has been removed.

#### 📅 Planning

* Fixed a display bug affecting the **horizontal scrollbar**.
* Correction of **partial unavailability**: they take into account the active team.
* Improved **drag & drop** functionality for sessions (auto-scroll restored).
* Bug fixed regarding access to empty or unavailable AI planning.

#### 🧾 Interface & UX

* **Filter changes:** Red crosses replaced with the "Clear" link.
* In the **scheduling filters**, the "OK" button becomes "Save".
* The **staff** field in the mobile popup is simplified.

#### 👤 Users & API

* Fixed an API crash related to **anonymous staff**.
* Removal of the default admin role on **anonymous staff**.
* Fixed display issues in dropdowns (overly long texts were cut off).
* Fixed API: Crash on `get members` corrected.

***

### 🔄 Modifications

#### 🧾 Internal Billing

* Overhaul of the internal billing system: payments are now made via **Stripe (link)** or **GoCardless (direct debit)**.

#### 📱 Mobile accessibility & session list

* The **session list** (`session-list`) is now accessible to everyone.
* Allows for quick viewing of **participants, resources, sessions**, even for supervisors.

#### 🎨 Design & Display

* Color palette for sessions and resources modified (more pastel).
* UI improvement on **manage-participants** and **manage-resources** (especially on mobile).
* The chatbot's "Exit" button has been moved to the left for a standard display.

***

For any questions or assistance, our support team is available at <support@yoplanning.com>

See you soon for the next improvements 🚀


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.yoplanning.support/en/information-de-mise-a-jour/rapport-de-maj-2025/mise-a-jour-yoplanning-juin-2025.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.