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

# Configuring software packages

This section discusses configuring and managing software packages in VHQ.

<details>

<summary>Keywords</summary>

Also called: download library. Search terms: package fields, package management.

</details>

## What is the Download Library?

**Download library** is a central repository of all the software packages configured on VHQ. You can manage software packages from *Download Library*.

## Download Library field reference

| Field               | Description                                                             |
| ------------------- | ----------------------------------------------------------------------- |
| Package Name        | Package name of the device.                                             |
| Models              | Device model name.                                                      |
| File                | The file in the package.                                                |
| File Size (KB)      | Maximum size of the file.                                               |
| Package Type        | Package type (bundle, application, service pack).                       |
| File Version        | File version.                                                           |
| Package Category    | Package category.                                                       |
| Component           | Package component — payment device, tablet, or payment device & tablet. |
| Post Install Action | Any action to be performed after installation.                          |
| Tags                | Tags.                                                                   |
| Automatic Download  | Whether automatic download is allowed.                                  |
| Uploaded By         | Name of the uploader.                                                   |
| Uploaded On         | Date and time of the upload.                                            |
| Applications        | Applications in the package. Click **View** to see them.                |

## Related topics

* [Adding packages](/support-us/verifone-hq/vhq-software-management/configuring-software-packages/adding-packages.md)
* [Editing packages](/support-us/verifone-hq/vhq-software-management/configuring-software-packages/editing-packages.md)
* [Deleting packages](/support-us/verifone-hq/vhq-software-management/configuring-software-packages/deleting-packages.md)
* [Schedule downloads](/support-us/verifone-hq/vhq-software-management/configuring-software-packages/schedule-downloads.md)


---

# 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.verifone.com/support-us/verifone-hq/vhq-software-management/configuring-software-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.