> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/global-settings/user-management/users/new-user-first-login.md).
# New User First Login
## Overview
After the System Administrator creates a user's account, the user must complete the initial login process, which involves changing the password. This article walks you through the process of logging into your account for the first time.
## User First Login
{% hint style="info" %}
Before starting the login process, make sure your System Administrator has provided you with the following:
* The email address to log in to your account.
* The temporary password for your account.
{% endhint %}
{% stepper %}
{% step %}
### Login
1. Enter the login URL provided by your System Administrator in the browser.
2. Enter the **Email** used to register the user.
3. Click **Continue**.
4. Access your email account and open **Flosum: Login Verification Code**.
The email is sent from no-reply@flosum.app. Check your spam folder if you have not received the email.
5. Copy the verification code.
6. Enter the copied verification code in the **Verification Code** textbox.
7. Click **Continue**.
8. Select the tenant to log in to.
{% hint style="warning" %}
If you have multiple tenants and are unsure which tenant to select, contact your System Administrator.
{% endhint %}
8. Click **Continue**.
{% endstep %}
{% step %}
### Change Temporary Password
1. In the **Password** textbox, enter the **Temporary Password** that the System Administrator provided.
2. Click **Login**.
3. Enter a **New Password** that meets the stated password requirements.
4. Re-enter the password in the **Confirm New Password** textbox.
5. Click **Change Password**.
{% endstep %}
{% step %}
### Login with New Password
1. Enter the **Email** used to register the user.
2. Click **Continue**.
3. Access your email account and open **Flosum: Login Verification Code**.
The email is sent from no-reply@flosum.app. Check your spam folder if you have not received the email.
4. Copy the verification code.
5. Enter the copied verification code in the **Verification Code** textbox.
6. Click **Continue**.
7. Select the tenant to log in to.
{% hint style="warning" %}
If you have multiple tenants and are unsure which tenant to select, contact your System Administrator.
{% endhint %}
8. Click **Continue**.
9. In the **Password** textbox, enter the new password you created.
10. Click **Login**.
11. You have successfully logged into your new Flosum account.
{% endstep %}
{% endstepper %}
---
# 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://docs.flosum.com/global-settings/user-management/users/new-user-first-login.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.
