> 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/quickstart-guides/for-users/console-overview.md).

# Console overview

## Console layout

The OCS console is designed to be user-friendly and straightforward. Below is an overview of its key components:

<figure><img src="https://461838061-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtjrEC8kt8LJiJYFBs5CS%2Fuploads%2FETPhvGZvYwc4jTZIWJSD%2FCapture%20d%E2%80%99%C3%A9cran%20du%202026-04-23%2009-29-48.png?alt=media&amp;token=c37330ae-402e-46b7-98a8-7472b9e04128" alt="OCS console layout example"><figcaption><p>OCS console layout example</p></figcaption></figure>

1. **Navigation Bar (A)**:
   * Found at the top of every page, the navigation bar allows you to access the different sections of the application.
2. **Main Display Area (B)**:
   * The central part of the console typically contains a data table displaying the relevant information.
3. **Action Column (C)**:
   * On the far-right column of most tables, you’ll find available actions such as **edit** or **remove**.
4. **Table Header (D)**:
   * You can sort most tables by clicking on the header of any column.
5. **Table Tools (E)**:
   * Located at the top of the table, these tools include:
     * A **search bar** for filtering data.
     * Options to **export the table**.
     * Controls to **show/hide specific columns**.
     * The ability to choose how many rows are displayed per page.
6. **User Options (F)**:
   * Accessible via the **gear icon** in the top-right corner. These options allow you to edit your user information and log out of the application.

***

## Consulting the inventory

### **Accessing the asset inventory table**

Navigate to **Inventory -> Assets** using the top navigation bar in the OCS console. If agents have been installed and successfully inventoried, you will see entries in the table.

### **Consulting asset details**

* Click on an asset’s name to view its detailed information.
* The page is divided into three areas:
  * **Navigation tabs (left panel):** switch between categories such as Administrative data, Deployment, Hardware, Networks, etc.
  * **Main view (center/right):** displays the data for the selected category.
  * **Action icons (top right):** refresh the page, assign a package, etc.

<figure><img src="https://461838061-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtjrEC8kt8LJiJYFBs5CS%2Fuploads%2FqDD5D566KmqUK0ob3iOM%2Fimage.png?alt=media&amp;token=fa76442e-4981-4b01-b014-b2313284c649" alt="Details of an asset"><figcaption><p>Details of an asset</p></figcaption></figure>

#### **Template details**

Template data is organized into Categories for easier navigation. Each Category is accessible from the left-hand tabs panel. Inside a category, data is divided into sections. For example, the **Hardware** category contains sections such as **Batteries** and **Bios**.

<figure><img src="https://461838061-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtjrEC8kt8LJiJYFBs5CS%2Fuploads%2F1HWuYZ66I2xpIs2ZJmqE%2Fimage.png?alt=media&amp;token=70e67b29-dc4f-4c68-9cf5-9321da4da17a" alt="Example of template details for an asset"><figcaption><p>Example of template details for an asset</p></figcaption></figure>

{% hint style="info" %}
Don’t like the default layout? Categories are fully customizable. Learn more on the [Categories page](https://documentation.ocsinventory-ng.org/administrator-docs/server-setup/customization/categories.md).
{% endhint %}


---

# 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/quickstart-guides/for-users/console-overview.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.
