Skip to main content

What's New

Subscribe through our RSS Feed or Atom Feed to stay up-to-date with what's new in Poly Lens!

Managing meeting rooms shouldn't require guesswork​

With Poly Studio Room 5.1, we are introducing new capabilities that help IT teams better manage Windows-based meeting rooms, simplify camera configuration, and troubleshoot issues more efficiently. Built around visibility, control, and manageability, this release makes it easier to support rooms at scale.

Summary​

  • Presenter Tracking configuration for Poly Studio E60 cameras using room snapshots
  • Remote Room Capture with a user consent workflow through Poly TC10 touch controllers
  • Automatic installation and management of the Poly Studio E70 Audio Service for MTR on Windows
  • Local Log Collection in the Studio room app for troubleshooting in secure or offline environments
  • Connected Device Management for improved visibility into room peripherals, settings and software updates within the Studio room app
  • Manage mixed meeting Room environments with greater precision
  • Customer-driven fixes for camera detection, policy management, device naming, installer reliability, and Poly TC10 usability

Smarter Camera Configuration with Poly Studio E60​

Setting up presenter tracking has traditionally required a bit of guesswork. Administrators often needed to adjust settings, test the results, and repeat until everything looked right.
With Studio Room 5.1, configuring Presenter Tracking on Poly Studio E60 becomes much more intuitive. Administrators can now capture a snapshot from the camera and use that image to define presenter tracking zones and stage framing boundaries directly within Poly Lens.
Instead of working with abstract coordinates, you are working with an actual view of the room. For training spaces, classrooms, and larger conference rooms, that means faster deployment and greater confidence that the camera will behave as expected.

Remote Room Capture with User Awareness​

When supporting rooms remotely, a common question is: What does the room look like right now? Is the camera positioned correctly? Has the furniture been moved? Is something blocking the field of view?
Studio Room 5.1 allows authorized administrators to request a snapshot from supported USB cameras through Poly Lens, only when the room is not active in call. To help maintain transparency, the process includes a consent workflow through the Poly TC10 touch controller, ensuring room occupants are informed when a snapshot is requested. Users in the room are even empowered to reject the request for a snapshot at any time.
It is a practical new tool that can help resolve issues faster and reduce the need for on-site visits.

Simplified Poly Studio E70 Audio Service Management​

For customers using Poly Studio E70, we have made audio service management more straightforward.
Studio Room can now automatically install, update and launch the Poly Studio E70 Audio Service when the camera is detected in a supported Microsoft Teams Rooms on Windows environment. Administrators can also enable or disable the service locally through the Studio Room app or remotely through Poly Lens policies.
The goal is simple: less manual intervention, more consistency, and fewer deployment headaches.

Local Log Collection for Faster Troubleshooting​

Not every room deployment has unrestricted internet connectivity.
For customers operating in secure or isolated environments, Studio Room 5.1 adds the ability to download diagnostic logs directly from the Studio Room app. This makes it easier to collect troubleshooting information about the Studio room app itself or the connected peripherals even when cloud access is unavailable. The logs for Poly TC10 are now bundled with the app logs. It is a small enhancement that can have a significant impact when supporting rooms in restricted environments.

Better Management for Connected Devices​

Meeting rooms are made up of many devices working together. Cameras, microphones, touch controllers, compute systems, and peripherals all need to function seamlessly.
Studio Room 5.1 app introduces a new connected device experience that gives administrators better visibility into the devices attached to Windows-based room systems. Device status, firmware information and update, and supported settings can now be viewed and managed more easily from within the Studio Room app. This is useful in those deployments where Lens cloud is not an option, and the IT administrators need to manage the PC based room and its peripherals locally or by remotely connecting to the PC based compute.
Some settings and custom software upload options may have limitations for certain devices, including the Poly TC10s. We are aware of these areas and continue to look for ways to improve the experience.
When something is not working as expected, having that information readily available can make a big difference.

Manage Mixed Meeting Room Environments with Greater Precision​

