Allow for an NCentral customer to have assigned to it a primary from the NCentral User list (our employees), as Account Managers or other term. Lets say I have 100 Accounts divided amongst 10 Account Managers (selectable from my users). If this data is available via the API and pumped over to a new column (UserID) in dimCustomer in the warehouse database, then one can make assignments in ticket application based on ...more »
The problem with the current dashboard is: first column is the customer name or device, anyhow: that is how you recognize the row. When scrolling horizontal your customer identification goes out of sight, so you have no clue which line is who's account, so: you get lost and can make mistakes easily. See my screenshot. The red box should be (optionally) locked, so when pressing the green arrow, the info slides behind the ...more »
We think there should be a way to report on this or, at least, add another icon (flag) next to the contacts, that have admin access.
When creating an automation policy, I need a way to include the customer ID and the Site and the machine id in N-central (not necessarily the net bios name) in an email that is being sent out. If i could pull this information into a variable that would be great. An email that only contains the computer name is not very useful with you have thousands of computers.
So the SO Level reporting (and the descriptions) is broken by design. It's a UX Disaster. They were never actually meant to be run at the so level which is why they don't include the details that the customer level reports do, and were never updated to include the customers/sites that an so level report would need to be fit for purpose. Yet the descriptions are the same as the customer level reports which is completely ...more »
After introducing partial support for sites into n-central quite some time ago, support for customers/sites was removed or never actually added in filter previews and reports.
I am told that for a report or filter to include the customer/site instead of just a device name, a feature request needs to be created because Solarwinds consider this to be by design.
Hi! I would be extremely useful to have a button for "New Ticket" or "Add a New Ticket" when looking at the customer on the dashboard. This would eliminate me from having to then click tickets and then choose "Add a ticket". The most common action when you open a customer's information is going to be to add a ticket, in my opinion. At a minimum, the option to add a ticket should be listed under the "ACTIONS" button. ...more »
The ability to provide customer logins / access restricted to only themselves for self-service offers great opportunities in itself but this option lead not only to problems with the policy management (as you are able to access all policies) but also the active discovery. If you have two different customers with a custom login for self-service certain scenarios can lead to both customers seeing each others network. ...more »
The customer ticket request portal should be mobile friendly. Customers that want to manage their tickets and either lose internet or are on the road away from their company can't do anything because they can't work with the customer portal.
Currently you can only set a customer to active or non-active. When non-active they arent displayed as a customer to assign a ticket too.
We currently have a customer 'on-hold' due to lack of payment. I would like an option to put the customer ON-HOLD and then add a note to say why.
Doing this should also put ALL exiting and new tickets ON-HOLD automatically.
it would be extremely handy to be able to, at the very least, export the selected customers from the rules grant customer/site access tab, at the very most, have a report that will show me the associations between customers and rules, allowing me to pick which customers, or which rules I want to run the report against. In particular I need this for all of my patch management rules as we currently have to audit patch ...more »
The ability to move customers or sites between SOs at the system level would be useful. We have managed and un-managed customers in separate SOs, sometimes they change their agreement and need to be moved.
The ability to move customers/sites/devices already exists within an SO, this would just be an extension of this feature up to the system level.