> 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-store.md). # Package Store The RealmJoin Package Store is a maintained library of ready-to-use packages deployable via RealmJoin Client or Intune. Browse, filter and inspect packages before subscribing. {% embed url="" %}

Package Store with featured apps, type and OS filters — The RealmJoin Package Store

The Package Store lists all packages your tenant can subscribe to: the generic packages RealmJoin provides for all customers, plus the custom and organic packages built for your organization. Each package can be deployed via the RealmJoin Agent or Intune. ## Browse the store ### Filters Two filter groups narrow down the list. Each shows one option at a time.

**Package type** (see [Package kinds](/application-management/packages.md#package-kinds)): * **Generic** (default) - Packages available to all customers. * **Custom** - Packages built specifically for your organization. * **Organic** - Packages built automatically from your uploaded `.zip` files. * **Unlisted** - Only shown to tenant administrators. Lists your custom and organic packages that are not listed in the store, see [Listing and unlisting packages](#listing-and-unlisting-packages). **Operating system:** * **Windows** (default) * **MacOS** - macOS packages can only be deployed via Intune. * **Android** - Only shown if Android app deployment is activated for your tenant. Android apps are not part of the RealmJoin catalogue; they are added from Managed Google Play by pasting a Google Play link. See [Android Apps (Managed Google Play)](/application-management/packages/android-apps-managed-google-play.md). ### Search The search bar above the list searches by: * **Display name** - e.g. "7-Zip" * **Category** - e.g. "Tools" or "Office". Categories are shown as tags on each package. * **Description** - e.g. "free and open-source file archiver" * **Package ID** - e.g. "generic-7zip". The ID is matched from its start. * **Unique TVM ID** - The software's ID in the Microsoft Defender software inventory, matched from its start. The results update as you type. The placeholder shows how many packages your tenant can access; on a [limited catalogue](/application-management/packages.md#full-and-limited-catalogue) it shows the number of free packages next to the total. ## Package Store details

Clicking a package opens its store entry. The store entry describes the package as RealmJoin provides it. Once you subscribe, your tenant's instance has its own [details page](/application-management/packages/package-details.md). ### Package properties The left side of the page always shows the core properties of the package: * **Display name**, **publisher** and **description** * The [package badges](/application-management/packages.md#package-badges), such as *Generic* and *Maintained* * **Package ID** ("Unique RJ ID"), e.g. `generic-7zip` * **Platform**, **package type** (e.g. Choco or Craft for Windows, PKG or DMG for macOS) and **architectures** * **Download size** and **install size** * **Version**, **last update** and the update comment * **Unique TVM ID** - If available, a link to the software's entry in the [Microsoft Defender software inventory (TVM)](https://security.microsoft.com/software-inventory/applications). There you can check for known security issues and outdated versions of this software in your organization. An appropriate license from Microsoft is needed to access TVM. * **In RealmJoin as** / **In Intune as** - If you already subscribed to the package, a link to your subscription in [Package Management](/application-management/packages/package-management.md). ![Available Version vs Provisioned Package](https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2F14DdOmrQq6WO6T8aQEie%2Fimage.png?alt=media\&token=57bb0071-b406-4505-9dad-450e15a10be0) ### Overview tab

The Overview tab is split into these sections: * **Readme** - The long description of the package. * **Subscribe** - The buttons to subscribe to the package, see [Subscribing to a Package](/application-management/packages/package-store/package-store-details.md). * **Technical Help** - If the package provides it, the supported [arguments](/application-management/packages/package-settings.md#arguments) and other requirements. ### Versions tab The Versions tab is the package's changelog. It shows when the package has been updated in RealmJoin's repository plus a short description of changes. Each version in the changelog links to its own Package Store entry. Subscribing from such an entry provisions exactly that version, which is the only way to deploy a version older than the current one. An already subscribed package cannot be downgraded, see [Package Updates](/application-management/packages/package-updates.md#downgrades).

## Listing and unlisting packages Custom and organic packages can be unlisted, for example to keep an outdated organic package from being subscribed again. At the bottom of the left side, the store entry shows whether it is **Listed in Store** or **Not listed in Store**. Tenant administrators can switch this with **Unlist now** or **List now**.

Unlisted packages no longer appear under *Custom* or *Organic*. Tenant administrators still find them under the **Unlisted** filter and can list them again. --- # 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-store.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.