> 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/app/using-the-app/link-users/unvalidated-app-account.md).

# Rattacher un utilisateur quand le compte App n'est pas validé

Un compte App non validé est un compte pour lequel l'environnement de production n'a pas encore été connecté et approuvé par Gonexa.

## Connexion à un environnement déjà rattaché

Si un utilisateur tente de connecter un environnement Salesforce déjà rattaché à un autre compte App, deux options s'offrent à lui :

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

Il est possible de connecter des sandboxs sur un compte App non validé, avant de connecter la production.
{% endhint %}

* Faire une demande de rattachement pour rejoindre le compte App existant
* Créer un ticket de support Gonexa afin de demander que son compte devienne le compte principal

![Popup environnement rattaché à un compte App non validé](https://2755037948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMvpmte999umph55KoFMZ%2Fuploads%2FrGP9BbeD9OkF1IOXx9FZ%2Fapp-9.png?alt=media)


---

# 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/app/using-the-app/link-users/unvalidated-app-account.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.