# Inbox In the ***Inbox*** tab, you can access the automated submissions of instances that have been assigned to your user. Unlike submissions, in this case, you do not need to select a specific form to view its instances; instead, you will receive all submissions that meet these conditions. For this reason, the ***Inbox*** also functions as a history of received cases, whether they are answered or pending a response.

As in the ***Submissions*** screen, the buttons in the upper left corner allow you to sort and filter the forms based on their data, with the ability to apply multiple filters simultaneously. The filters for the ***Inbox*** are predefined, and it is not possible to add new options using ***tags***.

Let’s take a closer look at each of the data points displayed on this screen. ## Form This refers to the name of the template defined in the ***Name*** field of the form definition we reviewed in the previous section.

## Description This is the title of the form, established through the ***Title*** attribute in the ***Build*** application. As we saw earlier, it can be either a fixed text or a dynamic one that updates based on the data entered in a specific field. ## Stage This refers to the ***stage*** a form is in within a workflow, meaning a sequence of steps that must be completed in order, each consisting of a form. As the user progresses through the process, and if the subsequent ***stages*** are assigned to the same ***manager***, new rows will be generated to display each active stage. ## Creation Date and Last Saved These data points refer, respectively, to the date and time when the form instance was created and the date and time when changes were last saved. Draft forms may display the message "Never saved" if they have not yet been processed. ## Actions The ***Open*** option allows you to re-enter the form, whether it is a submission or a draft instance. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.rpaconnect.io/en-us/interaction-channels/instance-management-in-teams-and-the-portal/interface-and-common-functions/inbox.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.