> 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/frequently-asked-questions-faq.md). # Frequently Asked Questions (FAQ) #### Q: I signed up as a mentor. Why can't I access mentor features yet? Creating a mentor account is only the first step. To access mentor features such as **Sessions**, **Task Requests**, **Mentees**, and **Manage Events**, you must submit a mentor application and wait for it to be approved by an administrator. See **Mentor Verification** for more information. #### Q: How long does mentor verification take? The review time depends on the number of applications being processed. Your application status will be updated once it has been reviewed. If your application remains pending for an unusually long time, contact the support team. #### Q: My mentor application wasn't approved. Can I apply again? Yes. If your application is not approved, review the feedback provided, make the necessary improvements, and submit a new application. #### Q: Why can't I create a session even after becoming a verified mentor? Session creation requires the appropriate **Interest Group (IG)** assignment. If you do not have an assigned Interest Group, you will not be able to create sessions. Contact your administrator if you believe you should have access. #### Q: Can I create recurring or weekly sessions? No. Recurring sessions are not currently supported. Each session must be created individually. #### Q: How do learners join my sessions? Learners can join your sessions in two ways: * By sending you a **session request**, which you can review and approve. * By joining a scheduled session using its **Session ID**. #### Q: Who appears in my Mentees list? Mentees can appear in your list in two ways: * They are assigned to you by a **Campus Lead in the case of a Campus Mentor Scope.** * A learner who requests a session becomes your mentee once you approve and schedule that session request. #### Q: What happens to the tasks I submit? Submitted tasks appear under **Pending** until they are reviewed by a Think Tank. Once approved, they become available to learners. If rejected, you can update the task and submit it again. #### Q: Can I save an event without publishing it? Yes. During the final step of event creation, you can choose **Save as Draft**. Draft events remain in the **Drafts** section until you are ready to publish them. #### Q: Can I delete my account from the dashboard? No. Account deletion is not currently available through the dashboard. Please contact the support team if you need assistance. #### Q: Can I use the dashboard on a mobile device? Yes. The dashboard can be accessed using a mobile web browser. However, some features are easier to use on a desktop or larger screen. --- # 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/frequently-asked-questions-faq.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.