> 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/ocs-inventory-v3-extensions/overview/introduction.md).

# Introduction

Extensions are optional modules that add new features to OCS Inventory without modifying its core. They let you extend the inventory, the automation engine and the web console with capabilities that are specific to your environment, such as integrating with a third-party platform (hypervisor, ticketing system, etc.) while keeping the base application clean and upgradable.

{% hint style="info" %}
Looking for how to install, enable, or remove an extension from the command line ? See the [Managing Extensions](/ocs-inventory-v3-extensions/overview/managing-extensions.md) page.
{% endhint %}

### Key concepts

The extension system follows three principles:

* **Isolation**: Each extension has a self-contained folder and manifest. It never modifies core application code.
* **Extension points**: Extensions use APIs, automation hooks, menu entries, etc. They do not alter existing behavior.

### Extension components

An extension can include only a backend component, or both a backend and a frontend component. Deploy and enable them separately.

* **Backend module**: Provides data models, API endpoints, and management commands. It can enrich automation rules with additional data.
* **Frontend module**: Adds console pages, menu entries, and interface components.

### Finding extensions

Extensions are currently listed in the [OCSInventory-rework-extensions](https://github.com/OCSInventory-NG/OCSInventory-rework-extensions) GitHub repository. A dedicated, more user-friendly platform will be introduced soon.

### Building extensions

All extensions maintained for OCS Inventory are available in a dedicated [Git repository](https://github.com/OCSInventory-NG/OCSInventory-rework-extensions). Developers looking to build their own extension can use it as a reference and starting point.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.ocsinventory-ng.org/ocs-inventory-v3-extensions/overview/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.