> 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/faq/faq-pour-le-parametrage.md).

# FAQ for settings

List of questions below, click on them to see the answer.

* [Why don't the discounts set in the product appear online?](https://docs.yoplanning.support/en/faq/faq-pour-le-parametrage/pourquoi-les-reductions-parametrees-dans-le-produit-napparaissent-pas-en-ligne.md)
* [Why are products not displayed in the Potential Planning?](https://docs.yoplanning.support/en/faq/faq-pour-le-parametrage/resolution-du-probleme-des-produits-non-affiches-dans-le-planning-potentiel-sur-yoplanning.pro.md)
* [How can I ensure that Yoplanning only suggests instructors with the required skills?](https://docs.yoplanning.support/en/faq/faq-pour-le-parametrage/affecter-les-moniteurs-selon-leurs-competences.md)
* [Why am I seeing non-public discounts in my booking module?](https://docs.yoplanning.support/en/faq/faq-pour-le-parametrage/comprendre-la-visibilite-des-informations-dans-le-module-de-reservation.md)
* [Is it possible to integrate the staff's mobile number into the information received by the client?](https://docs.yoplanning.support/en/faq/faq-pour-le-parametrage/faq-integration-du-numero-de-mobile-dun-staff-dans-les-e-mails-de-rappel.md)
* [Why can't I change the font in email templates?](https://docs.yoplanning.support/en/faq/faq-pour-le-parametrage/pourquoi-je-ne-peux-pas-changer-de-police-de-caractere-dans-les-template-demail.md) [Is it possible to set up the next season even though this one isn't finished?](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/pour-creer-votre-planning-pour-la-future-saison-dans-yoplanning.md)
* [Is it possible for online sales to remain active even after the service has started?](https://docs.yoplanning.support/en/faq/faq-pour-le-parametrage/faq-vente-en-ligne-apres-le-debut-de-la-prestation.md)?
* [How to create an Orchestra connectivity request?](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/channel-manager/mise-en-place-dune-connectivite-pour-les-offices-du-tourisme-equipes-de-orchestra.md)
* [How to import a client file?](https://docs.yoplanning.support/en/faq/faq-pour-le-parametrage/importer-un-fichier-client-dans-yoplanning.md)
* [How to create an engineering connectivity request?](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/channel-manager/mise-en-place-dune-connectivite-pour-les-offices-du-tourisme-equipes-de-ingenie.md)
* [Pay in 3 installments with no fees](https://docs.yoplanning.support/en/faq/faq-pour-le-parametrage/paiement-en-3-fois-sans-frais-avec-klarna-via-stripe.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.yoplanning.support/en/faq/faq-pour-le-parametrage.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.
