> 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/mentor/getting-started/new-users.md).
# New Users
If you're new to μLearn, you'll need to create an account before you can access the Mentor Dashboard.
### Creating a μLearn Account
1. Click on Join Now in the [μLearn Website](https://mulearn.org/).
2. Click **Sign Up** at the bottom of the page.
3. On the Sign Up page, enter the following information:
* Full Name
* Email Address
* Password
* Confirm Password
4. Click **Continue** to create your account.
Alternatively, you can select **Signup with Google** to create your account using your Google account.
### Continue with Mentor Onboarding
After your account has been created, you'll be guided through the mentor onboarding process.
The onboarding includes:
1. Selecting **Mentor** as your role.
2. Select Your Organization (Optional)
3. Choosing your interests.
4. Accessing the Mentor Dashboard.
Once onboarding is complete, you can apply for mentor verification from your dashboard to unlock mentor-specific features.
---
# 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/mentor/getting-started/new-users.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.
