> For the complete documentation index, see [llms.txt](https://docs.mulearn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mulearn.org/how-to-use-the-platform/company/getting-started/existing-user.md).

# Existing User

If you already have a μLearn account, you can sign in using your existing credentials to access the Company Dashboard.

### Signing In

1. Open the μLearn Sign In page.
2. Enter your registered **Email Address** or µ**ID**.
3. Enter your **Password**.
4. Click **Sign In** to access your account.

Alternatively, you can:

* Select **Continue with Google** if your account is linked to Google.
* Select **Login with OTP** to sign in using a one-time password.

If you've forgotten your password, click **Forgot Password?** and follow the instructions to reset your password.

> **Note:** If you haven't previously selected the **Company** role or completed the company onboarding process, you'll be guided through the remaining setup after signing in.

### Accessing the Company Dashboard

After signing in successfully, you'll be redirected to the **Company Dashboard**. From there, you can continue managing your organization, access available features, or complete the company verification process if required.


---

# 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.mulearn.org/how-to-use-the-platform/company/getting-started/existing-user.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.