> For the complete documentation index, see [llms.txt](https://documentation.ocsinventory-ng.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ocsinventory-ng.org/user-docs/deployment/packages-and-actions.md).

# Packages

## Packages

A package consists of one or more **Actions**, along with metadata that describes its purpose, the targeted operating systems, and other relevant details.

### Creating a Package

{% stepper %}
{% step %}
Go to **Deployment → Packages** in the top navigation menu.

You’ll see the list of existing packages if any.

<figure><img src="https://461838061-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtjrEC8kt8LJiJYFBs5CS%2Fuploads%2FjYGneGE5281qgpCos6LQ%2Fimage.png?alt=media&amp;token=03fe9d58-da37-454e-a436-329ab425de7c" alt="Package view"><figcaption><p>Package view</p></figcaption></figure>
{% endstep %}

{% step %}
Click the **Add a Package** button:

A form will appear to create your new package.
{% endstep %}

{% step %}
Fill out the package detail&#x73;**.**

* **Name**: enter a unique name for the package.
* **Description**: provide a brief description.
* **Targeted operating system**: select the OS this package is intended for.

<figure><img src="https://461838061-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtjrEC8kt8LJiJYFBs5CS%2Fuploads%2FN809FjLekxpntbuTHAAO%2Fimage.png?alt=media&amp;token=345bfd50-e785-45c0-ac1b-5709f427bed6" alt="Package creation form"><figcaption><p>Package creation form</p></figcaption></figure>
{% endstep %}

{% step %}
Click **Add** to create the package.

The page will refresh, and your new package will be displayed in the list.

The **Deployment Actions** column will show **0 by default**, indicating no actions are currently associated with the package.

{% hint style="info" %}
**Next step**: See the section on [Actions](https://documentation.ocsinventory-ng.org/user-docs/deployment/actions.md#adding-actions)
{% endhint %}
{% endstep %}
{% endstepper %}

### Edit Package metadata

{% stepper %}
{% step %}
Click the Pencil Icon.

In the **Actions** column of the Packages table, click the **pencil icon** for the package you want to edit.
{% endstep %}

{% step %}
Update the form.

* **Name**: Modify the package name if required.
* **Description**: Update the package description.
* **Targeted operating system**: Adjust the operating system if necessary.

<figure><img src="https://461838061-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtjrEC8kt8LJiJYFBs5CS%2Fuploads%2F97uIGOYN3qZ4HVtNR41s%2Fimage.png?alt=media&amp;token=424d50c4-8a89-45c2-bd4d-d87ddd1a1208" alt="Example: editing the package&#x27;s description"><figcaption><p>Example: editing the package's description</p></figcaption></figure>
{% endstep %}

{% step %}
Save your changes.

Click the **Save** button to apply your updates.
{% endstep %}
{% endstepper %}

### Removing a Package

{% stepper %}
{% step %}
Click the **Trash** icon.

In the **Actions** column of the Packages table, locate the package you want to remove and click the **trash icon**.
{% endstep %}

{% step %}
Confirm deletion.

When prompted, confirm the deletion to permanently remove the package.
{% endstep %}
{% endstepper %}


---

# 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://documentation.ocsinventory-ng.org/user-docs/deployment/packages-and-actions.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.
