> 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.md). # Getting Started Welcome to the Mentor onboarding guide. This section helps you access the μLearn platform and begin your journey as a mentor. Whether you're creating a new account or returning with an existing one, you'll find the information needed to get started. Use the appropriate guide based on your situation: ### New Users If you're new to μLearn, start here. This guide walks you through the complete onboarding process, including creating your account, selecting the Mentor role, completing the initial setup, choosing your interests, and accessing the Mentor Dashboard for the first time. You'll learn how to: * Create a new μLearn account * Choose the Mentor role during onboarding * Complete the required setup * Personalize your experience by selecting your interests * Access the Mentor Dashboard ### Existing Users Already have a μLearn account? This guide explains how to access your existing account and continue using the Mentor Dashboard. You'll learn how to: * Sign in to your μLearn account * Recover your account if you've forgotten your credentials * Access the Mentor Dashboard --- # 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.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.