> 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/tools/messages.md).
# Messages
## Messages
Tab **Messages** allows sending and scheduling desktop notifications for users and computers.
The section enables:
* sending one-time messages,
* creating alerts,
* scheduling recurring messages,
* using ready-made templates,
* monitoring active delivery schedules,
* verifying message delivery and read status.
The module provides three main areas:
* **Quick Message**
* **Message Templates**
* **Active Cycles**
### Quick Message
Option **Quick Message** allows you to immediately send a message to selected recipients.
When creating a message, you can specify:
* message type,
* recipients,
* expiration date,
* message content,
* recurring delivery schedule.
### Message type
The system allows sending two types of messages
{% tabs %}
{% tab title="Regular message" %}
**Regular message:**
* is displayed in the lower-right corner of the screen,
* can be postponed by the user for later,
* does not block the user's active work,
* the full content is visible after opening the message.
**This type of message works well for:**
* reminders,
* organizational information,
* administrative messages,
* less critical notifications.
{% endtab %}
{% tab title="Alert" %}
**Alert:**
* is displayed centrally on the screen,
* overlays other active windows,
* requires the user to close it,
* forces confirmation that the message has been read.
{% hint style="warning" %}
The end user cannot postpone the alert for later.
{% endhint %}
**This solution is recommended for:**
* security messages,
* critical administrative information,
* urgent actions requiring user response.
> *A good practice is to add a statement to the message content such as:*\
> *“Closing the message indicates acknowledgment of its content.”*
> {% endtab %}
> {% endtabs %}
### Recipient selection
Messages can be directed to:
* computers,
* users,
* groups of devices or users defined by Focus.
#### Computers
After selecting computers, the message will be displayed on the specified workstation.
{% hint style="info" %}
* the message will appear regardless of who is currently using the device,
* the message will also be displayed to the user who logs in later.
{% endhint %}
#### Users
After selecting users, the message is assigned to a specific user.
{% hint style="info" %}
The message will be displayed regardless of which computer the user is currently logged in to. This is especially useful in domain environments and large organizations, where users frequently change workstations.
{% endhint %}
#### Focus
The system also allows you to use previously prepared filters of the [**Focus**](/eacloud-docs-en/features/tools/configuration/focus.md).
This makes it possible to quickly target messages, for example, to:
* a specific organizational structure,
* company departments,
* computers with a specific operating system,
* servers,
* selected device groups.
### Expiration date
The expiration date defines the moment after which the message will no longer be delivered to users.
This mechanism is particularly useful for time-bound messages, for example:
* server restarts,
* service work,
* maintenance windows,
* planned technical outages.
> *Example:*
>
> * *if the user was absent during message delivery,*
> * *and the expiration date has already passed,*
> * *the message will not be displayed after they log in again.*
As a result, users do not receive outdated information.
### Message content
The message editor allows you to create detailed messages.
Available functions include:
* text formatting,
* changing the appearance of the content,
* adding images,
* adding links
* preparing more comprehensive informational messages.
### Recurring messages
A message can be set as a recurring task.
To do this, select the option:
* **Set as recurring task**
After it is enabled, additional schedule settings will appear.
It is possible to define:
* the start date of delivery,
* the end date,
* the execution interval,
* the number of executions.
The system allows, among other things, to:
* send a message indefinitely,
* end delivery after a specified date,
* end delivery after a specific number of executions, e.g., after 5 sends.
### Logs and confirmations
Information about message and alert reads is saved in the tab:
* **Logs**
This allows the administrator to verify:
* who received the message,
* who read it,
* when the message was acknowledged.
## Message Templates
**Message Templates** allow you to prepare ready-made messages for repeated use.
When creating a template, we define:
* template name,
* message content,
* optional description.
After saving, the template is added to the list of available templates and can be used when creating new messages.
### Template operations
Message templates can be:
* edited,
* copied,
* deleted.
The copy option allows you to quickly create new message variants based on existing templates.
## Active Cycles
Tab **Active Cycles** displays information about currently active recurring message schedules.
The administrator can check:
* which messages are active,
* their execution schedule,
* delivery status,
* interval configuration,
* cycle end time.
### Summary
The Messages module enables effective communication with end users directly at their workstations. With support for alerts, schedules, and recurring messages, the system can serve as a central tool for administrative and security communication.
The solution is particularly well suited for:
* security incidents,
* service work,
* administrative communication,
* information campaigns,
* enforcing acknowledgment of the message.
Because sometimes an email ends up in the “read it sometime” folder, whereas an alert in the middle of the screen is hard to miss.
---
# 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:
```
GET https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/tools/messages.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.