> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/local-governance/access/local-governance-stack/property-tax/pt-user-manual/employee-user-manual/view-employee-inbox.md).
# View Employee Inbox
**Employee Inbox** provides the option to search for applications in different states or workflow. Employees get a view of applications assigned to them for further processing.
Enter at least one or multiple parameters to refine the search for property applications. The parameters include **Application No.**, **Mobile No.**, and the **Unique Property ID**.
Click on the **Search** button to view the search results. The search results show the filtered list of property applications along with their status.
Other filters available to refine the view of applications are -
* Assigned to Me
* Assigned to All
* Locality
* Application Type
Click on the **Unique Property ID** hyperlink in the search list screen to access the details. Click on the **Clear Search** button to renew the search parameters.
---
# 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.digit.org/local-governance/access/local-governance-stack/property-tax/pt-user-manual/employee-user-manual/view-employee-inbox.md?ask=&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.
