> 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/connect/en/getting-started/configure-connect-sharepoint.md).

# Gonexa Connect basic setup

Set up Gonexa Connect for SharePoint to allow document collaboration after generation, while keeping a single reference version, synchronized with your context in Salesforce.

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

We will go through **4 steps** to achieve this:

* Setting up Files Connect
* Activating Gonexa Connect user rights
* The Salesforce setup of Files Connect
* The choice of storage location per template

## Prerequisites

{% hint style="info" %}
**BEFORE STARTING**

* Have installed and set up Gonexa Doc
* Have subscribed to Gonexa Connect.\
  *Please contact sales if necessary.*
* Have access to an admin account that can grant administrator consent for an application's authorized APIs. Contact your company's SharePoint manager to set up Gonexa Connect.
* Have a Salesforce account that has access to the SharePoint admin account
* Have a SharePoint site created
  {% endhint %}

## In this section

* [Set up Azure and SharePoint for Gonexa Connect](/connect/en/getting-started/configure-connect-sharepoint/configure-azure-and-sharepoint.md)
* [Set up Gonexa Connect in Salesforce](/connect/en/getting-started/configure-connect-sharepoint/configure-salesforce.md)
* [Choice of storage location per template](/connect/en/getting-started/configure-connect-sharepoint/storage-location-per-template.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/connect/en/getting-started/configure-connect-sharepoint.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.