v5.5 - 08.2025
Document management
Document management provides you with a central tool for managing documents in a structured way in our cloud and assigning them to specific companies, routers or machines.
What the document management offers
- Location-based assignment of documents at company, router or machine level
- Filter and search functions by:
- File name or content
- Name or type of the assigned company, machine or router
- Location of the assigned reference
- Simple handling of complex infrastructures
Limits
- Maximum 100 MB per file
Example use cases
Document management can be used for various applications. For example:
- Internal application: Maintenance documents
- To ensure that the necessary data can be accessed quickly during maintenance work, it can be assigned to the relevant machine so that the personnel carrying out the work do not have to invest any time in searching.
- External application: Customer instructions
- To make it easier for customers to use your machine, it is possible to provide them with instructions and other documents specifically for this machine.
MQTT user management
The new MQTT user management allows users to create their own MQTT clients to retrieve machine data directly from the MQTT broker and process it individually.
π What does the MQTT user administration offer?
Until now, machine data was only visualized in the cloud. With the new feature, users can now:
- Create their own MQTT clients
- Establish authenticated connections to the MQTT broker
- Only access machine data for which they are authorized
- Use data in real time for their own systems or applications
π Security & access control
Every MQTT client is:
- User-bound: Access is restricted to the machines assigned to the respective user.
- Individually manageable: Users can create, manage or delete clients themselves.
- Automatically secured: Access data and rights are controlled by the system (no unauthorized access possible)
π² Push notifications with device management
With the latest update, the push notifications have been technically and functionally enhanced. Instead of being sent via FCM Topic as before, notifications are now sent to individual devices using tokens. This provides more control, transparency and testing options.
π What has changed?
Each device (e.g. browser or app) receives its own unique token that can be used to address it specifically. This enables:
- Precise control of which device receives a message
- Overview and management of all registered devices per user
- Test messages (demo) to check the connection
π§© New functions at a glance:
π₯οΈ Device overview per user
All registered devices are now listed in the user's notification details, including:
- Device type (browser, iOS, Android, etc.)
- Last access
- Device name
ποΈ Delete devices
Individual devices can be removed manually, e.g. if a token is invalid or a device is no longer used.
π€ Send demo messages
A demo notification can be sent to a specific device via an integrated test mechanism. Ideal for checking whether the device is correctly registered and accessible.
π Advantages of the token-based push system:
- π― Targeting accuracy: only relevant devices receive the message
- π§Ό Better maintainability: invalid tokens can be easily removed
- π§ͺ Simple verification: function test possible directly from the system
- π± Multi-device capable: Users can register several devices at the same time
OPP (Open platform) support
With the new router type OPP, it is now possible to use non-Eurogard routers to collect measured values. The router-side implementation is carried out by the customer himself.
π Multi-factor authentication (MFA)
With the latest release, the Multi-Factor Authentication (MFA) security function has been integrated into the platform. It enables significantly higher security when logging in through additional verification steps.
π‘οΈ What does the MFA function offer?
- Support for two-factor authentication (2FA) via authenticator apps (e.g. Google Authenticator)
- Support for passkeys - a modern, passwordless login method based on cryptographic keys
- Simple configuration per user or at company level
βοΈ Management options
- Administrators can specifically enable or disable 2FA or passkey requests for users
- Users can also manage their MFA settings independently via the user settings
- Flexible regulation at company level: Admins can make 2FA mandatory for all users