> 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/packaging-requests/organic-packages.md).

# Organic Packages

RealmJoin organic packages build from uploaded .zip files and publish automatically to the Package Store for binary file transport.

Organic packages are used for binary file transportation with a fixed configuration, which can not be changed. Uploaded .zip files are automatically added to the list of available packages in the tenant, and secured with a strong password. The content will be extracted to *`$env:SystemDrive\Install\packagename`* during package execution. This path can not be changed. An optional antivirus scan is available.

Because of this high standardization, organic packages are built automatically and within a couple of minutes. No ticket will be created and no charge added, the package will be made available in the Package Store under the Organic tab as soon as possible without the need of involvement of the packaging factory.

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FPrKfX5ekWZDR9LBLRDfU%2Fimage.png?alt=media&amp;token=c8abfd06-1129-4d2a-9135-55717e8afc44" alt=""><figcaption><p>Organic packaging request.</p></figcaption></figure>

##

{% hint style="warning" %}
Due to their automated creation process, organic packages cannot be updated. These packages are generated and published without user input, making them unchangeable. Additionally, since no installation routine is run, logical updates are not possible. To release a new version, create a new automatic organic package and remove the outdated one from your portal.
{% endhint %}

## Unlist Organic Packages

Organic packages can be unlisted after creation, if they should not be seen by other administrators in your tenant. Simply go to the package store, select the package and press the "Unlist now" button.

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FtFRivBAx9zkWF50eGIDc%2Fimage.png?alt=media&amp;token=a4186f51-5039-448a-a1f7-022150d62358" alt=""><figcaption><p>Unlist now</p></figcaption></figure>


---

# 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/packaging-requests/organic-packages.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.