Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Orion NPM - NetPath account limitations

Orion NPM - NetPath account limitations

Updated July 19, 2017


This article describes how to restrict access to NetPath endpoints for a user, considering the following scenario:

  • Orion is used in a NOC environment or one Orion platform hosts many MSP customers.
  • Orion is deployed using individual login accounts, each configured with specific node restrictions.
  • NetPath is not adhering to these restrictions and there is no way to limit the NetPath traces to a specific user or MSP customer account via the web GUI. NetPath does not have special account limitation settings (no method to choose who can delete, edit, or create NetPaths), and it does not have a way to filter out which paths can be seen per account (no method to edit specific path settings on the Summary page). 

Note: There are open feature requests for this function:



  • NPM 12.x
  • NetPath v1.x


Workaround to hide NetPath Admin

Restrict the NetPath Summary page to admin users only.

  1. Edit the menu bar for each user that you want to restrict from NetPath.
  2. Remove NetPath by deleting "netpath services" from the Network_Tabmenu from the menu bars of the users.

If you do not have a customized menu bar, create one and apply it to the user accounts.

Workaround to view specific NetPath traces ONLY

  1. Go to Settings > Manage Views.
  2. Search for and add  CUSTOM HTML resources.
  3. Save the resource such that it becomes part of the view.
  4. Edit the resource to assign a title and add custom HTML links to the paths that should be available to the users.



For example:

<b> Click <a href=""></a> to go to Orion Demo.<br /> 


<b> Click <a href="http://dev-cor-ktwo-03/ui/netpath/ro...7/07/20/0/0/0/"> (Thwack Route)</a> to go to Orion Demo - Thwack NetPath Link.<br /> 


<b> Click <a href=""> (Google Route)</a> to go to Orion Demo - Google NetPath Link.<br /> 


The output will look like the following:

Click to go to Orion Demo.
Click (Thwack Route) to go to Orion Thwack NetPath Link.
Click (Google Route) to go to Orion Google NetPath Link.



Last modified
18:16, 20 Jul 2017