> 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/administrator-docs/server-setup/customization/categories.md).

# Categories

Categories define how [inventory data](https://documentation.ocsinventory-ng.org/user-docs/asset-management/inventory-and-templates.md#template-inventory) is organized and displayed within an asset’s detail view. They let you customize the way templates and their sections appear when viewing asset information.

Each **category** is a group of related **inventory sections**.\
By default, OCS provides **seven predefined categories**, corresponding to the seven tabs shown in the left panel of an asset’s detail view.

Every category contains one or more **sections**, and each section is linked to a specific **template**.

<figure><img src="https://461838061-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtjrEC8kt8LJiJYFBs5CS%2Fuploads%2FjAQ2udkHZjdM9kUJDbuV%2Fimage_2026-04-22_163031453.png?alt=media&amp;token=fb291bc5-4970-4e26-b675-a97c0f9beed7" alt="Categories general view"><figcaption><p>Categories general view</p></figcaption></figure>

***

## Adding a category

Suppose your [template](https://documentation.ocsinventory-ng.org/user-docs/asset-management/inventory-and-templates.md#template-inventory) includes several sections related to virtual machines. For example, **VMware** and **Hyper-V**.&#x20;

You might want to group these under a dedicated category, such as **VMs**.

{% stepper %}
{% step %}
Navigate to **Configurations** **→ Inventory → Categories.**
{% endstep %}

{% step %}
Click **Add a new category**.
{% endstep %}

{% step %}
Complete the form.

* **Name**
* **Description**
  {% endstep %}

{% step %}
Click **Add.**
{% endstep %}
{% endstepper %}

To group the relevant sections under this new category, edit it as shown below.

## Edit a category

{% stepper %}
{% step %}
Navigate to **Configurations** **→ Inventory → Categories.**
{% endstep %}

{% step %}
Locate the category you want to edit.
{% endstep %}

{% step %}
Click the **pencil icon** in the Actions column.
{% endstep %}

{% step %}
Update the form as needed:

* **Name**
* **Description**
* **Sections**: use the drop-down list to select or deselect inventory sections to include or remove.
  {% endstep %}

{% step %}
Click **Save**.
{% 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/administrator-docs/server-setup/customization/categories.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.
