> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/release-notes/archive/2024/2024-09-30-oe-task-inbox.md).

# 2024-09-30: OE - Task Inbox

### Overview

We are happy to share that the Task Inbox that was previously accessible only by external access links, outside the Management Dashboard, is now fully integrated and available within the dashboard itself. This enhancement provides employees with a more streamlined and efficient way to access their tasks directly from the dashboard, improving overall convenience and workflow efficiency.

Employees can now easily manage all their tasks in one place, eliminating the need to rely on external links for task access. This update is part of our continuous effort to enhance user experience and productivity.

| Feature        | Benefits                                                                    |
| -------------- | --------------------------------------------------------------------------- |
| **Task Inbox** | Access all the tasks assigned to a single user within Management Dashboard. |

### Known problems

No known problems at time of release.

### Documentation and links

* [Task Inbox and Tasks](/oe-user-guides/management-dashboard/configuring-oe-tenant/task-inbox.md)


---

# 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://developer.emporix.io/release-notes/archive/2024/2024-09-30-oe-task-inbox.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.