> 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/design-template-in-word.md).

# Design the template in Word

You can start from a document template you already have or directly download a Gonexa template from our library of pre-designed templates: \[Pre-designed templates]

{% hint style="warning" %}
**Tip**

You can start from a document template you already have or directly download a Gonexa template from our library of pre-designed templates: [Pre-designed templates](https://www.gonexa.fr/ressources/templates)
{% endhint %}

## Build the static part of the document

* Create the fixed part of the document, such as titles, logos, headers, footers, banners, terms and conditions, etc., using standard Word features.
* If you are adding child objects, prepare the table headers.

## Open the Assistant

* In the document template, click "Access Tags" in the Gonexa Assistant component
* If you are opening it for the first time, click "Allow" to let the Assistant connect to your Salesforce environment and synchronize the fields of your document template.

![Opening the Gonexa Assistant](https://content.gitbook.com/content/U1Chwyf7Cc7FN9BiEh0V/blobs/FDIBphAo3poPLHHg5HDz/06-05-ouverture-assistant.gif)

## Insert tags from the Assistant

{% hint style="warning" %}
**Tip**

Position the Assistant in a corner of your screen, next to your Word template, to keep it within reach.
{% endhint %}

* Click the object in the Assistant to display the available fields
* Use the search bar to filter, and type the field you are looking for directly
  * You can also click the arrows to navigate between object relationships and look for information linked to the main object by traversing the relationships
* Click the desired field: it is copied to your clipboard
* Then paste the tag into your Word template at the desired location
* Format the tag using standard Word formatting (size, color, alignment, bold...)

![Inserting tags with the Assistant](https://content.gitbook.com/content/U1Chwyf7Cc7FN9BiEh0V/blobs/Iqpp4efQrErYnAfJTTDo/07-06-utilisation-assistant-corrigee.gif)

## Save the Word file to your computer

* Make sure you save your Word template in an accessible folder so you can find it easily
* If you use Google Workspace with Google Docs, save your template in Word format (.docx)

{% hint style="danger" %}
**Warning**

File size is limited to 3 MB by Salesforce standards.

Remember to optimize your file size so that it can be uploaded, which will also improve generation time and save storage in your org.
{% endhint %}


---

# 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/design-template-in-word.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.