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

# Attach a user when the App account is validated

An App account is considered validated once the production environment has been connected and verified by the Gonexa team. This account then becomes the main account.

## Connecting to an environment that is already attached

When a user tries to connect a Salesforce environment that is already attached to another validated App account, the following process applies:

* The user enters their Salesforce credentials and clicks Log In
* The App detects that the environment is already associated with another App account
* A popup appears to inform the user of the situation
* The user can then request to be attached to this main App account

![Popup: environment attached to a validated App account](https://content.gitbook.com/content/MXHiWjspBVPRVSdBvi50/blobs/35a1MZcb8p2AbvrHBEI2/app-7.png)

## Managing attachment requests

* Attachment requests are visible on the home page of the main App account (the one validated by Gonexa).
* Users of that account can then accept or decline the request.


---

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