> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/detect-investigate-and-respond-to-threats/cortex-advanced-email-security/mailbox-inventory.md).

# Mailbox Inventory

{% hint style="info" %}

### Notice

Requires the Advanced Email Security add-on.
{% endhint %}

The Mailbox Inventory provides centralized asset visibility for all mailboxes managed under the Email Security module. Connected to the Unified Asset Inventory (UAI), this dedicated page displays all active mailboxes in a single, comprehensive table. From this view, you can use dashboard widgets to see a high-level breakdown of your assets and filter the table by specific mailbox types (such as user, room, or shared) to manage your email environment.

When you filter using either the widgets or the table, both the widgets and the table are updated.

**Mailbox Inventory widgets**

Use the widgets to get a better understanding of your email security assets.

* Type breakdown: Displays distribution across mailbox types
* Onboarded / Non-Onboarded: Shows a breakdown of how many mailboxes are actively onboarded to Email Security .

**Mailbox Inventory table**

The unified inventory table displays all discovered mailboxes where the email field isn't empty. Each row represents one mailbox record with its associated metadata (owner, type, onboarding status, etc.). Rows with an empty email field are excluded.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/detect-investigate-and-respond-to-threats/cortex-advanced-email-security/mailbox-inventory.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.