> 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/sessions.md).

# Sessions

#### Purpose

Create, review, schedule, and manage mentoring sessions from a single workspace.

#### Page Overview

The Sessions page allows mentors to create new sessions, manage scheduled sessions, and review session requests submitted by learners. It is organized into three tabs: **Upcoming**, **All Sessions**, and **Student Requests**.

#### Features/Sections

* **Upcoming** – Displays all scheduled upcoming mentoring sessions.
* **All Sessions** – Displays all sessions created by the mentor.
* **Student Requests** – Displays session requests submitted by learners for review.
* **New Session** – Opens the session creation dialog.
* **Session Actions** – Perform actions on scheduled sessions from the Upcoming tab.

#### Available Actions

* Create a new mentoring session.
* View upcoming sessions.
* View all created sessions.
* Review student session requests.
* Approve or reject a session request.
* Modify session details before approving a request.
* Open the meeting link for an online session.
* Copy the meeting information.
* Edit a scheduled session.
* View session participants.
* Delete a scheduled session.

#### Step-by-Step Workflow

**Creating a new session**

1. Open **Management → Sessions**.
2. Click **New Session**.
3. Enter the session details:
   * Title
   * Description
   * Interest Group
   * Start date and time
   * End date and time
   * Session mode
   * Meeting link (for online sessions)
4. Click **Create Session**.
5. The session appears under the **Upcoming** tab with the **Scheduled** status.

**Reviewing a student request**

1. Open the **Student Requests** tab.
2. Locate the request and click **Review**.
3. Select an action from the **Action** dropdown:
   * Approve Request
   * Reject Request
4. When approving, you can modify:
   * Start time
   * End time
   * Session mode
   * Meeting link
5. Click **Approve & Schedule**.
6. After approval, the session is added to the **Upcoming** tab.

#### Statuses and Their Meaning

| Status    | Description                                                              |
| --------- | ------------------------------------------------------------------------ |
| Scheduled | The session has been approved or created and is scheduled to take place. |

#### Tips & Best Practices

* Verify the session date and time before approving a learner request.
* Ensure the meeting link is valid before scheduling an online session.
* Use descriptive session titles so learners can easily identify the session topic.
* Review learner requests regularly to avoid delays in scheduling.

#### Notes/Limitations

* Session start time must be set to a future date and time. Attempting to schedule a session in the past displays an error.
* Date and time fields include a built-in date and time picker for selecting the schedule.
* Session requests can be approved with modified scheduling details before confirmation.

#### Related Pages

* Task Request
* 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/sessions.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.