> For the complete documentation index, see [llms.txt](https://eaclouddoc.eauditor.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/it-infrastructure/computers/computer-details.md).

# Computer Details

The computer card contains information about the selected device and functions that enable its monitoring and remote management.

To open it:

1. Go to:

   **Functions > IT Infrastructure > Computers**
2. Click the name of the selected computer.

The device card will open in a separate system tab.

<figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2FkrrpxhdEFaySuDxEzHer%2Fimage.png?alt=media&amp;token=150895f2-435e-4982-918f-6b57c787da4d" alt="karta komputera" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
The scope of available data and functions depends on the subscription plan, user permissions, monitoring configuration, and information sent by eAgent.
{% endhint %}

### Computer card tabs

| Tab                  | Purpose                                                                                         |
| -------------------- | ----------------------------------------------------------------------------------------------- |
| **Overview**         | Summary of computer status, security, resource usage, and user activity.                        |
| **Details**          | Data about the operating system, hardware, network, and resources associated with the computer. |
| **Management**       | Terminal, file explorer, and service and process management.                                    |
| **Software**         | Information about the software registered on the computer.                                      |
| **Users**            | Device owner, IT administrator, and user activity.                                              |
| **Patch management** | System update status and available operations.                                                  |
| **Alerts**           | Events requiring attention, their severity, impact, and resolution status.                      |
| **Documents**        | Files and documents associated with the device.                                                 |

### Frequently asked questions

<details>

<summary><strong>Why can't I see all tabs or functions?</strong></summary>

The availability of items may depend on the subscription plan, user permissions, the device operating system, and the eAgent configuration.

</details>

<details>

<summary><strong>Why is some data blank?</strong></summary>

eAgent may not have sent the required information yet, or the given monitoring type has not been configured. Check the device's last connection date and the assigned [monitoring configuration](/eacloud-docs-en/features/tools/configuration/monitoring.md).

</details>

<details>

<summary><strong>Does opening the computer card perform an operation on the device?</strong></summary>

No. Opening the card is only for viewing data. Remote operations require selecting the appropriate function and confirming it.

</details>


---

# 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://eaclouddoc.eauditor.eu/eacloud-docs-en/features/it-infrastructure/computers/computer-details.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.