General Settings

When scrolling down in the assets view, the top Header row is not visible - please have this header row frozen in place so that is always shown, even when scrolling down the page.

There’s a lot of excess that can be removed to optimize space.

Please enable the users to select also "OR" for the conditions not only AND

Can we add in the Asset Importance as one of the Asset collection records? I would like to add a series of tags to the assets based on their importance.

Enhance the Discovery Settings configuration by allowing users to exclude specific IP addresses (both static and ranges) directly within an existing discovery scope, rather than requiring separate entries. At present, our users can Define scan scopes using CIDR ranges & Exclude devices via MAC address However, excluding specific IP addresses requires creating a separate discovery entry or modifying the CIDR range, which can be inefficient and harder to manage. Here is an example "A network scan for 192.168.1.0/24 needs to exclude: A firewall (192.168.1.1) A sensitive server range (192.168.1.200–192.168.1.210)" Currently, this requires multiple configurations. With this feature, it could be handled in a single, clean entry.

Ninja RMM uses a service named "Lockhart" when backup is enabled for that endpoint. However, it does not make a new application item. It runs through the "NinjaRMMAgent" application. Every ninja endpoint has "NinjaRMMAgent" Not every "NinjaRMMAgent" is actually backing up.

Currently if an agent is automatically deprecated for inactivity and comes back online, the previously assigned 'manual tags' are wiped.

We would like to request a dedicated section within the Jobs area for Lightweight Agent Scans. When a Lightweight Scan is manually initiated, there is currently no clear visibility into its status. It would be very helpful to see: Whether the scan is in progress When the scan has completed The start and end time Any relevant status details or errors Having real-time status tracking within the Jobs section would improve troubleshooting, technician efficiency, and overall workflow visibility.