Hi @KBhuva 

Thanks for reaching out to TP-Link Business Forums.

Thank you for your detailed feedback and for taking the time to share your experience.

We fully understand your concerns regarding the changes introduced in Omada Controller 6.0 and later versions, particularly the adjustments to the Insights section and the impact this may have on your daily operational workflow. We acknowledge that the previous centralized visibility for items such as routing tables, VPN status, and switch monitoring was valuable for administration and troubleshooting.

At the same time, we would like to clarify that these design changes were made based on broader market feedback and user research, with the goal of improving overall usability and simplifying device management across diverse environments. That said, we also recognize that such changes may not align with every user’s workflow. Your concern in this regard is completely valid and appreciated.

Given this, we would like to ask for your permission to move your post to a feature request / voting thread. If more users express similar needs and support this request, we will consolidate the feedback and submit it to our R&D team for further evaluation and potential improvement in future releases.

We sincerely appreciate your input, as it helps us better understand real-world usage scenarios and refine our products accordingly.

Hi  @Gabriel-TP,

Appreciate the quick feedback and clarification.
 

You mentioned that these changes were made based on broader market feedback and user research. I assume this refers to feedback received through the public feature request forums, unless TP-Link hosts a separate feedback or testing community that users are generally not aware of.

I ask this because I was not able to locate many public feature requests or discussions specifically asking for the previous Insights monitoring items to be removed or relocated in this manner.

I am not looking to argue the design direction, however I do feel these changes have negatively impacted operational workflow, particularly for environments of a larger scale such as mine.

My deployment currently consists of:

• 1 × ER8411 v1.0
• 12 × SG3428XPP-M2 v1.20
• 1 × SX3016F v1.20
• 9 × EAP683 UR(EU) v1.0

In environments of this size, centralized operational visibility becomes extremely important for efficient administration and troubleshooting.

I also generally wait before rolling out controller and firmware updates into production specifically to avoid workflow disruptions such as this. Since implementing the update, the rest of the team has also expressed dissatisfaction with this particular change.

Please feel free to move the post into the feature request section if required. However, from my perspective, I still consider this a broken operational workflow rather than simply a feature request, as the redesign does not simplify administration for our environment and instead introduces additional steps and complexity into day-to-day management.

Thank you again :-)

KB

I also came across another feature request below which further confirms that users were actively using and relying on the previous centralized operational visibility within the Insights menu or can say that they would prefer it to be centralized:

https://community.tp-link.com/en/business/forum/topic/857656?moduleId=4

The VPN Status section was previously available directly within Insights and was much easier to locate and manage operationally.

Since these changes were introduced, functions such as VPN monitoring now require additional navigation and are less intuitive to access during troubleshooting or routine administration.

This reinforces the point that the previous centralized Insights layout was actively useful in real-world environments and that the current redesign has reduced operational efficiency for some administrators.

Hi @KBhuva 

We understand your perspective, especially knowing the impact on your workflow is critical. The feedback and data used for product design decisions are not limited to inputs from the public forums or technical support interactions. They are gathered through a broader process that includes dedicated market research efforts and user studies conducted by internal teams. Unfortunately, we are not able to share further details about those processes. We appreciate you taking the time to articulate this and to provide concrete examples. Your request has been formally recorded, and we will ensure that your feedback—along with the related use cases you described—is submitted to our R&D team for further evaluation.

BTW, on your behalf, we will now move your post to the Voting thread.

  @Gabriel-TP As I understand, the information mentioned by KBhuva is still there but we need to dig into the Omada portal to find it. In general, and as a network engineer, I agree having the information KBhuva mentioned readily available as indeed, they are helpful while troubleshooting. They may not be so helpful for monitoring and general views, but they are gold for troubleshooting!

I suggest the creation of "views" in the portal so we can select (or adjust) what we would like to see. In that way NOC can have their own items on the front screen, while engineers have the information that helps them most.