> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/guides/guides-fr/relecture-et-livraison-client.md). # Relecture et livraison client Pilotez des cycles de validation, livrez les fichiers finaux et collaborez en toute sécurité avec des clients et des freelances.
Le cycle de validation clientPartagez, commentez, résolvez, versionnez et approuvez sans quitter Shade.La boucle de révision client
Livrez les fichiers finaux à un clientLivraison sécurisée et à vos couleurs avec des collections, des liens et des contrôles de téléchargement.Remettre les fichiers finaux à un client
Travaillez avec des freelancesDonnez aux prestataires exactement l’accès nécessaire à une mission, puis retirez-le proprement à la fin.Travailler avec des freelances
--- # 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://academy.shade.inc/guides/guides-fr/relecture-et-livraison-client.md?ask=&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.