> 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/devices/details-card.md).

# Details card

The device detail card is available after clicking the device name in the view **Devices**. It is primarily used to review and manage devices that do not have the service installed, such as printers, USB drives, or monitors. The detail card offers limited functionality compared to agent-equipped computers. Devices can be added manually, discovered via the network, or imported from a file.

***

## **Overview**

Tab **Overview** provides a general overview of the selected device.

### **Overview**

* **Security**: Information about the device's security status, if available.
* **Alerts**: Widgets indicating issues that require the administrator's attention regarding the device.
* **User**: Preview and ability to edit the user responsible for the device.
* **Device**: Device type, its name, unique ID and the organization it is assigned to.
* **User activity**: Information related to user activity on the hardware.
* **Additional information**: Ability to add notes about the device.

### **Relations**

Tab **Relations** allows viewing the device's relationships with other infrastructure elements, such as:

* Related computers,
* Related peripheral devices (e.g., monitors, keyboards),
* Related documents and other resources.

***

## **Users**

Tab **Users** provides information about users associated with the device. Displayed data includes:

* The user's name and their domain.
* **Login status**: Information about login time and duration of user activity.
* **Edit capability**: Editing the owner and additional users of the device.

***

## **Alerts**

Tab **Alerts** presents current notifications related to the device. These can be critical alerts, warnings or informational messages regarding device issues and status. The view allows managing alerts, including closing or resolving the issue. This includes:

* **Critical alerts**: Requiring immediate response.
* **Warnings**: Information about potential issues.
* **Information about device status**: Such as uptime or connection status.<br>

***

## **Documents**

Tab **Documents** allows storing and organizing documents related to the device. Capabilities include:

* **Adding documents**: Uploading files via the **Add here** option or by dragging files.
* **Organizing documents into folders**: E.g. **Protocols**, **Invoices**, **Other**.
* **Document information**: Displayed are the name, relationships, creation date, file size and the person responsible for creating the file.

***

{% hint style="warning" %}
These are key details for managing devices in the system without an installed agent. Documentation for other device types or extended features (e.g. [computers with an agent](/eacloud-docs-en/features/it-infrastructure/computers.md)) is available in the relevant sections.
{% 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 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://eaclouddoc.eauditor.eu/eacloud-docs-en/features/it-infrastructure/devices/details-card.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.