Who can use this feature?
👤 Organizations Owners, Admins, Group Admins, Group Facilitators, and custom roles with the "Screen Casting, Camera Casting, and Two-Way Audio" permission.
🚩 Available on the Essential, Classroom Pro, and Enterprise Plans.
Overview
Remote Assistance lets you see and support a device user in real time from the ArborXR Web Portal over Wi-Fi. You can cast the user's screen, stream their camera, talk with them, and hear the device's audio. This is how teams guide users through XR experiences, troubleshoot remotely, and deliver hands-free expert support to field workers and frontline staff.
Remote Assistance is made up of four capabilities.
Capability | What you do | Supported devices |
Screen casting | Cast the device's screen output to the portal. | All VR devices (PICO, Meta Quest, HTC VIVE, DPVR, Play for Dream), plus phones and tablets. |
Camera casting | Stream the device's point-of-view camera feed to the portal. | Meta AI glasses, Samsung Galaxy XR, Magic Leap 2, plus phones and tablets. |
Two-way audio | Talk to the user through the device, and hear them talk back. | Every device ArborXR supports, from VR headsets to AR devices to phones and tablets. |
Device audio playback | While casting a screen, hear sound coming from the device, such as the audio in an app. | Same as screen casting: all VR devices (PICO, Meta Quest, HTC VIVE, DPVR, Play for Dream), phones, and tablets. |
⚠️ In order to use this feature, URL stun:stun.cloudflare.com:3478 must be whitelisted in your network. For more information on the URLs and ports required by ArborXR, see this article.
Group Facilitator Role
Often the people who configure device content and settings are not the same people who run sessions. The Group Facilitator role exists for this reason. It limits a user's access to remotely assisting and remotely launching content across specific groups of devices, without granting full portal access. For more on user roles, see this article.
Start a Remote Assistance Session
When you start a session, the portal presents only the actions the device supports:
Cast Screen for screen casting
Cast Camera for the device's camera feed
Two-Way Audio to talk with the user
💡 Each action runs independently. You can start two-way audio on its own, or start casting first and layer two-way audio on once the cast is running. Start or stop any one without ending the others.
Cast Multiple Devices
Option 1: From the All Devices Page
Navigate to Devices & Groups in the side navigation menu. Observe that by default
Select one or multiple devices.
Click Actions.
Click the action you want, such as Cast Screen, Cast Camera, or Two-Way Audio.
Option 2: From a Group's Devices Page
Navigate to Groups in the side navigation menu.
Select the Group in question.
Select one or multiple devices.
Click Actions.
Click the action you want, such as Cast Screen, Cast Camera, or Two-Way Audio.
Cast Single Device
Navigate to Devices in the side navigation menu.
Select the device in question.
Click Remote Control & Assist.
Click the action you want, such as Cast Screen, Cast Camera, or Two-Way Audio.
Hear the Device's Audio While Casting
Once you start casting a device's screen, click the volume icon in the session view to toggle on device audio playback. This lets you hear the sounds the user hears, such as audio playing inside an app, alongside the screen feed. Device audio playback is available on every device that supports screen casting: all VR devices (PICO, Meta Quest, HTC VIVE, DPVR, Play For Dream), phones, and tablets.
Remotely Launch Content
Remotely launching content goes hand in hand with Remote Assist. A Launch Content button is built directly into the session view, so you can launch an app, video, or WebXR link without leaving the session.
Configure User Consent Settings
By default, Remote Assistance sessions start without prompting the wearer. To require the user to grant permission at the start of every session:
Navigate to a group
Select the Settings tab
Select Security
Uncheck the checkbox next to Request User Consent for Remote Assist to disable the consent dialog.
Click Save.
This is what the permission prompt looks like (captured on Meta Quest):
Meta AI Glasses
Meta AI glasses (e.g. Ray-Ban Meta, Meta Ray-Ban Display, Oakley Meta Vanguard, and Oakley Meta HSTN) support two of the Remote Assist capabilities: camera casting (the wearer's point-of-view feed) and two-way audio. Screen casting and device audio playback do not apply, since the glasses have no screen.
Unlike headsets, Meta AI glasses are not managed by ArborXR directly. They connect to ArborXR as peripherals of an Android phone they are paired to, and appear under a Meta Wearables tab on that phone, plus a blue glasses icon next to the phone in the Devices list.
💡 For the full step-by-step guide on adding Meta AI glasses to ArborXR, see Add Meta AI glasses to ArborXR for Remote Assist.
Start a Remote Assistance session on Meta AI glasses:
From the phone's device page: click Remote Control & Assist, then select Cast [your glasses model].
From the Devices table: click the blue glasses icon next to the phone, then in the Paired Wearables section click Assist, then Cast + Two-Way Audio.
💡 The first time you assist a given pair of glasses, the Meta AI app prompts the wearer on the phone (not the glasses) to allow ArborXR to access the camera. Tap Always allow, then Confirm, to suppress the prompt on future sessions. When session consent is required, that prompt also appears on the phone rather than the glasses.