As organizations continue to expand and modernize their meeting spaces, IT teams are often responsible for managing a mix of room types, collaboration platforms, and workspace experiences. Maintaining consistency across these environments while meeting the unique needs of different spaces can quickly become a challenge.
Poly Studio Room 5.1 app enhances workspace management in Poly Lens by providing more granular policy controls for Poly TC10 touch controllers connected to Windows-based Room systems. To support this, Poly Lens now identifies these devices through a dedicated Poly TC10-PC model, enabling administrators to apply policies and configurations more precisely across their meeting Room fleet. Whether deployed with HP Poly Studio 5 and 7 Room Compute or HP Mini Conference G9 Plus PCs running Microsoft Teams Rooms, organizations gain greater flexibility to support unique Room requirements without affecting other environments.
With more targeted policy management, IT teams can better support the realities of complex workplace deployments, including organizations operating a mix of Windows and Android-based meeting spaces. Administrators can apply the right settings to the right devices, help reduce configuration errors, simplify ongoing management, and deliver a more consistent user experience across locations. By enabling more precise policy administration, Poly Lens helps organizations scale collaboration environments with confidence. IT teams can maintain consistent Room experiences across locations while adapting configurations to meet the unique requirements of different spaces, room systems, and deployment models.

Key benefits for IT administrators​

  • Simplify management across mixed Android and Windows Room technology environments
  • Apply policies more precisely to support different deployment scenarios
  • Reduce operational risk by targeting configurations to the appropriate devices
  • Maintain consistent meeting experiences across locations and Room types
  • Scale workspace management more effectively as collaboration environments grow

Want to get the most from policy-based workspace management?
Learn how Poly Lens policies help standardize device experiences, simplify administration, and maintain control across your deployment in the Poly Lens Policy Overview.

Continuous Improvements Based on Customer Feedback​

Along with the new capabilities, Studio Room 5.1 includes a number of fixes based on customer-reported issues. This release addresses:

  • Poly Studio E70 policy application through Poly Lens cloud
  • Camera detection reliability
  • MSI logging and installer behavior
  • Poly TC10 touch input and display scaling
  • Device name synchronization between Poly Studio Room and Poly Lens cloud
  • Service recovery during installation failures
  • A2 microphone status reporting in Poly Lens
  • Updated .NET runtime components used with HP Console Control deployments
    These improvements help make deployments more stable, and day-to-day management more predictable.

Get Started​

Ready to learn more about Poly Studio Room 5.1? Explore product documentation, deployment guidance, and support resources:

As Poly Lens continues to grow, you can expect ongoing updates that focus investment on the features and services that provide you with the most value.
On November 3, 2026, the Poly Lens Insights Feed will reach end of life.

Changes to the Insights Feed​

The Insights Feed currently gives you a news-feed-style experience that highlights trends and observations from your environment.
Beginning November 3, 2026:

  • You will no longer have access to the Insights Feed in Poly Lens
  • Automatically generated insight cards will no longer appear

You will not need to take any action unless you use one of the affected APIs described below.

What Is Not Changing​

You will continue to have access to the broader Poly Lens Analytics experience, including:

  • Historical and trend analytics on the Device, Room, and Site Overview pages under Analytics
  • The Device and Room Insights Dashboard under Insights > Dashboard
  • Historical reports under Insights > Reports

You can continue using these tools to understand device activity, room utilization, meeting behavior, and other important trends across your environment.

Information for API Consumers​

If you use select Poly Lens Insights and Analytics GraphQL queries, you will need to update your integrations before they are deprecated on November 3, 2026.

GraphQL Queries Being Deprecated Without Replacement The following GraphQL queries will be deprecated and will not be replaced:

  • topics
  • insightsPriority
  • topicIndicators

If your integrations rely on these queries, you should remove those dependencies before November 3, 2026.

GraphQL Query Being Replaced

The following GraphQL query will also be deprecated:

  • charts

You will be able to replace the charts query with newer, easier-to-use APIs. Additional information and migration guidance, including the full GraphQL field signatures, will be provided in the technical documentation before the deprecation date.

