> 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/en/getting-started/build-template.md).

# Build a template

Set up your first template using an example with Word or Google Docs.

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

We are going to go through **3 simple steps** to achieve this:

* Creating the basic configuration in Salesforce
* Designing the document in Word
* Uploading the template to Salesforce to make it available to users

{% hint style="info" %}
**Prerequisites**

* Have completed the full installation of the Gonexa package
* Have basic knowledge of Microsoft Word or Google Docs
* Have updated your application to a recent version
  {% endhint %}

## In this section

* [Configure a document template in Salesforce](/doc/en/getting-started/build-template/configure-document-template-in-salesforce.md)
* [Design the template in Word](/doc/en/getting-started/build-template/design-template-in-word.md)
* [Upload the document template](/doc/en/getting-started/build-template/upload-document-template.md)
* [Filter template visibility](/doc/en/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/en/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.