> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/support/user-permissions-and-administration/how-to-log-in-to-limio-for-the-first-time-and-set-up-your-password.md).

# Log In for the First Time and Set Up Password

When a new user is created in Limio, they must authenticate using temporary credentials for their first login.

## **Retrieve your temporary login details**

You will receive an email containing your temporary username and password. Temporary passwords are valid for **7 days**. If the password expires, a **tenant admin** must reset it before you can proceed.

## **Log in to the Limio app**

Open the Limio login page and enter the **username** and **temporary password** from your email.

## **Set up a new password**

You will be prompted to create a new password. As per the Limio password policy, it must meet the following requirements:

* At least **12 characters** long
* Contains **1 uppercase letter**
* Contains **1 lowercase letter**
* Contains **1 number**

Confirm your new password and submit.

## **Complete your login**

Once redirected to the login page, enter your **username** and **new password** to access Limio.


---

# 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.limio.com/support/user-permissions-and-administration/how-to-log-in-to-limio-for-the-first-time-and-set-up-your-password.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.