I'd like the ability to block customer level users from being able to access filter/dashboard/repositoy items that were created at a higher level. I don't want to completely remove access to the filters/dashboards/repo as they should be able to manage items at their level and below, but don't want them being able to look into the items that were created at a higher level, since they're not a higher level user that should ...more »
Currently, rules can only target devices inclusively based on one or more filters, targeting all devices included in them. It'd be helpful to have the ability to *exclude* devices based on filters also. For instance, I want to create update schedules that ensure Domain Controllers don't get rebooted alongside everything else. Currently that means setting up a separate filter that includes class "Servers - Windows" except ...more »
I'd like to create a filter specific to when devices were added to the N-Central system, so I can see new devices, or those that have been in the system for a specific period of time.
It would greatly enhance managing PM if we could create workstation filters based on patch status. In the days following a big patch release I am very interested in identifying workstations with patches in Pending status as they may be having issues. I have multiple workstations at several clients that are rarely used and usually offline. To reduce clutter, I usually invoke a Workstation Filter to see only online workstations. ...more »
right now, the only option to transfer filter/item ownership is to kill the user, at which point n-central asks for you to grant ownsership to someone else.
I vote that this ability should be possible without the death penalty for the unsuspecting user that had the nerve to try to create a filter themselves.
they can do so for repository items, so why remove the ability to do so for filters?
it makes for a pretty powerless "product admin"...
right now the options are to have the user make the change, change th euser passowr dand make the change yourself, or kill the user which then transfers ownership of all their filters, items etc to another user. Either option seems too complicated to me.
I discovered today that productadmin is no longer able to edit a filter owned by another user. I propose that we fix this by tying it in with the user roles, and offer the ability for shared ownership to the members of the user role on a filter/repo item marked as shared so anyone can easily update. Changes would be auditable. If the item is marked as private then it belongs to the user, but we should allow for the ...more »
It would be useful to be able to filter services that are in a disabled state in the Active Issues page. This can currently be done already by unselecting all the status' in the filter and selecting the services you are interested in. However, the problem with this is that those services will show up with any status. So it would be good if you could add in a 'Disabled' status next to 'Failed', 'Warning', 'Normal', ...more »
It would be great if our N-Central users could create personal filters without assigning them the filter manage permission.
Maybe add another permission level to Filter.
When building a filter at a customer level, the preview shows devices from the SO level (or possibly higher; we only have one SO). Steps to replicate: Start with two devices in different customers. Go down into one customer, and start creating a filter at the customer's green level. Choose to preview the devices affected. You will see devices listed from other customers. This is undesirable and does not match other behavior. ...more »