> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v8/getting-started/how-to-login-from-lean-client.md).
# How to Login from Lean Client
Once you have created the repository and configured the server, the next step is to login using your Astera account credentials.
You will not be able to design any dataflows or workflows on the Lean client if you haven’t logged in to your Astera account. The options will be disabled.
## **Log in to your user account**
1. Go to *Server > Configure > Step 2: Login as admin*.
2. This will direct you to a login screen where you can provide your user credentials.
If you are using Astera 8 for the first time, you can login using the default credentials as follows: *Username: admin* *Password: Admin123*
After you log in, you will see that the options in the Astera Lean Client are enabled.
You will not see options to create a new dataflow, workflow, or any project. For those options to appear, you’ll have to enter your license.
## **How to automati****cally reconnect on client startup**
If you don’t want Astera to show you the server connection screen every time you run the client application, you can skip that by modifying the settings.
To do that go to *Tools > Options > Client Startup* and select the *Auto Connect to Server* option. On enabling the option, Astera will store the server details you entered previously and will use those details to automatically reconnect to the server every time you run the application.
The next step after logging in is to unlock Astera using the License key.
---
# 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://documentation.astera.com/astera-data-stack-v8/getting-started/how-to-login-from-lean-client.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.
