> 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/mentor-workspace.md). # Mentor Workspace #### Purpose The **Mentor Workspace** is where mentors manage their mentoring activities. From here, you can create and manage sessions, review task submissions, view your mentees, and organize community events. #### What's Included The Mentor Workspace consists of the following sections: * **Sessions** – Create, schedule, and manage mentoring sessions, review learner requests, and view upcoming sessions. * **Task Requests** – Submit community tasks for review and track their approval status. * **Mentees** – View learners assigned to you or those who become your mentees through approved session requests. * **Manage Events** – Create, edit, and manage community events, save drafts, and track event approval status. #### Access The Mentor Workspace becomes available after your mentor application has been approved. Some features, such as session creation, may require additional permissions or an assigned Interest Group. #### Related Pages * Sessions * Task Requests * Mentees * Manage Events --- # 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/mentor-workspace.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.