This page will show detailed information for a single package in your environment and allows you to manage its assignment to users and updates.
This page looks like the [Package Store Details](/app-management/packages/package-store/package-store-details.md) page but gives details about a package that is already imported into your environment. It does not reflect the generic package 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 to be managed via RealmJoin Portal at this point. This guide will focus on **Managed** and **Basic** packages from the package store as these are best supported currently.
## Package Properties
### Name and Core properties
Every package detail page will show an overview of the core properties like the package's **Display Name**, **Description** and **Package ID** ("Unique RJ ID") on the left side of the screen. This part will not scroll and be always visible in any tab.
You can use the edit button next to the package's name to give a package a custom display name relevant to your users. For packages hosted in Intune, this will also rename the package's display name in Intune. This will not break the relationship with the [package store entry](/app-management/packages/package-store/package-store-details.md) for packages sourced from the [package store](/app-management/packages/package-store.md).
### Status Fields
Also displayed on the left side of the screen are four status fields for a package, displayed as tags below the package name and publisher name.
These fields are binary - they are set to one of two possible values. The text of each field changes accordingly. Some of the fields are also color-coded for easier glanceability.
* **Maintained / Unmaintained:** RealmJoin will provide new versions / updates of maintained packages on a regular basis.\
Automatic package management can be applied to keep the software delivered by these packages permanently up-to-date in your environment.
* **Generic / Custom:** Generic packages are available to all customers / environments. Custom packages are not globally available to all customers. In most cases this is a custom software package created specifically for your environment.
* **Billable / Non-Billable:** Provisioning of this package will count towards your package usage quota - if you have one. Currently all publicly available packages are billable.
* **Free to Use / Needs License:** Does this software need a commercial license to be used?
* **Intunemanaged / Intuneunmanaged:** These tags denote packages, that are offered via Intune.
* **Intunemanaged**: Managed and Basic packages from the package store, delivered via Intune
* **Intuneunmanaged**: Unmanaged packages in Intune (not from the package store)
## Tabs
The right side of the screen shows the contents of the current tab.
The following tabs are available:
### Overview
Overview tab
#### Title, Description and other Info
This tab will show the long description, license and technical help information of a package.
#### Assignments and Deployment Status
Use these tables to assign additional groups and check the deployment status of apps for devices and/or users.
#### Usage
{% hint style="warning" %}
The Usage function 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. Clicking on the numbers under Client Count or User Count will show the device/users using the respective version of the package.
### History
The package's history shows when the package has been updated in RealmJoin's repository.
History tab
There are two types of changes tracked in Changelog.
 Changes to the instance of the package in your environment, specifically in Intune. E.g. publishing a newer version of the package to your users.
 Changes to package store entry.
---
# 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.realmjoin.com/app-management/packages/package-details.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.