> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/application-management/packages/package-management.md).

# Package Management Overview

RealmJoin Package Management lists all packages across RealmJoin and Microsoft Intune to filter, search, sort, and spot pending updates and failed installs.

Package Management (*Packages* in the portal navigation) shows all packages that currently exist in your environment across RealmJoin and Microsoft Intune.

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2Fgit-blob-00406362e03c9e76b1b2a852b7568aedd2234fdc%2Fpkg-package-list.png?alt=media" alt="Package Management list with filters and columns"><figcaption><p>Package Management list</p></figcaption></figure>

Clicking on the name of a package opens the package's [details page](https://docs.realmjoin.com/application-management/packages/package-details.md).

## Filters

**Platform** - Limit the list to **Win**, **Mac** or **Android** packages, or show **Any**.

**Source:**

* **All** - All packages across RealmJoin and Intune, including Intune apps that were not created by RealmJoin, such as mobile apps and Microsoft Store apps.
* **RealmJoin** - Only packages deployed via the RealmJoin Agent.
* **Intune** - All Intune apps, whether created by RealmJoin or not.
* **Supported** (default) - Only packages handled by RealmJoin: RealmJoin Agent packages and the Intune apps created by RealmJoin.

**Toggles:**

* **Updates only** - Only packages from the Package Store for which a newer version exists in the store.
* **Automation only** - Only packages from the Package Store with [update automation](https://docs.realmjoin.com/application-management/packages/package-updates.md#automation) configured.
* **Failures only** - Only packages with failed installations.

The toggles become available once the package list has been fully loaded.

## Columns

* **Name** - The display name of the package.
* **Main** - The version currently deployed to the Main group.
* **Preview** - The version currently in [preview](https://docs.realmjoin.com/application-management/packages/package-updates.md#staged-updates-with-preview), if any.
* **Update** - The latest version available in the Package Store, if it is newer.
* **Automation** - The [automation](https://docs.realmjoin.com/application-management/packages/package-updates.md#automation) state. Shows when the next automated update is due, or **ASAP** if it is due now. Without a pending update it shows which channels are automated: **fully**, **main only** or **preview only**.
* **Install** - A bar showing how many devices have the package installed, not installed, pending or failed.
* **Coordinator** - How the package is deployed: **RealmJoin (managed)**, **RealmJoin (basic)**, **Intune (managed)**, **Intune (basic)** or **Intune (unmanaged)** for Intune apps not created by RealmJoin.
* **Platform** - The platform of the package.

## Search, sort and export

The search box searches the list by any visible field, incl. name, version and platform. The results update as you type.

Click a column header to sort by that column. Use the export button next to the search box to download the current list.


---

# 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.realmjoin.com/application-management/packages/package-management.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.