Looking Ahead​

To give you time to review and prepare, these changes will take effect 90 days after this announcement.
These updates will give you a simpler Poly Lens experience while supporting future investment in faster, more flexible Analytics and reporting capabilities.

Thank you for your continued feedback and partnership as Poly Lens continues to evolve.

Managing modern collaboration spaces requires more than floor plans and device lists. You need a way to truly visualize your rooms, understand how your HP Poly collaboration devices, including cameras, conference phones, microphones, and touch controllers, are positioned and performing, and track real-time device status across your environments.

As you may have seen at InfoComm 2026, today we’re introducing a smarter, more intuitive way to design and manage meeting spaces. We are calling this new tool Room VisualizerAI, a premium feature coming soon to HP Workforce Experience Platform with an active Poly Lens Pro for Rooms license.

Using just a handful of room photos and real-world dimensions, this AI-powered capability analyzes walls, furniture, devices, and spatial elements to bring your rooms to life as interactive, true-to-scale 3D models. The result is a more intuitive, data-driven approach to collaboration space design, helping you optimize device placement, validate coverage, and unlock new levels of visibility, control, and insight across your collaboration spaces.

How It Works​

Getting from four walls, your HP Poly devices, and a whiteboard to a fully interactive 3D model takes just three simple steps.

See Marty Sexton walk through how we bring rooms to life with Room VisualizerAI.

What You Can See and Do in the Digital Twin​

Once your room is brought to life as a digital twin, you can do far more than visualize it; you can actively design, optimize, and manage it.

Room VisualizerAI isn’t a static render. It is a dynamic planning and operations layer that becomes more powerful as you add devices and data.

  1. True-to-scale 3D room models
    Accurate digital replicas of your rooms for planning, analysis, and Generate procurement decisions, built from photos and real-world dimensions, not assumptions.
  2. Camera field-of-view overlays
    Visualize exactly what each camera captures from its intended position. Identify blind spots and coverage gaps before or after installation and adjust placement for optimal experiences.
  3. Acoustic coverage simulation
    Overlay microphone pickup patterns across the room to ensure every participant can be clearly heard, no matter where they sit.
  4. Simulated device swap
    Test and compare different HP Poly cameras and microphones using simulated device swap, a capability that lets you virtually evaluate configurations before making changes or purchases. Validate coverage, explore alternatives, and confidently choose the right setup for your space.
  5. Device placement and optimization
    Place, reposition, or refine device layouts within the model to quickly find the ideal configuration for your room.
  6. Device location and health insights
    View each device’s real-time status directly in the room context. Firmware alerts, connectivity issues, and hardware warnings are surfaced in one unified, spatially aware view.
  7. Remote access support and troubleshooting
    Diagnose and resolve room issues from anywhere, reducing onsite visits and accelerating resolution.
  8. Individual seat-level usage analytics (Coming post-InfoComm)
    Understand true room utilization down to the individual seat, who is using the space, how often, and how to right-size your room portfolio based on real data instead of estimates.

Reimagine How You Design and Manage Collaboration Spaces​

Room VisualizerAI marks a significant step forward in how you design, deploy, and manage meeting environments.

By combining immersive 3D visualization with real-time device insights and data-driven intelligence, you can move from reactive room management to proactive optimization, ensuring every space is purpose-built for better collaboration experiences.

With HP Poly Lens Pro for Rooms and the HP Workforce Experience Platform (WXP), you are not just managing devices, you are unlocking a smarter, more connected way to bring your collaboration spaces to life.

Get Started​

You manage more devices than ever across offices, shared spaces, remote workers, and hybrid environments. While Poly Lens group policies have traditionally focused on IP-based and cloud-managed devices, many organizations also rely heavily on USB-connected devices such as headsets, speakerphones, and USB cameras.

To help simplify management across these environments, Poly Lens is introducing support for applying group policy settings to supported USB devices connected through Lens.

More Consistent, Scaled Management Across Device Types​

