> 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/vigilyze/getting-started/vigilyze-interface-overview.md).
# VigiLyze interface overview
This page introduces the main areas of the VigiLyze interface and the terminology used throughout the documentation.
#### User menu
The User menu is in the upper-right corner of the screen.
From the User menu, you can access:
* Personal settings
* Organisation settings
* Other account-related options
#### Landing page
On the first page you encounter when logging into VigiLyze, you see
* Number or ongoing investiations assigned to you, and others in the organisation
* Links to VigiLyze courses
* MedDRA version date
* Information about the dataset, including when it was last updated and how often updates are performed
#### Qualitative and Quantitative views
VigiLyze provides two complementary ways of working with data:
* The **Qualitative view** focuses on report-level review and assessment.
* The **Quantitative view** focuses on aggregated drug-reaction combinations and disproportionality measures.
---
# 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/vigilyze/getting-started/vigilyze-interface-overview.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.
