> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/organization-and-workflows/overview.md).

# Inbox

The recordings and bug reports that need you, and how to assign them.

**Inbox**, at the top of the sidebar, lists the recordings and bug reports that need you in this workspace, newest activity first. The count next to it is everything you haven't marked done.

{% embed url="<https://app.screendesk.io/recordings/0642e1a8-ba38-46af-a5d1-8d611308ac68>" %}

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2FdKFoHQJ9NPi0BceATupp%2Fdocs-window-inbox.png?alt=media" alt="The Inbox in Screendesk"><figcaption></figcaption></figure>

An item lands in your Inbox when:

* someone assigns it to you
* a customer sends a recording through your request link
* someone comments on a recording or bug report you're assigned to or follow
* someone mentions you in a comment

Each row says what happened and who did it. Opening an item marks it read. Select **Done** when you've dealt with it, or **Mark all done** to clear the whole list (you can undo it straight after). Done items move to the **Done** tab and come back to Inbox when something new happens on them.

**Workspace updates** appear above the list: a teammate accepted an invite, you were given access to a private folder, AI labels are waiting for review, and similar notices. They count toward the total until you mark them done.

## Assign a recording or bug report

Open it and, under **Assigned to**, select **Add or remove assignees**. Check one or more teammates; each change saves right away. Every assignee gets the item in their Inbox and an email.

* Assigning yourself doesn't notify you.
* Unassigning someone removes the item from their Inbox, unless they follow its comments.
* To see who owns what, use the **Assignee** filter on the **Customers** and **Team** lists.

## Follow a conversation

Writing a comment on a recording or bug report makes you follow it. To follow without commenting, select the bell at the top of its activity timeline. See [Comments and mentions](https://docs.screendesk.io/organization-and-workflows/collaboration.md).

## Email notifications

Inbox can't be turned off, but its emails can. Open **Notifications** in your account menu and use the **Recording assignments**, **Bug report assignments**, **Mentions** and **Followed conversations** switches.


---

# 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.screendesk.io/organization-and-workflows/overview.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.