With this update, you can extend group policy management to supported USB devices, helping ensure consistent configuration across users, groups, and locations. This makes it easier to manage device settings, software updates, and other supported policy-controlled behaviors from a centralized place in Poly Lens.

Many organizations deploy USB devices at scale across individual workstations, shared desks, focus rooms, and meeting spaces. As these deployments grow, maintaining consistent device behavior becomes increasingly important. Group policy support for USB devices helps reduce manual administrative effort by allowing you to manage supported USB devices using the same policy framework you already use in Poly Lens.

Examples of How You Can Use Custom Group Policies​

Custom group policies give you more flexibility to manage USB devices based on how, where, or by whom they are used.

For example, you could create a policy for executive users that keeps headsets and cameras on approved firmware versions, enables specific audio or video settings, and helps ensure a consistent experience across locations.

You could create a separate policy for shared workstations or hot desks where USB devices are used by multiple people throughout the day. This can help standardize settings so devices behave predictably no matter who connects to them.

For contact center or support teams, you could apply policies that help keep headset settings consistent across users, reducing the need for manual setup and helping teams stay aligned with company standards.

You could also create policies for specific device types, such as USB cameras, speakerphones, or headsets, so each category receives the right configuration based on its role in the workspace.

Why It Matters​

This update helps you

  • Extend centralized policy management to supported USB devices
  • Improve consistency across device settings and configurations
  • Reduce manual device administration
  • Support a more reliable end-user experience across locations and connection types
  • Better align USB device management with your organization’s standards

By bringing USB devices into the Poly Lens group policy experience, you gain more control, consistency, and visibility across a broader set of devices in your environment.

Getting Started​

After you have created a device group, you can assign group policies by going to Manage > Policies > Device Groups, then selecting the group you want to configure.

Once applied, group policies can help ensure supported USB devices receive the intended configuration when they are connected through Lens.

HP Poly Studio Desktop App Version 5.1 is now available for adoption! This exciting release introduces new IT admin-focused desktop management controls in Poly Lens cloud and support for new display features on supported HP Displays. It also includes further CPU consumption performance improvements and the resolution of many known issues from recent prior versions.

New Desktop Management Features in Poly Lens Cloud​

Locked Settings – IT Admins are now able to lock supported app and device settings in Studio Desktop through Policy. This restricts end users from making any changes to such settings, allowing IT Admins to enforce their policies when desired. Current Policy settings are considered “unlocked”, where the policy sets the default value for the setting, but the end user is able to change the setting if they wish. Restore defaults functionality for app and device settings have also been updated to follow locked Policy settings in the Studio Desktop app, while unlocked Policy settings and settings not managed by Policy will revert to factory default.

Desktop Feature Configuration – IT Admins can now disable Calendar and/or Wellbeing functionality in Studio Desktop if desired. If your organization is seeking to remove either of these features of Studio Desktop, this is now possible through visiting the App Management section of the Desktop App page in Poly Lens cloud.

Expanded Desktop Settings Management – More Studio Desktop app settings can now be managed through Poly Lens cloud. Categories added include General, Notifications and Device Alerts, and Language. These settings are also generally compatible with locked Policy settings. For example, IT Admins can now enforce a specific language across all Desktop apps managed in their Accounts, if desired.

For more information on this release, please see HP Poly Studio Desktop 5.1.0 Release Notes.

Shared devices are a critical part of today’s workplace infrastructure. Whether it’s a dock or display in a hotdesking area, a peripheral in a shared workspace, or an audio and video device in a meeting room, these assets are managed by IT but used by many people.

That distinction matters.

Shared devices are not personal devices. They are part of the workplace environment, and they need to remain consistently managed, monitored, updated, and available as part of that environment. For IT teams managing devices across offices, rooms, neighborhoods, and flexible workspaces, the challenge is not just getting devices deployed. It is keeping them correctly assigned, governed, and managed over time.

The Core Challenge​

In shared spaces, many different users may connect to the same device over the course of a day, week, or month. Those users may include employees, contractors, guests, or people from different parts of the organization.

