This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Restricting Access to Transaction Monitors?

We currently have NPM so if we moved forward with SEUM it would be as a module versus a standalone.

In this implementation, is there a way to restrict users to see only the transaction monitors that are appropriate to them? Currently in NPM we do this at the node level using custom properties but I would also need to be able to do this with SEUM if we were going to offer this as an additional monitoring service to our customers.

Thanks in advance any and all responses!