Hello everyone,

we are using Omada in a professional MSP context to manage customer environments with 20+ switches per site.

Our main use case – and honestly one of the biggest reasons we chose Omada – was the ability to:

• Define networks globally

• Create and manage port profiles centrally

• Apply those profiles across multiple switches in a scalable way

•  

After the latest update, this workflow appears to be fundamentally changed.

As far as we can see, port profiles now need to be assigned per port individually. We are being referred to multi-edit (batch editing), but this is not a replacement for global profile management across multiple switches.

For us, this removes the core efficiency advantage of the platform. What previously took minutes can now take hours in larger environments.

So I would like to ask the community:

1. Is this change officially confirmed as intended behavior?

2. Is there any roadmap information about restoring global port profile management?

3. Are we overlooking an alternative method (e.g., switch groups, template logic, inheritance models)?

4. How are other MSPs handling this change in larger deployments?

We have deployed Omada in one of our largest customer environments specifically because of this centralized management capability. Losing this functionality significantly impacts our operational efficiency.

If anyone has official statements, changelog references, or best-practice workarounds, I would highly appreciate it.

Thank you.