> 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-details.md).
# Package Details
The RealmJoin package details page shows a single subscribed package's properties, assignments, install status, history, automation and settings.
Package details page
The details page shows a single package in your environment. Open it by clicking a package in [Package Management](/application-management/packages/package-management.md).
It looks like the [Package Store details](/application-management/packages/package-store.md#package-store-details) page, but describes your tenant's instance of the package rather than the generic store entry.
## Package types
This page can display any package that is understood by RealmJoin Portal, this includes
* **Managed** and **Basic** packages from the Package Store
* **Unmanaged** packages in Intune (not from the Package Store)
* **RealmJoin Classic** "Choco" and "Craft" packages
Different types of packages have different levels of support in the RealmJoin Portal. This guide focuses on **Managed** and **Basic** packages from the Package Store.
## Package properties
The left side of the page shows the core properties of the package and stays visible on every tab:
* **Display name**, **publisher** and **description**
* The [package badges](/application-management/packages.md#package-badges), such as *Generic* and *Maintained*, plus the deployment method and subscription type, e.g. *RealmJoinManaged*. Badges are only shown for packages from the Package Store.
* **Package ID** ("Unique RJ ID")
* **Version** and, during a [preview](/application-management/packages/package-updates.md#staged-updates-with-preview), the preview version, plus the latest version in the Package Store
* **Package type**, **architectures**, **download size** and **install size**
* **Unique TVM ID**, **categories** and **platform**
The actions menu at the bottom of the left side contains **Delete**, which removes the package from your tenant. It does not remove the package from the store or uninstall existing deployments.
### Display name
Use the edit button next to the package's name to give it a custom display name relevant to your users. For packages hosted in Intune, this also renames the app in Intune. The package stays linked to its [Package Store entry](/application-management/packages/package-store.md).
### Short description
For packages deployed via the RealmJoin Agent, you can also overwrite the package's **Short Description**, which is the text users see for the package in the [App Catalog](/realmjoin-agent/client-menu/self-service-portal.md#app-catalog-tab). The description shipped with the package is written from a packaging perspective and often explains its technical background. A custom description lets you tell users what the package means for them, e.g. *"Connects the printer on the 2nd floor of office building 5"* for a printer mapping package.
Editing the short description of an existing package
* Use the edit button next to **Description** to open the editor. The package's own description is shown below the text field for reference.
* A custom description can be up to 1000 characters long.
* While a custom description is set, the package shows a **Customized** badge next to **Description**, and the App Catalog shows your text instead of the package's description.
* Use **Reset to package default** (or save an empty text) to go back to the package's description. Saving the unchanged package description does not create a custom description, so the package keeps following future description changes of the package.
* The custom description applies to your tenant only and is kept when a managed package is updated to a new version. The package's long description is not affected.
## Tabs
The right side of the page shows the following tabs:
* [**Overview**](#overview) - Description, updates, assignments, install status and usage.
* [**History**](#history) - Changes to the package in your environment and in the store.
* **Automation** - Managed packages only. Automatic rollout of new store versions, see [Automation](/application-management/packages/package-updates.md#automation).
* **Config** - Technical Application Owners, arguments and expert settings, see [Package Settings](/application-management/packages/package-settings.md).
Android apps only have the Overview tab.
### Overview
Overview tab
The Overview tab is split into sections, listed in the sidebar on the right:
* **Readme** - The long description of the package.
* **Update** - Shown when the Package Store offers a newer version. See [Update a package manually](/application-management/packages/package-updates.md#update-a-package-manually).
* **Assignments** - The groups, users and devices the package is assigned to. See [Package Assignments](/application-management/packages/package-deployment.md).
* **Install status** - How many devices have the package installed, failed to install it or have another version, with a breakdown of the exit codes (RealmJoin) or Intune error codes (Intune), see below.
* **Dependent Packages** - The packages entered in this package's [*Depends on*](/application-management/packages/package-settings.md#dependencies-and-installation-order) setting that exist in your tenant, each linked to its package page. Shown only if at least one entry matches.
* **Technical Help** - If the package provides it, the supported [arguments](/application-management/packages/package-settings.md#arguments) and other requirements.
* **Vulnerabilities** - Known security vulnerabilities of the software, if available.
* **Usage** - The spread of versions across your devices, see below.
For Intune packages, the tab additionally shows the **Device status** and **User status** reported by Intune, separately for the main and the preview app.
#### Install status
For RealmJoin packages, the section is based on the data reported by the RealmJoin Agent and shows the number of devices with the package installed, failed or in another version, plus the exit codes of failed installations.
For Intune packages, the section is based on the Intune install status and shows when it was collected. It lists the number of devices and users per state (**Installed**, **Failed**, **Pending**, **Not installed**, **Not applicable**) and a table of the Intune error codes of failed installations with their description and the number of affected devices. Each error code links to its explanation. The **Device status** list below shows the state per device and user.
Install status and device status of an Intune package
#### Usage
{% hint style="warning" %}
The Usage section requires the RealmJoin Agent to properly populate data.
{% endhint %}
Use the usage table to determine the spread of versions deployed across your device fleet as well as your license count. Click the numbers under **Device Count** or **User Count** to see the devices or users using the respective version.
### History
The History tab shows when the package has been changed.
History tab
Two types of changes are tracked:
 Changes to the instance of the package in your environment, e.g. publishing a newer version of the package to your users.
 Changes to the Package Store entry.
---
# 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-details.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.
