> For the complete documentation index, see [llms.txt](https://support.who-umc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.who-umc.org/vigiflow-ereporting-for-industry/vua/selecting-sender-organisation.md).
# Selecting sender organisation
Your account may include multiple organisation profiles if you represent several MAHs or CROs, or report to more than one NRA through VigiFlow eReporting for Industry.
### When representing different sender organisations
* Log in to VigiFlow eReporting for Industry.
* If your account includes multiple organisation profiles, you will be taken to the **Select organisation** screen.
* Select the organisation you will report for. You will then be directed to the **Main menu** and the **active sender organisation** is displayed in the top-left corner of the screen.
### When sending to different NRAs
* Access to VigiFlow eReporting for Industry is granted and managed separately by each NRA.
* If your account has been added by more than one NRA, you will see the **Select organisation** screen when logging in.
* Select the NRA you intend to report to. You will then be directed to the **Main menu** and the **country code** of the currently active sender organisation appears in the top-left corner of the screen.
### Switching organisation
* Open the **User menu** in the top-right corner.
* Select **Switch organisation** and choose the new sender organisation you wish to represent.
---
# 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://support.who-umc.org/vigiflow-ereporting-for-industry/vua/selecting-sender-organisation.md?ask=&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.