Without a clear way to identify a device as shared, these devices can behave more like personally assigned devices than workplace-managed assets. That creates unnecessary complexity for IT teams, especially at scale.

A shared device should remain part of the managed environment where IT placed it. It should continue to appear in the right inventory, follow the right management workflows, receive the right updates, and remain visible for monitoring and reporting. Admins should not have to repeatedly verify whether shared devices are still associated with the correct account, space, or management structure.

For IT teams responsible for large fleets of shared devices, consistent ownership and control are essential. Shared devices serve many users, but they should remain managed by the organization.

Until now, there was no built-in control in Poly Lens Cloud to clearly designate a device as shared and enforce that management model at the device level.

Introducing Shared Device Mode​

Poly Lens Cloud now includes Shared Device Mode, a straightforward control that allows admins and device managers to designate a device as shared.

When a device is marked as shared, Poly Lens treats it as a workplace-managed asset rather than a personally assigned device. This helps ensure the device remains associated with the account where IT provisioned it, regardless of who connects to it or signs in through the HP Poly Studio Desktop application.

That means shared devices stay where they belong in Poly Lens Cloud, so IT teams can continue managing them with confidence.

With Shared Device Mode, IT teams get:

Account-locked Management​

The device stays associated with the current account where it is managed.

Admin-controlled Changes​

If a device needs to be moved or reassigned, that change requires an explicit provisioning action by an IT admin.

Multi-user Readiness​

Any number of users can connect to and use the device without changing its managed ownership.

Role-based Control​

Only users with Admin or Device Manager privileges can change the Shared setting.

This gives IT teams a reliable way to preserve their intended device structure across shared spaces, without adding ongoing manual cleanup or oversight.

Deciding Whether to Mark a Device as Shared​

The Shared setting is designed for devices that serve multiple people rather than a single assigned user.

Common examples include devices installed in meeting rooms, collaboration spaces, hoteling areas, hotdesking stations, shared desks, and other common workplace environments. These are devices that IT manages on behalf of the organization, even though many different people may use them.

Whether a device should be marked as shared depends on how your organization uses its spaces and manages its device fleet.

**Important:**If a device is intended to be claimed and managed by a single individual, do not mark it as shared. Shared Device Mode is intended for devices that serve multiple people, not personally assigned devices.

What this Means for Day-to-Day Management​

The practical effect of Shared Device Mode is simple: IT retains clear, predictable control of devices in shared spaces.

Devices stay associated with the account where they were provisioned. Monitoring, firmware management, inventory accuracy, and utilization visibility in Poly Lens Cloud remain consistent because the device continues to live in the right managed environment.

For admins, this helps reduce the operational overhead that can come from managing shared devices across many locations. There is less need to chase down devices, correct ownership issues, or re-establish the intended management structure after users connect.

And when a device does need to move, whether because a space is being reconfigured, a device is being reassigned, or an account structure is changing, that change happens through the normal admin provisioning workflow.

Shared Device Mode helps make shared device management more intentional, more predictable, and easier to scale.

How to Enable the Shared Setting​

The Shared setting is available now in Poly Lens Cloud. To enable it:

  1. Log in to Poly Lens Cloud and navigate to your device inventory.
  2. Select the device you want to designate as shared, or select multiple devices for a bulk update.
  3. Mark the device or devices as Shared and confirm.

Once enabled, the device is treated as shared and remains account-locked to its current managed account.

The Shared setting can be changed at any time by users with Admin or Device Manager privileges.

Full Documentation​

For complete details on the Shared Device feature, including how it interacts with provisioning workflows and account management, refer to the Shared Devices documentation in the Poly Lens support portal.

Looking Ahead​

Shared Device Mode is a meaningful step forward in how Poly Lens Cloud supports the realities of modern hybrid work. Meeting rooms, hotdesking spaces, and shared work areas rely on devices that are used by many people but managed by IT as part of a larger workplace environment.

