> For the complete documentation index, see [llms.txt](https://docs.dailybiz.com/index/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dailybiz.com/index/gestion-commerciale-bis/fichiers/chantiers/creation.md).

# creation

Pour créer de façon optimale votre chantier et surtout de façon à pouvoir exploiter les données dans vos éditions, il est important de paramétrer les types de chantiers avant de commencer à enregistrer votre chantier.

En effet, lorsque vous paramétrez le type de chantier vous pouvez cibler vos éditions sur les types de chantiers en indiquant ce champ comme filtre.

1. Cliquez sur ![](https://297857182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ9LMIGmeG0qrLUTeglcC%2Fuploads%2Fgit-blob-c76722282ead30f95218c889cbdabe2c3c249076%2Fimage%20\(116\).png?alt=media) ou **\<INSER>**.
2. Renseignez les champs.
3. Cliquez sur ![](https://297857182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ9LMIGmeG0qrLUTeglcC%2Fuploads%2Fgit-blob-8e6d5c1cfde04f6c18ae68889b8a104990e7207a%2Fimage%20\(132\).png?alt=media) ou **\<ENTREE>**.

{% hint style="info" %}
Les champs "Code client" et le "Code chantier" ne sont pas modifiables.
{% endhint %}

4\. Sélectionnez le type de chantier

Vous pourrez ensuite l'utiliser pour filtrer des informations via des éditions ciblées sur le type de chantier.


---

# 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.dailybiz.com/index/gestion-commerciale-bis/fichiers/chantiers/creation.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.