The dashboard is the operational core of the platform and is updated regularly: new indicators, more flexible filters, more readable views. This guide explains how new functionalities are introduced and how to keep up without chasing every minor change.
How they are released
New features on the dashboard follow a structured release cycle: first an internal verification phase, then a gradual release to the entire user base. Each version comes with a public release note describing what has changed, what has been added, and what has been improved. The notes are collected in the Upgrade software section.
Types of updates
- New indicators: new metrics that complement existing ones;
- New views: additional layouts to read the same data in different ways;
- New filters: tools to isolate accounts, periods, or categories of operations;
- Readability improvements: graphic revisions, contrasts, information ordering;
- Integrations: connections with new supported broker or external tools.
How to approach an update
Each time you enter the dashboard after a major update, spend a few minutes exploring the modified section without rushing before making operational decisions. Changing habits regarding numbers takes time, and the first days with a new view may require more careful reading. The How to read the dashboard guide remains the basic reference to return to.
What does not change
Updates evolve the interface but do not change the platform's scope: Arbicsx continues to provide technological software in accordance with D.Lgs. 58/1998 (TUF), does not manage capital on behalf of third parties, and does not offer advice. New functionalities help to better read operations, not to promise results.
If a new feature significantly changes a view you use every day, compare the old data and the new one for a few days before changing your operational habits, so as to understand how it is calculated.
Structured feedback
New features improve over time thanks to user feedback. If a new feature seems unclear or could be improved, opening a ticket for support with organized feedback is more useful than a generic comment on informal channels. In the How to send an effective request guide, you will find the recommended template.
Compatibility with existing habits
In most cases, new features are added without replacing others, so you can continue using the views you already know. When a view is instead revised or removed, the release is preceded by a dedicated communication: consult the Important communications guide to understand how these changes are announced.
Staying updated
A weekly check of the Updates category is often sufficient. There is no need to follow every micro-change: just be aware of the general picture and delve only into what truly affects your daily work.
Was this guide helpful?
If this guide wasn't enough, our team is available.
Every request is routed to the correct channel. Contact us and receive a structured reply as quickly as possible.
Go to support