With Shared Device Mode, Poly Lens gives IT teams a clearer way to manage those devices correctly at scale, helping keep shared assets organized, visible, and under the right administrative control.

For additional assistance, please reach out through HP Support.

The next time you sign in to Poly Lens, you’ll notice a refreshed login experience. We’ve updated the sign-in page with a cleaner, simpler design that makes it easier to access Poly Lens and get to work. It is a small change on the surface, but one designed to make everyday access feel smoother and more intuitive.

Looking Ahead: Simplifying Account Access​

This update also helps prepare Poly Lens for an important change coming soon. Over the next few months, we will begin asking users with local Poly Lens accounts to migrate to one of the available Single Sign-On options. This change is intended to make account access easier to manage while improving security, reliability, and consistency behind the scenes. If you currently use a local Poly Lens account, there is nothing you need to do right now. We will provide guidance in advance, and your important user information will carry over as part of the transition. Our goal is to make the migration as seamless as possible.

Built for Where Poly Lens is Going​

As Poly Lens continues to evolve alongside the HP Workforce Experience Platform, we are focused on reducing friction across the admin experience, starting with everyday moments like signing in. This refreshed login design is one of many improvements helping Poly Lens feel more connected, secure, and intuitive as we continue building for the future of workspace device and space management.

Microsoft has deprecated Incoming Webhooks for Microsoft Teams. As a result, Poly Lens Microsoft Teams notifications now use Power Automate Workflows as the supported replacement. For more information on this retirement notice, please visit Microsoft Dev Blogs.

To continue receiving Poly Lens notifications in Microsoft Teams channels, administrators must manually create a Power Automate workflow and update the Teams notification configuration in Poly Lens with the generated HTTP endpoint. This change ensures continued compatibility with Microsoft Teams and aligns with Microsoft’s supported automation and security model going forward.

Required Action: Create a Power Automate Workflow​

Follow the steps here in Poly Lens Help to create a Power Automate Workflows that replaces the deprecated Teams webhook.

What’s Changing​

  • Incoming Webhooks for Microsoft Teams are retired (Microsoft managed change).
  • Poly Lens no longer supports direct webhook-based Teams notifications.
  • Power Automate workflows are now the required integration method for delivering Lens notifications to Teams channels.

Important: This is a manual, one-time setup per Teams channel.

What’s Not Changing​

  • Notification types supported in Poly Lens remain the same:
    • Software Updates Available
    • Devices Offline
    • Licenses Expiring
  • Notifications are still delivered directly into Microsoft Teams channels

Who Needs to Take Action​

  • Poly Lens administrators
  • Admins currently using Poly Lens Notification with Microsoft Teams Incoming Webhooks

Known Limitations & Notes​

  • Power Automate Premium licensing is required and governed by your Microsoft licensing and tenant policies
  • Each Teams channel requires its own Power Automate workflow
  • Workflow creation must be done by a Teams user with appropriate permissions
  • This process replaces all Incoming Webhook based integrations

We appreciate your cooperation in ensuring a seamless transition. Visit Notification Center - Teams Notifications for more information.

If you have not done so already, we recommend beginning your adoption of the HP Poly Studio App. The future of the Poly Lens platform is here today with our recently released suite of HP Poly Studio Apps, and all future improvements to our Desktop, Mobile, and Room apps will happen within these apps. To read our full announcement for this launch, please visit Announcing the New HP Poly Studio App. The most important takeaway is that we have retained all existing functionality from the prior Poly Lens suite of apps, allowing for full continuity in your organization.

For the Poly Studio Desktop app, we plan to mark our next release as the latest release version in Poly Lens. This means that organizations with “use latest” policies for Desktop App version will automatically move to the latest version of Poly Studio Desktop at that time. For this reason, we recommend testing out the latest version of the Poly Studio Desktop app now (5.0.1), to become more familiar and comfortable with it in advance.

