> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/connect-3.2-en/operacion.md).

# Operation

## Editran Connect User Interface

The Editran Connect interface is designed to offer clear and functional navigation, geared toward operational and administrative tasks. This section describes the main UI elements that are always present or common to most sections.

![Editran Main Screen](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-36bec36428128b404183c82cb4921fc0cc103922%2F01_general_detalle.png?alt=media)

The main areas numbered in the reference image are detailed below:

***

### 1. Top header

It contains contextual navigation and persistent system elements:

* **Section title**: Shows which module or screen the user is in (for example: *Dashboard*).
* **Breadcrumb trail**: Lets you know the context or hierarchy of the active section.
* **User icon**: Quick access to profile options, log out, etc.

***

### 2. Side navigation menu

Located on the left, it allows quick access to the different modules of the system. The menu may include icons for:

* **Dashboard**
* **Address Book**
* **Schedules**
* **Messaging**
* **Status**
* **Local settings**, among others.

> ℹ️ *Note:* The icons are accompanied by tooltips when hovering the mouse over them.

***

### 3. Main workspace area

This is the space where information is displayed according to the active module. In the case of the *Dashboard*, it is divided into two main blocks:

* **Outgoing**: Monitoring of channels that transmit data to other nodes.
* **Incoming**: Monitoring of channels that receive data from other nodes.

Each block shows:

* Channel status: *Transmitting*, *Blocked* or *Available*.
* Charts or visual indicators.
* Access to quick actions (such as viewing channels).

***

### 4. User panel

Located in the upper right, it shows the initials of the connected user and allows:

![User menu](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-3bf9523cf1879e66cddee38266b0d69355241005%2F02_general_contextual.png?alt=media)

* User profile, from where you can [change your password](https://gitlab.devops.onesait.com/onesait/disruptors/ecosystems-editran/editran-documentation/-/blob/public/connect/3.2/operacion/general/cambiar_password.md)
* Local Settings (if you are a global administrator)
* Email notifications
* Theme selector (Light/Dark)
* Log out

***

### Other visible sections

* **Latest alerts**: Section at the bottom where the latest system alerts are shown.
* **Transmission history** and **Activity log**: Links available in the header to access the system's detailed logs.

***

> ✅ *Usage tip:* Familiarizing yourself with the layout of this interface makes navigating between modules easier and reduces response time in operational tasks.


---

# 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://docs.editran.onesait.com/documentacion-editran/connect-3.2-en/operacion.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.