> For the complete documentation index, see [llms.txt](https://docs.empe.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empe.io/develop/intro/login.md).

# Login

To access your account, follow the steps below:

1. **Access the Login Page:**
   * Open the `One-Click Deployment` application.
   * Navigate to the **Log In** page.
2. **Fill in the Login Form:**
   * Enter the following details:
     * **E-mail:** The e-mail address you used to register.
     * **Password:** Your account password.
3. **Submit the Form:**
   * Click **Log In** to access your account.

After logging in you have an authenticated session and can access your deployments from the dashboard.

***

## Forgot Your Password?

If you cannot remember your password, click the **Forgot Password?** link on the Log In page. Enter your registered e-mail address and the platform sends you a reset link. Follow the link to choose a new password, then return to the Log In page to sign in.

***

Don't have an account yet? Use the **Sign Up** link on the Log In page to create one — see [Registration](/develop/intro/registration.md) for details.

For any issues during registration or login, please contact our support team for assistance.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.empe.io/develop/intro/login.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.