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

# Task Requests

#### Purpose

Create and manage task requests that are submitted for administrative review before becoming available to learners.

#### Page Overview

The Task Requests page allows mentors to submit new tasks, monitor their approval status, and manage existing task requests. Tasks are organized into four tabs based on their current review status.

#### Features/Sections

* **All Tasks** – Displays every task request submitted by the mentor.
* **Pending** – Displays task requests awaiting review.
* **Approved** – Displays approved task requests.
* **Rejected** – Displays rejected task requests.
* **Submit Task** – Opens the task submission form.

#### Available Actions

* Submit a new task request.
* View task requests by status.
* Track the approval progress of submitted tasks.
* Review approved, pending, and rejected tasks.
* Edit task requests.
* Delete task requests.

#### Step-by-Step Workflow

**Submitting a new task**

1. Open **Management → Task Requests**.
2. Click **Submit Task**.
3. Complete the task details:
   * Task Title
   * Hashtag
   * Interest Group
   * Karma Points
   * Task Type
   * Level
   * Usage Count
   * Description
4. Click **Submit Task**.
5. The task request appears in the **Pending** tab until it is reviewed.

**Managing task requests**

1. Open the required status tab:
   * All Tasks
   * Pending
   * Approved
   * Rejected
2. Locate the required task.
3. Use the available actions to edit or delete the task when applicable.
4. Monitor the task status until the review process is completed.

#### Statuses and Their Meaning

| Status   | Description                                            |
| -------- | ------------------------------------------------------ |
| Pending  | The task has been submitted and is waiting for review. |
| Approved | The task has been reviewed and approved.               |
| Rejected | The task has been reviewed but was not approved.       |

#### Tips & Best Practices

* Provide a clear and descriptive task title.
* Write detailed instructions so learners understand the expected outcome.
* Assign Karma points appropriate to the effort required.
* Verify all task details before submitting for review.

#### Notes/Limitations

* Every submitted task undergoes a review process before approval.
* Task requests are organized into separate tabs based on their current status.
* Task Requests follows the same review workflow as Session Requests, allowing mentors to track requests throughout the approval process.

#### Related Pages

* Sessions
* 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/task-requests.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.