> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/doc/getting-started/build-template.md).

# Construire un modèle

Configurez votre premier modèle à l'aide d'un exemple avec Word ou Google Doc.

{% embed url="<https://www.youtube.com/watch?v=WAdkUsrQCEM>" %}

Nous allons parcourir **3 étapes simples** pour y parvenir :

* Création de la configuration de base dans Salesforce
* Design dans Word du document
* Chargement du modèle dans Salesforce pour le mettre à disposition des utilisateurs

{% hint style="info" %}
**Pré-requis**

* [ ] Avoir fait l'installation complète du Package Gonexa
* [ ] Maîtriser les basics de Microsoft World ou Google Docs
* [ ] Avoir mis à jour son application sur une version récente
  {% endhint %}

## Dans cette rubrique

* [Configurer un modèle de document dans Salesforce](/doc/getting-started/build-template/configure-document-template-in-salesforce.md)
* [Designer le modèle dans Word](/doc/getting-started/build-template/design-template-in-word.md)
* [Mettre en ligne le modèle de document](/doc/getting-started/build-template/upload-document-template.md)
* [Filtrer la visibilité d'un modèle](/doc/getting-started/build-template/filter-template-visibility.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://university.gonexa.fr/doc/getting-started/build-template.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.