> 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/first-time-login.md).

# First time login

{% hint style="info" %}
If you already have access to **VigiFlow**, you can log in to **VigiLyze** directly from VigiFlow using the VigiLyze button, or by using your existing VigiFlow username and password.
{% endhint %}

For new VigiLyze users, follow these steps to set a password:

1. Navigate to the VigiLyze login page ([https://vigilyze.who-umc.org](https://vigilyze.who-umc.org/)) and click **Forgot your password**.
2. Enter your email address and click **Send verification code**.
3. A field is displayed requesting the verification code. Leave this window open and open your email inbox in a new tab or application.
4. You will receive an email from Uppsala Monitoring Centre containing a verification code. Enter the code in the *Verification code* field.
5. Click **Verify**.
6. Click **Continue**.
7. Create a new password.

The next time you sign in to VigiLyze, enter your email address and password.
\
After signing in, the VigiLyze landing page is displayed. You can then begin working with the data available to your organisation.

If you cannot sign in, contact the person responsible for VigiLyze administration in your organisation or contact UMC support.


---

# 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/first-time-login.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.