The Poly Studio Desktop app includes many new, exciting features that build upon our existing device management functionality. The app now supports HP Docks, Displays, and AI PCs, and includes a refreshed inventory view for this wide array of devices. Additionally, the app includes redesigned wellbeing reminders, light and dark modes, and a new calendar integration for one click meeting joins with Teams and Zoom for Windows accounts.

Note that the calendar feature requires enabling read access to your Microsoft O365 account. If your environment has additional security policies that require administrator approval first, you can refer to the HP Poly Studio Calendar Integration article to enable this feature organization-wide for a simplified rollout.

We look forward to further enhancing our HP Poly Studio apps in the near future, and thank you for your engagement as we continue to improve the experiences we provide for both IT Administrators and end users. Additionally, we welcome any feedback you have regarding our apps and cloud platform. Feedback can be submitted through our in-app feedback forms.

Today marks a significant milestone for Poly Lens and HP Workforce Experience platform. The Poly Lens Add-on is now available in WXP and with it, we're opening a new phase in how you connect, navigate, and manage collaboration devices across the HP software ecosystem. This release serves as the foundation for the ongoing development of the Poly Lens Add‑on experience within WXP.

If you caught our recent update, One small step toward a single pane of glass WXP…, you already know where we're headed. This release takes the next step by introducing a solution that ranges from secure tenant connectivity to efficient cross-platform navigation, all specifically designed to minimize obstacles and enhance the quality of device management.

What’s New in WXP​

The Poly Lens Add‑on enables organizations to connect a WXP tenant to a Poly Lens Cloud tenant. Once connected, WXP IT administrators can open Poly Lens Cloud via a click‑through workflow and continue managing collaboration devices and rooms as they do today by deploying, monitoring, maintaining, and measuring these devices without missing a beat.

This release is intentionally focused on the essentials:

  • Secure tenant‑level authorization between WXP and Poly Lens Cloud.

  • Seamless cross‑platform navigation, with Poly Lens opening in a new browser tab without the need to sign in again.

  • A strong foundation for future Poly Lens Add‑on enhancements in WXP.

Why this Matters to You​

You shouldn't have to search through several tools to find workflows for collaboration devices, rooms, and endpoints. This release helps reduce that fragmentation by enabling a governed, tenant‑level link between WXP and Poly Lens Cloud so you can move between platforms with fewer steps and clearer ownership.

Functionality available to you today:​

  • A cleaner path to device and room management: WXP is where you enable and manage the Poly Lens tenant connection, while device and room management continues in Poly Lens Cloud.

  • Role‑based access aligned to WXP governance: Access and permissions follow WXP roles mapped into Poly Lens Cloud.

  • Greater clarity at the tenant level: Only one Poly Lens tenant can be linked to a WXP tenant at a time.

New Connection Details Exposed in Poly Lens Cloud​

To make it easier to validate and audit tenant connections especially in multi-tenant environments this release also surfaces additional WXP connection metadata directly in Poly Lens Cloud > Integrations > HP Workforce Experience.

The following details are now visible:​

  • Name and Tenant ID of the WXP Tenant that is integrated

  • Who established the connection

  • Date when the integration was established

This visibility gives administrators a clear audit trail and makes it straightforward to confirm which tenants are linked, and when.

A Few Important Notes​

  • One‑to‑one tenant linking: Only one Poly Lens tenant can be linked to a single WXP tenant at a time.

  • Datacenter alignment is required: US-based WXP tenants can only connect to US Poly Lens accounts, and EU-based WXP tenants to EU Poly Lens accounts. Cross-region connections are currently unsupported at this time.

  • Where device management happens: The Poly Lens Add‑on focuses on authorization and navigation. Device and Room management continues in Poly Lens Cloud.

For deeper onboarding and guidance, refer to the WXP Documentation.

Ready to Take the Next Step?​

The Poly Lens Add‑on in WXP is a foundational milestone establishing secure tenant connectivity, streamlined navigation, and clearer tenant visibility that will enable future Poly Lens Add‑on enhancements to grow from a solid base.

Log in to WXP, navigate to Add‑ons > Poly Lens, and select Connect to get started.