> This is part 1 of 2 of the full documentation (pages 1–100 of 162).
> The content is paginated: fetch every part to see all of it.
> Next part: https://kb.mago.io/llms-full.txt/1
> Page index: https://kb.mago.io/llms.txt

# Setup Guide

Find guides, tutorials, and troubleshooting articles to install, configure, and optimize your Mago devices and software in the official Mago Knowledge Base.

## Select your room experience before you start

Mago turns any room into a modern meeting space. Before installing, it's worth taking a moment to decide how your room will be used. This determines the hardware requirements, the video conferencing licenses involved, and the steps you'll follow.

The two available experiences are BYOM only and Room System (includes BYOM), each suited to different scenarios and levels of room autonomy.

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th></th><th></th><th align="center"></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><h3>BYOM</h3><p>Bring Your Own Meeting</p></td><td>With BYOM (Bring Your Own Meeting), a user device, laptop or mobile, connects to the room to start and manage meetings. The room relies on the user's device for meeting launch and control.</td><td><strong>Best for:</strong> flexible spaces, hot-desking rooms, or quick rollouts where no dedicated room identity is needed.</td><td align="center"><a href="/mago/setup-guide/byom">Go to BYOM Setup Guide</a></td><td><a href="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FMW61wROo7zy8SZzwdt2M%2Fmago-byom.jpg?alt=media&amp;token=5ad35a18-d830-4fb0-97e3-6272920577c7">mago-byom.jpg</a></td><td><a href="/mago/setup-guide/byom">BYOM</a></td></tr><tr><td align="center"><h3>Room System + BYOM</h3><p>Room as a host</p></td><td>With Room System, the room has its own identity and can start, host, and manage meetings independently via a touch controller and calendar integration. BYOM is still supported: users can connect their device and take control if needed.</td><td><strong>Best for:</strong> dedicated meeting rooms with high utilization, rooms that need to be bookable via calendar, or scenarios where meetings should start without a user device.</td><td align="center"><a href="/mago/setup-guide/room-system">Go to Room System Setup Guide</a></td><td><a href="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F1TLO13G9GjVt0IhCLCMQ%2Fmago-roomsystem.jpg?alt=media&amp;token=2f7973a4-ea6a-4b6c-9c0b-1f2ab6a88a2d">mago-roomsystem.jpg</a></td><td><a href="/mago/setup-guide/room-system">Room System</a></td></tr></tbody></table>

## Not sure which one you need?

<table><thead><tr><th valign="middle"></th><th align="center">BYOM only</th><th align="center" valign="middle">Room System</th></tr></thead><tbody><tr><td valign="middle">Requires user device (laptop or mobile) to start a meeting</td><td align="center"><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td align="center" valign="middle">❌</td></tr><tr><td valign="middle">Requires touch controller (or Interactive Flat Panel)</td><td align="center">❌</td><td align="center" valign="middle">✅</td></tr><tr><td valign="middle">Room Calendar integration</td><td align="center">❌</td><td align="center" valign="middle">✅</td></tr><tr><td valign="middle">Room can host meetings independently</td><td align="center">❌</td><td align="center" valign="middle">✅</td></tr></tbody></table>


# BYOM

With Mago configured as BYOM (Bring Your Own Meeting), the room relies on a user device to start and manage meetings. When a user enters the room, they connect their laptop or mobile to the room system, which provides the display, audio, and video. No room identity, calendar, or dedicated video conferencing license is required.

### Choose your hardware

Select your room hardware to get started with the installation.

<table><thead><tr><th width="206.703125">Hardware</th><th width="289.640625">→ Go to</th><th>OS</th><th>Display</th><th>AV peripherals</th></tr></thead><tbody><tr><td><strong>Windows (PC / OPS)</strong></td><td><a data-mention href="/mago/setup-guide/byom/install-on-windows">Install on Windows</a></td><td>Windows 11</td><td>External, passive or interactive</td><td>USB (camera, mic, speaker)</td></tr><tr><td><strong>Neat Bar Gen 2,</strong><br><strong>Neat Bar Pro</strong></td><td><a data-mention href="/mago/setup-guide/byom/install-on-neat-neat-pulse">Install on Neat (Neat Pulse)</a></td><td>Neat OS (Neat Pulse)</td><td>External, passive</td><td>Integrated in the bar</td></tr><tr><td><strong>Neat Board 50,</strong><br><strong>Neat Board Pro</strong></td><td><a data-mention href="/mago/setup-guide/byom/install-on-neat-neat-pulse">Install on Neat (Neat Pulse)</a></td><td>Neat OS (Neat Pulse)</td><td>Integrated, interactive</td><td>Integrated in the board</td></tr><tr><td><strong>All-in-One Interactive Flat Panel</strong></td><td><a data-mention href="/mago/setup-guide/byom/install-on-android-all-in-one-interactive-flat-panel">Install on Android (All-in-One Interactive Flat Panel)</a></td><td>Android</td><td>Integrated, interactive</td><td>Integrated in the unit</td></tr><tr><td><strong>Android Display,</strong><br><strong>Smart TV</strong></td><td><a data-mention href="/mago/setup-guide/byom/install-on-android-display-smart-tv">Install on Android (Display / Smart TV)</a></td><td>Android, GoogleTV, FireTV</td><td>Integrated, passive</td><td>USB (camera, mic, speaker)</td></tr></tbody></table>


# Install on Windows

With BYOM, Mago runs on a Windows device connected to a passive or interactive display. Users connect their laptop or mobile to start and manage meetings. No calendar integration or room license is required.

### Installation steps

{% stepper %}
{% step %}

### Check hardware and peripherals

You will use a certified Windows device from the Certified [Windows Devices](/mago/certified-devices/windows-devices) list, or your own Windows hardware that meets the minimum specifications. Connect the display via HDMI or DisplayPort and attach all USB audio and video peripherals (camera, microphone, speaker) before launching Mago so they are detected correctly on first startup.
{% endstep %}

{% step %}

### Prepare the network

Connect the device to wired Gigabit Ethernet. Verify that the connection provides at least 2 Mbps of internet bandwidth. Configure firewall rules and FQDN allowlisting according to the [Network](/mago/requirements/network) requirements. Proxy connections are not supported.
{% endstep %}

{% step %}

### Prepare wireless screen sharing

Mago on Windows supports two wireless screen sharing methods:

**Mago Link** allows any user to share their screen by visiting [magolink.com](https://magolink.com) from a browser on their laptop or mobile. No app install is required. Verify that the network meets the requirements described in [Mago Link](/mago/requirements/presentation/wireless-screen-sharing/mago-link).

**Native screen sharing** is available via **Miracast**, **Google Cast**, and **AirPlay** directly from the operating system of the user device. All methods are installed automatically with Mago and do not require additional software. However, the network must be configured to allow mDNS and multicast traffic for device discovery. Verify that these requirements are met before proceeding. See [Wireless Screen Sharing](/mago/requirements/presentation/wireless-screen-sharing).
{% endstep %}

{% step %}

### Prepare video conferencing

By default, Mago joins meetings **as a guest** with no additional setup.

If BYOM users should join as **authenticated participants**, bypassing the lobby and appearing with their own identity, additional configuration is required depending on the provider.&#x20;

Complete the steps for each provider that applies to your deployment.

{% tabs %}
{% tab title="Microsoft Teams" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest and always goes to the lobby. No additional setup is required.

**User Join (BYOM Authenticated Calls)**

To enable User Join (BYOM Authenticated Calls), which allow users to bypass the lobby and appear with their own identity, you will need to:

* Authorize the **Mago app** in your organization. Follow this link to add the Mago app and grant admin consent: [Microsoft 365](/mago/requirements/third-party-providers/microsoft-365)
* Install the **Azure Communication Services service principal** in the tenant. Follow this guide to setup the ACS service: [Authenticated Calls with Microsoft Teams](/mago/requirements/video-conferencing/authenticated-calls/authenticated-calls-with-microsoft-teams)

Each user who connects with their device will also require a Microsoft Teams license.

{% hint style="info" %}
Each user will sign in with their video call provider account in the Mago app on their personal device, and their authenticated identity is passed automatically to the room when connected.
{% endhint %}

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FyZ2AQqffwo7VZsETNSXL%2Fbyom-setup-auth.jpg?alt=media&amp;token=dd33895d-9f4c-48a3-8118-1331f52eb10f" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Zoom" %}
**Guest Join (ID and Passcode)**

{% hint style="warning" %}
Since March 2026, Zoom no longer allows unauthenticated participants to join meetings from room systems.
{% endhint %}

* A Zoom account is required for all join modes, including Guest Join. Any Zoom account type is supported (Free, Pro, Business, Enterprise). Have the Zoom account credentials ready, as they will be entered during the activation wizard.
* The "Mago Room" app from the Zoom Marketplace must also be approved on the Zoom tenant or on the individual user account. See [Zoom](/mago/requirements/third-party-providers/zoom) for the approval procedure.

**User Join (BYOM Authenticated Calls)**

{% hint style="info" %}
Coming soon
{% endhint %}
{% endtab %}

{% tab title="Webex" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.

**User Join (BYOM Authenticated Calls)**

{% hint style="info" %}
Coming soon
{% endhint %}
{% endtab %}

{% tab title="Google Meet" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Prepare Windows

If you are using a certified Mago Core device, it comes with Mago pre-installed and you can skip to the next step.

If you are using your own Windows hardware, follow the full preparation procedure described in [How to Prepare Your Own Windows Hardware](/mago/certified-devices/windows-devices/how-to-prepare-your-own-windows-hardware). This includes a fresh installation of Windows 11, system updates, power and display configuration, removal of unnecessary components, Mago installation, and Mago user configuration. Once the preparation is complete, continue with the next step.

{% hint style="danger" %}
Do not use vendor images such as Microsoft Teams Rooms or Zoom Rooms, as these are not supported.
{% endhint %}
{% endstep %}

{% step %}

### Sign in or Sign up to Mago Admin Center

If you do not already have an account, register at [admin.mago.io](https://admin.mago.io). You will also need a valid Mago license key. If you do not have one, you can select a free trial during device activation.
{% endstep %}

{% step %}

### Install Mago

{% hint style="info" %}
If you already completed the [How to Prepare Your Own Windows Hardware](/mago/certified-devices/windows-devices/how-to-prepare-your-own-windows-hardware), Mago is installed and you can skip to the next step.
{% endhint %}

If you are using a certified Windows device, download the Mago installer from [admin.mago.io/download-software](https://admin.mago.io/download-software) and run it on the device. During installation, Mago creates a dedicated Windows user account named "Mago" configured for automatic logon. Do not run Mago from an administrator account or any other Windows profile.

For large-scale rollouts, Mago can also be deployed silently via Intune, SCCM, or PDQ Deploy. See [How to Install Using Software Distribution (Silent Install)](/mago/certified-devices/windows-devices/deploy-valarea-pod-with-software-distribution-silent-install).
{% endstep %}

{% step %}

### Activate the device and complete the setup wizard

On first launch, Mago displays an activation screen with a QR code or a 6-digit code. Open [admin.mago.io](https://admin.mago.io) in a browser, go to Devices > Activate, and follow the on-screen steps to activate. Name the device when prompted. The device will appear under Devices in the Admin Center once activation is complete.

During the activation wizard, complete the following configuration steps.

* *Skip calendar setup.* BYOM does not use a room calendar. Skip the calendar configuration step when prompted.
* *Configure video call providers.* For each video conferencing provider you plan to use (Microsoft Teams, Zoom, Cisco Webex, Google Meet, Mago Meet), enable Guest Join with meeting ID and Passcode. Connect the provider account where required (Zoom).
  {% endstep %}

{% step %}

### Configure policies

In Mago Admin Center, go to Policies and create or assign a policy for the device. Configure appearance, device settings, and any restrictions as needed. The device will update over the air.
{% endstep %}

{% step %}

### Verify

* Confirm date and time are correct
* Verify network connectivity
* Test wireless screen sharing
* Test USB peripherals

{% hint style="success" %}
The room is now ready for BYOM use!
{% endhint %}
{% endstep %}
{% endstepper %}


# Install on Neat (Neat Pulse)

With BYOM, Mago runs on a Neat device managed via Neat Pulse. Users connect their laptop or mobile to start and manage meetings. No calendar integration or room license is required.

### Installation steps

{% stepper %}
{% step %}

### Check hardware and peripherals

You will use a Neat Bar or Neat Bar Pro connected to a passive external display via HDMI, or a Neat Board or Neat Board Pro with integrated display and AV peripherals. See [Neat Devices](/mago/certified-devices/neat-devices) for the list of certified Neat devices.
{% endstep %}

{% step %}

### Prepare the network

Connect the device to wired Gigabit Ethernet. Verify that the connection provides at least 2 Mbps of internet bandwidth. Configure firewall rules and FQDN allowlisting according to the [Network](/mago/requirements/network) requirements. Proxy connections are not supported.
{% endstep %}

{% step %}

### Prepare wireless screen sharing

**Mago Link** allows any user to share their screen by visiting [magolink.com](https://magolink.com) from a browser on their laptop or mobile. No app install is required. Verify that the network meets the requirements described in [Mago Link](/mago/requirements/presentation/wireless-screen-sharing/mago-link).
{% endstep %}

{% step %}

### Prepare video conferencing

By default, Mago joins meetings **as a guest** with no additional setup.

If BYOM users should join as **authenticated participants**, bypassing the lobby and appearing with their own identity, additional configuration is required depending on the provider.&#x20;

Complete the steps for each provider that applies to your deployment.

{% tabs %}
{% tab title="Microsoft Teams" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest and always goes to the lobby. No additional setup is required.

**User Join (BYOM Authenticated Calls)**

To enable User Join (BYOM Authenticated Calls), which allow users to bypass the lobby and appear with their own identity, you will need to:

* Authorize the **Mago app** in your organization. Follow this link to add the Mago app and grant admin consent: [Microsoft 365](/mago/requirements/third-party-providers/microsoft-365)
* Install the **Azure Communication Services service principal** in the tenant. Follow this guide to setup the ACS service: [Authenticated Calls with Microsoft Teams](/mago/requirements/video-conferencing/authenticated-calls/authenticated-calls-with-microsoft-teams)

Each user who connects with their device will also require a Microsoft Teams license.

{% hint style="info" %}
Each user will sign in with their video call provider account in the Mago app on their personal device, and their authenticated identity is passed automatically to the room when connected.
{% endhint %}

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FyZ2AQqffwo7VZsETNSXL%2Fbyom-setup-auth.jpg?alt=media&amp;token=dd33895d-9f4c-48a3-8118-1331f52eb10f" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Zoom" %}
**Guest Join (ID and Passcode)**

{% hint style="warning" %}
Since March 2026, Zoom no longer allows unauthenticated participants to join meetings from room systems.
{% endhint %}

* A Zoom account is required for all join modes, including Guest Join. Any Zoom account type is supported (Free, Pro, Business, Enterprise). Have the Zoom account credentials ready, as they will be entered during the activation wizard.
* The "Mago Room" app from the Zoom Marketplace must also be approved on the Zoom tenant or on the individual user account. See [Zoom](/mago/requirements/third-party-providers/zoom) for the approval procedure.

**User Join (BYOM Authenticated Calls)**

{% hint style="info" %}
Coming soon
{% endhint %}
{% endtab %}

{% tab title="Webex" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.

**User Join (BYOM Authenticated Calls)**

{% hint style="info" %}
Coming soon
{% endhint %}
{% endtab %}

{% tab title="Google Meet" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Enroll the device in Neat Pulse

Make sure the Neat device is already enrolled in your Neat Pulse account. If it is not, follow the Neat onboarding flow to add it before proceeding. See <https://neat.no/pulse/>
{% endstep %}

{% step %}

### Install Mago from Neat AppHub

On your Neat device, open the Neat Pulse management portal and navigate to the AppHub. Search for Mago and install it. Alternatively, you can push the app remotely to one or more devices directly from Neat Pulse.
{% endstep %}

{% step %}

### Grant required permissions

On first launch, Mago will request permissions for microphone, camera, networking, and local discovery. Grant all permissions when prompted. These are required for video conferencing, pairing, and screen sharing to function correctly.
{% endstep %}

{% step %}

### Sign in or Sign up to Mago Admin Center

If you do not already have an account, register at [admin.mago.io](https://admin.mago.io). You will also need a valid Mago license key. If you do not have one, you can select a free trial during device activation.
{% endstep %}

{% step %}

### Activate the device and complete the setup wizard

On first launch, Mago displays an activation screen with a QR code or a 6-digit code. Open [admin.mago.io](https://admin.mago.io) in a browser, go to Devices > Activate, and follow the on-screen steps to activate. Name the device when prompted. The device will appear under Devices in the Admin Center once activation is complete.

During the activation wizard, complete the following configuration steps.

* *Skip calendar setup.* BYOM does not use a room calendar. Skip the calendar configuration step when prompted.
* *Configure video call providers.* For each video conferencing provider you plan to use (Microsoft Teams, Zoom, Cisco Webex, Google Meet, Mago Meet), enable Guest Join with meeting ID and passcode. For Zoom, an account is required.
  {% endstep %}

{% step %}

### Configure policies

In Mago Admin Center, go to Policies and create or assign a policy for the device. Configure appearance, device settings, and any restrictions as needed. The device will update over the air.
{% endstep %}

{% step %}

### Verify

* Confirm date and time are correct
* Verify network connectivity
* Test wireless screen sharing
* Test AV peripherals

{% hint style="success" %}
The room is now ready for BYOM use!
{% endhint %}
{% endstep %}
{% endstepper %}


# Install on Android (All-in-One Interactive Flat Panel)

With BYOM, Mago runs natively on an Android interactive all-in-one device. The display, camera, microphone, and speaker are integrated in the unit. Users connect their laptop or mobile to start and manage meetings. No calendar integration or room license is required.

### Installation steps

{% stepper %}
{% step %}

### Check hardware and peripherals

Verify that your device is on the [Android All-in-One Interactive Flat Panels](/mago/certified-devices/android-all-in-one-interactive-flat-panels) devices list.
{% endstep %}

{% step %}

### Prepare the network

Connect the device to wired Gigabit Ethernet. Verify that the connection provides at least 2 Mbps of internet bandwidth. Configure firewall rules and FQDN allowlisting according to the [Network](/mago/requirements/network) requirements. Proxy connections are not supported.
{% endstep %}

{% step %}

### Prepare wireless screen sharing

**Mago Link** allows any user to share their screen by visiting [magolink.com](https://magolink.com) from a browser on their laptop or mobile. No app install is required. Verify that the network meets the requirements described in [Mago Link](/mago/requirements/presentation/wireless-screen-sharing/mago-link).
{% endstep %}

{% step %}

### Prepare video conferencing

By default, Mago joins meetings **as a guest** with no additional setup.

If BYOM users should join as **authenticated participants**, bypassing the lobby and appearing with their own identity, additional configuration is required depending on the provider.&#x20;

Complete the steps for each provider that applies to your deployment.

{% tabs %}
{% tab title="Microsoft Teams" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest and always goes to the lobby. No additional setup is required.

**User Join (BYOM Authenticated Calls)**

To enable User Join (BYOM Authenticated Calls), which allow users to bypass the lobby and appear with their own identity, you will need to:

* Authorize the **Mago app** in your organization. Follow this link to add the Mago app and grant admin consent: [Microsoft 365](/mago/requirements/third-party-providers/microsoft-365)
* Install the **Azure Communication Services service principal** in the tenant. Follow this guide to setup the ACS service: [Authenticated Calls with Microsoft Teams](/mago/requirements/video-conferencing/authenticated-calls/authenticated-calls-with-microsoft-teams)

Each user who connects with their device will also require a Microsoft Teams license.

{% hint style="info" %}
Each user will sign in with their video call provider account in the Mago app on their personal device, and their authenticated identity is passed automatically to the room when connected.
{% endhint %}

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FyZ2AQqffwo7VZsETNSXL%2Fbyom-setup-auth.jpg?alt=media&amp;token=dd33895d-9f4c-48a3-8118-1331f52eb10f" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Zoom" %}
**Guest Join (ID and Passcode)**

{% hint style="warning" %}
Since March 2026, Zoom no longer allows unauthenticated participants to join meetings from room systems.
{% endhint %}

* A Zoom account is required for all join modes, including Guest Join. Any Zoom account type is supported (Free, Pro, Business, Enterprise). Have the Zoom account credentials ready, as they will be entered during the activation wizard.
* The "Mago Room" app from the Zoom Marketplace must also be approved on the Zoom tenant or on the individual user account. See [Zoom](/mago/requirements/third-party-providers/zoom) for the approval procedure.

**User Join (BYOM Authenticated Calls)**

{% hint style="info" %}
Coming soon
{% endhint %}
{% endtab %}

{% tab title="Webex" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.

**User Join (BYOM Authenticated Calls)**

{% hint style="info" %}
Coming soon
{% endhint %}
{% endtab %}

{% tab title="Google Meet" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Install Mago

{% hint style="info" %}
Some All-in-One Interactive Flat Panels come with Mago pre-installed by the manufacturer. Check with your device vendor before proceeding. If Mago is already present, skip the installation and launch the app directly.
{% endhint %}

If Mago is not pre-installed, install it using one of the following methods depending on what is available on your device:

* **Google Play Store** — available on GoogleTV and AndroidTV devices, search for "Mago for Display" and install (Google Play store link [here](https://play.google.com/store/apps/details?id=com.remago.receiver))
* **Amazon Appstore** — available on FireTV devices, search for "Mago for Display" and install (Amazon Appstore link [here](https://www.amazon.com/gp/product/B0F19DGJB2))
* **Direct APK** — download the APK from [admin.mago.io/download-software](https://admin.mago.io/download-software) and sideload it on the device

After installation, launch the Mago app.
{% endstep %}

{% step %}

### Grant required permissions

On first launch, Mago will request permissions for microphone, camera, networking, local discovery, and display over other apps. Grant all permissions when prompted. You can review permissions later via Settings → Apps → Mago → Permissions.
{% endstep %}

{% step %}

### Disable "Pause app activity if unused"

Android may automatically restrict apps that have not been used recently, revoking permissions or suspending background services. To prevent this from interrupting screen sharing, pairing, or meeting startup, disable this option on the device via Settings → Apps → Mago.
{% endstep %}

{% step %}

### Sign in or Sign up to Mago Admin Center

If you do not already have an account, register at [admin.mago.io](https://admin.mago.io). You will also need a valid Mago license key. If you do not have one, you can select a free trial during device activation.
{% endstep %}

{% step %}

### Activate the device and complete the setup wizard

On first launch, Mago displays an activation screen with a QR code or a 6-digit code. Open [admin.mago.io](https://admin.mago.io) in a browser, go to Devices > Activate, and follow the on-screen steps to activate. Name the device when prompted. The device will appear under Devices in the Admin Center once activation is complete.

During the activation wizard, complete the following configuration steps.

* *Skip calendar setup.* BYOM does not use a room calendar. Skip the calendar configuration step when prompted.
* *Configure video call providers.* For each video conferencing provider you plan to use (Microsoft Teams, Zoom, Cisco Webex, Google Meet, Mago Meet), enable Guest Join with meeting ID and Passcode. For Zoom, an account is required.
  {% endstep %}

{% step %}

### Configure policies

In Mago Admin Center, go to Policies and create or assign a policy for the device. Configure appearance, device settings, and any restrictions as needed. The device will update over the air.
{% endstep %}

{% step %}

### Verify

* Confirm date and time are correct
* Verify network connectivity
* Test wireless screen sharing
* Test AV peripherals

{% hint style="success" %}
The room is now ready for BYOM use!
{% endhint %}
{% endstep %}
{% endstepper %}


# Install on Android (Display / Smart TV)

With BYOM, Mago runs on an Android display or Smart TV connected to USB audio and video peripherals. Users connect their laptop or mobile to start and manage meetings. No calendar integration or room license is required.

### Installation steps

{% stepper %}
{% step %}

### Check hardware and peripherals

Verify that your device is on the [Android Displays / Smart TVs](/mago/certified-devices/android-displays-smart-tvs) devices list.
{% endstep %}

{% step %}

### Prepare the network

Connect the device to wired Gigabit Ethernet. Verify that the connection provides at least 2 Mbps of internet bandwidth. Configure firewall rules and FQDN allowlisting according to the [Network](/mago/requirements/network) requirements. Proxy connections are not supported.
{% endstep %}

{% step %}

### Prepare wireless screen sharing

**Mago Link** allows any user to share their screen by visiting [magolink.com](https://magolink.com) from a browser on their laptop or mobile. No app install is required. Verify that the network meets the requirements described in [Mago Link](/mago/requirements/presentation/wireless-screen-sharing/mago-link).
{% endstep %}

{% step %}

### Prepare video conferencing

By default, Mago joins meetings **as a guest** with no additional setup.

If BYOM users should join as **authenticated participants**, bypassing the lobby and appearing with their own identity, additional configuration is required depending on the provider.&#x20;

Complete the steps for each provider that applies to your deployment.

{% tabs %}
{% tab title="Microsoft Teams" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest and always goes to the lobby. No additional setup is required.

**User Join (BYOM Authenticated Calls)**

To enable User Join (BYOM Authenticated Calls), which allow users to bypass the lobby and appear with their own identity, you will need to:

* Authorize the **Mago app** in your organization. Follow this link to add the Mago app and grant admin consent: [Microsoft 365](/mago/requirements/third-party-providers/microsoft-365)
* Install the **Azure Communication Services service principal** in the tenant. Follow this guide to setup the ACS service: [Authenticated Calls with Microsoft Teams](/mago/requirements/video-conferencing/authenticated-calls/authenticated-calls-with-microsoft-teams)

Each user who connects with their device will also require a Microsoft Teams license.

{% hint style="info" %}
Each user will sign in with their video call provider account in the Mago app on their personal device, and their authenticated identity is passed automatically to the room when connected.
{% endhint %}

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FyZ2AQqffwo7VZsETNSXL%2Fbyom-setup-auth.jpg?alt=media&amp;token=dd33895d-9f4c-48a3-8118-1331f52eb10f" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Zoom" %}
**Guest Join (ID and Passcode)**

{% hint style="warning" %}
Since March 2026, Zoom no longer allows unauthenticated participants to join meetings from room systems.
{% endhint %}

* A Zoom account is required for all join modes, including Guest Join. Any Zoom account type is supported (Free, Pro, Business, Enterprise). Have the Zoom account credentials ready, as they will be entered during the activation wizard.
* The "Mago Room" app from the Zoom Marketplace must also be approved on the Zoom tenant or on the individual user account. See [Zoom](/mago/requirements/third-party-providers/zoom) for the approval procedure.

**User Join (BYOM Authenticated Calls)**

{% hint style="info" %}
Coming soon
{% endhint %}
{% endtab %}

{% tab title="Webex" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.

**User Join (BYOM Authenticated Calls)**

{% hint style="info" %}
Coming soon
{% endhint %}
{% endtab %}

{% tab title="Google Meet" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Sign in or Sign up to Mago Admin Center

If you do not already have an account, register at [admin.mago.io](https://admin.mago.io). You will also need a valid Mago license key. If you do not have one, you can select a free trial during device activation.
{% endstep %}

{% step %}

### Install Mago

If Mago is not pre-installed, install it using one of the following methods depending on what is available on your device:

* **Google Play Store** — available on GoogleTV and AndroidTV devices, search for "Mago for Display" and install (Google Play store link [here](https://play.google.com/store/apps/details?id=com.remago.receiver))
* **Amazon Appstore** — available on FireTV devices, search for "Mago for Display" and install (Amazon Appstore link [here](https://www.amazon.com/gp/product/B0F19DGJB2))
* **Direct APK** — download the APK from [admin.mago.io/download-software](https://admin.mago.io/download-software) and sideload it on the device

After installation, launch the Mago app.
{% endstep %}

{% step %}

### Grant required permissions

On first launch, Mago will request permissions for microphone, camera, networking, local discovery, and display over other apps. Grant all permissions when prompted. You can review permissions later via Settings → Apps → Mago → Permissions.
{% endstep %}

{% step %}

### Disable "Pause app activity if unused"

Android may automatically restrict apps that have not been used recently, revoking permissions or suspending background services. To prevent this from interrupting screen sharing, pairing, or meeting startup, disable this option on the device via Settings → Apps → Mago.
{% endstep %}

{% step %}

### Activate the device and complete the setup wizard

On first launch, Mago displays an activation screen with a QR code or a 6-digit code. Open [admin.mago.io](https://admin.mago.io) in a browser, go to Devices > Activate, and follow the on-screen steps to activate. Name the device when prompted. The device will appear under Devices in the Admin Center once activation is complete.

During the activation wizard, complete the following configuration steps.

* *Skip calendar setup.* BYOM does not use a room calendar. Skip the calendar configuration step when prompted.
* *Configure video call providers.* For each video conferencing provider you plan to use (Microsoft Teams, Zoom, Cisco Webex, Google Meet, Mago Meet), enable Guest Join with meeting ID and Passcode. For Zoom, an account is required.
  {% endstep %}

{% step %}

### Configure policies

In Mago Admin Center, go to Policies and create or assign a policy for the device. Configure appearance, device settings, and any restrictions as needed. The device will update over the air.
{% endstep %}

{% step %}

### Verify

* Confirm date and time are correct
* Verify network connectivity
* Test wireless screen sharing
* Test AV peripherals

{% hint style="success" %}
The room is now ready for BYOM use!
{% endhint %}
{% endstep %}
{% endstepper %}


# Room System

With Mago configured as Room System, the room has its own identity and can start, host, and manage meetings independently via a Touch Controller and Calendar integration. BYOM is still supported. Users can connect via the Mago app on their laptop or mobile to transfer their identity and take control of the meeting if needed.

### Choose your hardware

Select your room hardware to get started with the installation.

<table><thead><tr><th width="198.8359375">Hardware</th><th width="290.0703125">→ Go to</th><th>OS</th><th>Display</th><th>AV peripherals</th></tr></thead><tbody><tr><td><strong>Windows (PC / OPS)</strong></td><td><a data-mention href="/mago/setup-guide/room-system/install-on-windows">Install on Windows</a></td><td>Windows 11</td><td>External, passive or interactive</td><td>USB (camera, mic, speaker)</td></tr><tr><td><strong>Neat Bar Gen 2,</strong><br><strong>Neat Bar Pro</strong></td><td><a data-mention href="/mago/setup-guide/room-system/install-on-neat-neat-pulse">Install on Neat (Neat Pulse)</a></td><td>Neat OS (Neat Pulse)</td><td>External, passive</td><td>Integrated in the bar</td></tr><tr><td><strong>Neat Board 50,</strong><br><strong>Neat Board Pro</strong></td><td><a data-mention href="/mago/setup-guide/room-system/install-on-neat-neat-pulse">Install on Neat (Neat Pulse)</a></td><td>Neat OS (Neat Pulse)</td><td>Integrated, interactive</td><td>Integrated in the board</td></tr><tr><td><strong>All-in-One Interactive Flat Panel</strong></td><td><a data-mention href="/mago/setup-guide/room-system/install-on-android-all-in-one-interactive-flat-panel">Install on Android (All-in-One Interactive Flat Panel)</a></td><td>Android</td><td>Integrated, interactive</td><td>Integrated in the unit</td></tr><tr><td><strong>Android Display,</strong><br><strong>Smart TV</strong></td><td><a data-mention href="/mago/setup-guide/room-system/install-on-android-display-smart-tv">Install on Android (Display / Smart TV)</a></td><td>Android, GoogleTV, FireTV</td><td>Integrated, passive</td><td>USB (camera, mic, speaker)</td></tr></tbody></table>


# Install on Windows

With Room System, Mago turns a Windows device into a fully independent meeting room. The room calendar is displayed on screen, meetings can be joined or started with a single tap, and a wired or wireless touch controller lets anyone in the room manage the session.

### Installation steps

{% stepper %}
{% step %}

### Check hardware and peripherals

You will use a certified Windows device from the Certified [Windows Devices](/mago/certified-devices/windows-devices) list, or your own Windows hardware that meets the minimum specifications. Connect the display via HDMI or DisplayPort and attach all USB audio and video peripherals (camera, microphone, speaker) before launching Mago so they are detected correctly on first startup.
{% endstep %}

{% step %}

### Prepare the Touch Controller

**Wired Touch Controller**

Use a wired touch controller connected via USB / Ethernet (USB over IP) / PoE to the Windows device. See the full list of Certified Controllers here: [Wired touch controllers](/mago/certified-devices/windows-devices/wired-touch-controllers).&#x20;

**Wireless Touch Controller**

Alternatively, you can use an iPad (iPadOS 13+) or Android tablet (Android 10.0+, minimum resolution 1024x600) as a wireless touch controller by installing the Mago Controller app from the App Store or Google Play. See [Wireless touch controllers](/mago/requirements/wireless-touch-controllers) for instructions. The wireless touch controller tablet requires an active Wi-Fi internet connection.
{% endstep %}

{% step %}

### Prepare the network

Connect the device to wired Gigabit Ethernet. Verify that the connection provides at least 2 Mbps of internet bandwidth. Configure firewall rules and FQDN allowlisting according to the [Network](/mago/requirements/network) requirements. Proxy connections are not supported.
{% endstep %}

{% step %}

### Prepare wireless screen sharing

Mago on Windows supports two wireless screen sharing methods:

**Mago Link** allows any user to share their screen by visiting [magolink.com](https://magolink.com) from a browser on their laptop or mobile. No app install is required. Verify that the network meets the requirements described in [Mago Link](/mago/requirements/presentation/wireless-screen-sharing/mago-link).

**Native screen sharing** is available via **Miracast**, **Google Cast**, and **AirPlay** directly from the operating system of the user device. All methods are installed automatically with Mago and do not require additional software. However, the network must be configured to allow mDNS and multicast traffic for device discovery. Verify that these requirements are met before proceeding. See [Wireless Screen Sharing](/mago/requirements/presentation/wireless-screen-sharing).
{% endstep %}

{% step %}

### Authorize the Mago app in your organization

Before Mago can access **room calendars** and **video conferencing services** on behalf of your organization, a tenant administrator must grant consent to the Mago application in your identity or services provider, such as Microsoft 365 or Google Workspace.

This is a one-time operation that authorizes Mago to request the permissions it requires, such as reading calendar events and authenticating meeting participants.

{% hint style="warning" %}
Without this consent, devices will not be able to display room calendars or join meetings as authenticated participants.
{% endhint %}

Select your provider below and follow the setup steps.

{% tabs %}
{% tab title="Microsoft 365" %}
When using Mago with Microsoft 365 room resources and users, the Mago app for display and Mago mobile app access Microsoft 365 services through the Microsoft Graph and Azure Communication Services APIs. To enable these features, a tenant administrator must grant consent to the Mago enterprise application.

{% hint style="success" %}
Mago is a verified enterprise application in the **Microsoft Entra app gallery** (application ID `17781659-6867-4c77-9ba3-40670305181c)` and it is listed under the official **Azure Marketplace**.
{% endhint %}

#### Add the Mago application to your tenant

Open [admin.mago.io](https://admin.mago.io/) and sign in with a Microsoft 365 account that has **Global Administrator**, **Application Administrator**, or **Cloud Application Administrator privileges**. When prompted, review the requested permissions and select "Accept" on behalf of your organization. The Mago application is now registered in your tenant.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FSBktWH6jXKKddXFxxkng%2Fmago-admin-center-signin.jpg?alt=media&amp;token=c43b0523-dd1e-41c8-ad4f-3128de74f9f6" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FN9mgBPd1TFeHfU552urg%2Fmago-admin-consent.webp?alt=media&amp;token=e5c8903b-50cf-4b05-a05d-8cfe473e7949" alt="" width="375"><figcaption></figcaption></figure>

#### Grant admin consent to the required scopes

To review and grant admin consent to the required scopes in the Mago application permissions:

* Open the [**Azure portal**](https://portal.azure.com/) and sign in with a Microsoft 365 Administrator account.
* Go to Microsoft Entra ID > Enterprise Applications (or search directly for "**Enterprise Applications**").

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FiBdqVUpQpQSLQNL4Bkj2%2Fenterprise-apps.webp?alt=media&amp;token=bb4655ed-312c-4e3f-b80f-c39eb9fc2b96" alt=""><figcaption></figcaption></figure>

* Under the Application list, search for "**Mago**" (Application ID `17781659-6867-4c77-9ba3-40670305181c`).

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FWFi1wmwO2BlhLbgwTSM2%2Fenterprise-apps-mago.webp?alt=media&amp;token=d07d68d8-774a-43d5-af96-76624b67bc67" alt=""><figcaption></figcaption></figure>

* Enter the Mago application, go to **Security** > **Permissions** and verify that admin consent has been granted to the required scopes. To grant admin consent to all the required scopes, click the "Grant admin consent for *YourCompanyName*" button.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F5Hql2RRyQEziNdUZfP4Z%2Fenterprise-apps-mago-grant.webp?alt=media&amp;token=d6b8ad4b-6d29-468c-b84f-0830557e8703" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
See [Microsoft 365](/mago/requirements/third-party-providers/microsoft-365) for **Advanced consent options** and the full list of **Required features and scopes**.
{% endhint %}
{% endtab %}

{% tab title="Google Workspace" %}
When using Mago with Google Workspace room resources and users, the Mago app for display and Mago mobile app access Google services through Google APIs. To enable these features, a Google Workspace administrator must authorize the Mago application in the domain.

{% hint style="success" %}
Mago is a Google OAuth verified application.
{% endhint %}

#### Authorize the Mago application

Open [admin.mago.io](https://admin.mago.io/) and sign in with a Google Workspace account that has Super Admin privileges. When prompted, review the requested permissions and approve. The Mago application is now authorized in your domain.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FptqZeG1KKA7Q7fEhjAQB%2Fmago-admin-login.webp?alt=media&amp;token=1fc130ad-9776-40dc-a31a-fc435119cf84" alt="" width="351"><figcaption></figcaption></figure>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FInoQcmkioq9RJMDOtDjL%2Fmago-admin-center-google-signin.webp?alt=media&amp;token=ec711228-8371-4e61-b9a4-381cb93b3ea4" alt="" width="375"><figcaption></figcaption></figure>

#### Verify third-party app access and allow the Mago application if restricted

When room resources or users sign in later during device activation, Google will prompt them to approve additional scopes (such as calendar and meeting access).

{% hint style="warning" %}
If your domain restricts third-party application access, these prompts will be blocked with a **`400 admin_policy_enforced`** error.
{% endhint %}

#### Check third-party app access policy

To check if your domain restricts third-party application access:

* Open the [Google Admin console](https://admin.google.com/)
* Go to Security > Access and data control > **API controls**
* Click on **Settings**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FVI5V0TmYfaAJIY45So49%2Fgoogle-admin-8.webp?alt=media&amp;token=749f1b43-8521-432a-9807-d8fbd724d0a1" alt=""><figcaption></figcaption></figure>

* Under "Unconfigured third-party apps", verify which access level is selected. If it is set to "Allow users to access any third-party apps", no further action is required. If access is restricted, proceed with the next step to pre-authorize the Mago application at domain level.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FfFTtp3smBt53QIl3T0mn%2Fgoogle-admin-9.webp?alt=media&amp;token=bd3a67f7-3abe-4333-b1db-a8ce670196c0" alt=""><figcaption></figcaption></figure>

#### Pre-authorize the Mago application

If your domain restricts third-party application access:

* Open the [Google Admin console](https://admin.google.com/)
* Go to Security > Access and data control > API controls > **Manage App Access**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FLBO8JjSrXhwrYDA1ehyy%2Fgoogle-admin-1.webp?alt=media&amp;token=009551d7-3cf1-49fe-a4b0-a3017bd82321" alt=""><figcaption></figcaption></figure>

* Click on "Configure new app"

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2Fn9wVzHleirZv1yNKXlUO%2Fgoogle-admin-2.webp?alt=media&amp;token=bace8861-3ebd-4fb6-90d3-9c4d173d2dcd" alt=""><figcaption></figcaption></figure>

* Search for the following Mago app client IDs and add them as trusted app (one by one).

<table><thead><tr><th width="148.30078125">Application</th><th>Client ID</th></tr></thead><tbody><tr><td>Mago app for display / web</td><td><code>436832489008-nl03st57foo9su4qg5mddnadhl7ql5oe.apps.googleusercontent.com</code></td></tr><tr><td>Mago mobile app for Android</td><td><code>436832489008-5ie2c8hme7jucfh4vn4hul7sdkm8mhuk.apps.googleusercontent.com</code></td></tr><tr><td>Mago mobile app for iOS</td><td><code>436832489008-l3lejr6nqvgmevau7u999gm6c17jdci2.apps.googleusercontent.com</code></td></tr></tbody></table>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FDV0BTak78sohRm8CuHTU%2Fgoogle-admin-3.webp?alt=media&amp;token=640cf9e0-aa1c-4256-b7f2-38c523ae2e8f" alt=""><figcaption></figcaption></figure>

* Set your desired Scope and click **Continue**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FvACXSCMdnXaHQ3hwj7Mr%2Fgoogle-admin-4.webp?alt=media&amp;token=2a835ece-3797-4eb8-8e30-77feb62bba04" alt=""><figcaption></figcaption></figure>

* Set the app as **Trusted**, then click **Continue**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F5F0gatfqwQOSK73GFKlI%2Fgoogle-admin-5.webp?alt=media&amp;token=e7267572-68c7-476d-b975-5fee7fb8691e" alt=""><figcaption></figcaption></figure>

* Review and click **Finish**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FTuwZjSqWikY1JVFXHdpE%2Fgoogle-admin-6.webp?alt=media&amp;token=43656f5d-1749-4b55-b5db-dadeb013b3bb" alt=""><figcaption></figcaption></figure>

* Make sure to repeat the steps to configure all 3 Mago app client IDs.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FnXEy7r2WmJajKoenAsQk%2Fgoogle-admin-7.webp?alt=media&amp;token=db859a20-1821-444f-b82f-a28b6b06317b" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
This ensures that users and room resources are not blocked when Mago requests additional scopes (such as calendar access) during device activation or configuration.
{% endhint %}

{% hint style="info" %}
See [Google Workspace](/mago/requirements/third-party-providers/google-workspace) for the full list of **Required features and scopes**.
{% endhint %}
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Prepare the room resource and calendar

A room resource account is required for calendar integration and instant meeting hosting. Create and provision the account in your calendar provider before proceeding.

* **Microsoft 365** — create and provision a room resource account, grant the required OAuth scopes, and run the PowerShell command to correctly display meeting titles — see the full guide here: [Microsoft 365 calendar](/mago/requirements/calendar/microsoft-365-calendar)
* **Google Workspace** — create a service account for conference room calendars and configure resource delegation — see the full guide here: [Google Workspace calendar](/mago/requirements/calendar/google-workspace-calendar)
* **Microsoft Exchange on-premises** — create and provision service accounts and room resources — see the full guide here: [Microsoft Exchange calendar (On Premises)](/mago/requirements/calendar/microsoft-exchange-calendar-on-premises)
  {% endstep %}

{% step %}

### Prepare video conferencing

With Room System, the room has its own identity and can join meetings independently. The configuration depends on the video conferencing provider you plan to use. BYOM User Join is also available to users connected to the room. Complete the steps for each provider that applies to your deployment.

{% tabs %}
{% tab title="Microsoft Teams" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest and always goes to the lobby. No additional setup is required.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, you will configure the following:

* Install the **Azure Communication Services service principal** in the tenant
* Provision the room resource with a Microsoft Teams **license**

See [Authenticated Calls with Microsoft Teams](/mago/requirements/video-conferencing/authenticated-calls/authenticated-calls-with-microsoft-teams) for the full procedure.

**User Join (BYOM Authenticated Calls)**

Regardless of the room configuration, User Join (BYOM Authenticated Calls) is always available.

{% hint style="info" %}
When a user connects to the room with their personal device and starts a meeting, their user identity takes precedence over the room identity for the duration of the connection. Once the user disconnects, the room reverts to its own join mode.
{% endhint %}

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FTCtSK0GAuIvosfgjFF3h%2Frs-setup-auth.jpg?alt=media&amp;token=5dfa78cf-17c5-4822-bc44-32c7a5ff89e8" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Zoom" %}
**Guest Join (ID and Passcode)**

{% hint style="warning" %}
Since March 2026, Zoom no longer allows unauthenticated participants to join meetings from room systems.
{% endhint %}

* A Zoom account is required for all join modes, including Guest Join. Any Zoom account type is supported (Free, Pro, Business, Enterprise). Have the Zoom account credentials ready, as they will be entered during the activation wizard.
* The "Mago Room" app from the Zoom Marketplace must also be approved on the Zoom tenant or on the individual user account. See [Zoom](/mago/requirements/third-party-providers/zoom) for the approval procedure.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, you will assign the appropriate host license to the room resource Zoom account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}

{% tab title="Webex" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, a Webex account with host license is required (Free, Starter, Business, or Enterprise). Assign the appropriate license to the room resource account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}

{% tab title="Google Meet" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, a Google Workspace account is required (Free, Business Starter, Business Standard, Business Plus, or Enterprise). Assign the appropriate license to the room resource account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Prepare Windows

If you are using a certified Mago Core device, it comes with Mago pre-installed and you can skip to the next step.

If you are using your own Windows hardware, follow the full preparation procedure described in [How to Prepare Your Own Windows Hardware](/mago/certified-devices/windows-devices/how-to-prepare-your-own-windows-hardware). This includes a fresh installation of Windows 11, system updates, power and display configuration, removal of unnecessary components, Mago installation, and Mago user configuration. Once the preparation is complete, continue with the next step.

{% hint style="danger" %}
Do not use vendor images such as Microsoft Teams Rooms or Zoom Rooms, as these are not supported.
{% endhint %}
{% endstep %}

{% step %}

### Sign in or Sign up to Mago Admin Center

If you do not already have an account, register at [admin.mago.io](https://admin.mago.io). You will also need a valid Mago license key. If you do not have one, you can select a free trial during device activation.
{% endstep %}

{% step %}

### Install Mago

{% hint style="info" %}
If you already completed the [How to Prepare Your Own Windows Hardware](/mago/certified-devices/windows-devices/how-to-prepare-your-own-windows-hardware), Mago is installed and you can skip to the next step.
{% endhint %}

If you are using a certified Windows device, download the Mago installer from [admin.mago.io/download-software](https://admin.mago.io/download-software) and run it on the device. During installation, Mago creates a dedicated Windows user account named "Mago" configured for automatic logon. Do not run Mago from an administrator account or any other Windows profile.

For large-scale rollouts, Mago can also be deployed silently via Intune, SCCM, or PDQ Deploy. See [How to Install Using Software Distribution (Silent Install)](/mago/certified-devices/windows-devices/deploy-valarea-pod-with-software-distribution-silent-install).
{% endstep %}

{% step %}

### Activate the device and complete the setup wizard

On first launch, Mago displays an activation screen with a QR code or a 6-digit code. Open [admin.mago.io](https://admin.mago.io) in a browser, go to Devices > Activate, and follow the on-screen steps to activate. Name the device when prompted. The device will appear under Devices in the Admin Center once activation is complete.

During the activation wizard, complete the following configuration steps.

* *Connect the calendar.* Select the calendar provider (Microsoft 365 or Google Workspace) and connect the room resource account you prepared in Step 6. Complete the authentication flow and continue to the next step.
* *Configure video call providers.* For each video conferencing provider you plan to use (Microsoft Teams, Zoom, Cisco Webex, Google Meet, Mago Meet), enable the features that apply to your deployment: Guest Join with meeting ID and Passcode, Authenticated Calls, and Host Instant Meetings. The provider credentials and licenses you prepared in step 7 are required to complete this configuration.
  {% endstep %}

{% step %}

### Pair the Touch Controller

*Wired Touch Controller.* A wired controller is detected automatically as an extended display on Windows. No pairing is required. Open Mago Settings on the room PC, go to Display, and verify that the display configuration is correct. If the controller display is not assigned correctly, adjust the settings and recalibrate touch if necessary.

*Wireless Touch Controller.* On the iPad or Android tablet, open the Mago Controller app and follow the pairing instructions. The app discovers the room device automatically when both are on the same network. After pairing, the tablet displays the room calendar and meeting controls.
{% endstep %}

{% step %}

### Configure policies

In Mago Admin Center, go to Policies and create or assign a policy for the device. Configure appearance, device settings, and any restrictions as needed. The device will update over the air.
{% endstep %}

{% step %}

### Verify

* Confirm date and time are correct
* Verify network connectivity
* Test wireless screen sharing
* Test one-tap join from the touch controller
* Test USB peripherals

{% hint style="success" %}
The room is now ready for Room System use!
{% endhint %}
{% endstep %}
{% endstepper %}


# Install on Neat (Neat Pulse)

With Room System, Mago turns a Neat device into a fully independent meeting room. The room calendar is displayed on screen, meetings can be joined or started with a single tap, and a Neat Pad or Wireless Touch Controller lets anyone in the room manage the session.

### Installation steps

{% stepper %}
{% step %}

### Check hardware and peripherals

You will use a Neat Bar or Neat Bar Pro connected to a passive external display via HDMI, or a Neat Board or Neat Board Pro with integrated display and AV peripherals. See [Neat Devices](/mago/certified-devices/neat-devices) for the list of certified Neat devices.
{% endstep %}

{% step %}

### Prepare the Touch Controller

If you are using a Neat Bar Gen 2 with a Neat Pad, the Pad serves as the Touch Controller and no additional hardware is required.

If you are using a Neat Bar Gen 2 in BYOD mode without a Neat Pad, or a Neat Board (optionally), you will use an iPad (iPadOS 13+) or Android tablet (Android 10.0+, minimum resolution 1024x600) as a wireless Touch Controller. See [Wireless touch controllers](/mago/requirements/wireless-touch-controllers) for instructions. The wireless touch controller tablet requires an active Wi-Fi internet connection.
{% endstep %}

{% step %}

### Prepare the network

Connect the device to wired Gigabit Ethernet. Verify that the connection provides at least 2 Mbps of internet bandwidth. Configure firewall rules and FQDN allowlisting according to the [Network](/mago/requirements/network) requirements. Proxy connections are not supported.
{% endstep %}

{% step %}

### Prepare wireless screen sharing

**Mago Link** allows any user to share their screen by visiting [magolink.com](https://magolink.com) from a browser on their laptop or mobile. No app install is required. Verify that the network meets the requirements described in [Mago Link](/mago/requirements/presentation/wireless-screen-sharing/mago-link).
{% endstep %}

{% step %}

### Authorize the Mago app in your organization

Before Mago can access **room calendars** and **video conferencing services** on behalf of your organization, a tenant administrator must grant consent to the Mago application in your identity or services provider, such as Microsoft 365 or Google Workspace.

This is a one-time operation that authorizes Mago to request the permissions it requires, such as reading calendar events and authenticating meeting participants.

{% hint style="warning" %}
Without this consent, devices will not be able to display room calendars or join meetings as authenticated participants.
{% endhint %}

Select your provider below and follow the setup steps.

{% tabs %}
{% tab title="Microsoft 365" %}
When using Mago with Microsoft 365 room resources and users, the Mago app for display and Mago mobile app access Microsoft 365 services through the Microsoft Graph and Azure Communication Services APIs. To enable these features, a tenant administrator must grant consent to the Mago enterprise application.

{% hint style="success" %}
Mago is a verified enterprise application in the **Microsoft Entra app gallery** (application ID `17781659-6867-4c77-9ba3-40670305181c)` and it is listed under the official **Azure Marketplace**.
{% endhint %}

#### Add the Mago application to your tenant

Open [admin.mago.io](https://admin.mago.io/) and sign in with a Microsoft 365 account that has **Global Administrator**, **Application Administrator**, or **Cloud Application Administrator privileges**. When prompted, review the requested permissions and select "Accept" on behalf of your organization. The Mago application is now registered in your tenant.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FSBktWH6jXKKddXFxxkng%2Fmago-admin-center-signin.jpg?alt=media&amp;token=c43b0523-dd1e-41c8-ad4f-3128de74f9f6" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FN9mgBPd1TFeHfU552urg%2Fmago-admin-consent.webp?alt=media&amp;token=e5c8903b-50cf-4b05-a05d-8cfe473e7949" alt="" width="375"><figcaption></figcaption></figure>

#### Grant admin consent to the required scopes

To review and grant admin consent to the required scopes in the Mago application permissions:

* Open the [**Azure portal**](https://portal.azure.com/) and sign in with a Microsoft 365 Administrator account.
* Go to Microsoft Entra ID > Enterprise Applications (or search directly for "**Enterprise Applications**").

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FiBdqVUpQpQSLQNL4Bkj2%2Fenterprise-apps.webp?alt=media&amp;token=bb4655ed-312c-4e3f-b80f-c39eb9fc2b96" alt=""><figcaption></figcaption></figure>

* Under the Application list, search for "**Mago**" (Application ID `17781659-6867-4c77-9ba3-40670305181c`).

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FWFi1wmwO2BlhLbgwTSM2%2Fenterprise-apps-mago.webp?alt=media&amp;token=d07d68d8-774a-43d5-af96-76624b67bc67" alt=""><figcaption></figcaption></figure>

* Enter the Mago application, go to **Security** > **Permissions** and verify that admin consent has been granted to the required scopes. To grant admin consent to all the required scopes, click the "Grant admin consent for *YourCompanyName*" button.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F5Hql2RRyQEziNdUZfP4Z%2Fenterprise-apps-mago-grant.webp?alt=media&amp;token=d6b8ad4b-6d29-468c-b84f-0830557e8703" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
See [Microsoft 365](/mago/requirements/third-party-providers/microsoft-365) for **Advanced consent options** and the full list of **Required features and scopes**.
{% endhint %}
{% endtab %}

{% tab title="Google Workspace" %}
When using Mago with Google Workspace room resources and users, the Mago app for display and Mago mobile app access Google services through Google APIs. To enable these features, a Google Workspace administrator must authorize the Mago application in the domain.

{% hint style="success" %}
Mago is a Google OAuth verified application.
{% endhint %}

#### Authorize the Mago application

Open [admin.mago.io](https://admin.mago.io/) and sign in with a Google Workspace account that has Super Admin privileges. When prompted, review the requested permissions and approve. The Mago application is now authorized in your domain.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FptqZeG1KKA7Q7fEhjAQB%2Fmago-admin-login.webp?alt=media&amp;token=1fc130ad-9776-40dc-a31a-fc435119cf84" alt="" width="351"><figcaption></figcaption></figure>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FInoQcmkioq9RJMDOtDjL%2Fmago-admin-center-google-signin.webp?alt=media&amp;token=ec711228-8371-4e61-b9a4-381cb93b3ea4" alt="" width="375"><figcaption></figcaption></figure>

#### Verify third-party app access and allow the Mago application if restricted

When room resources or users sign in later during device activation, Google will prompt them to approve additional scopes (such as calendar and meeting access).

{% hint style="warning" %}
If your domain restricts third-party application access, these prompts will be blocked with a **`400 admin_policy_enforced`** error.
{% endhint %}

#### Check third-party app access policy

To check if your domain restricts third-party application access:

* Open the [Google Admin console](https://admin.google.com/)
* Go to Security > Access and data control > **API controls**
* Click on **Settings**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FVI5V0TmYfaAJIY45So49%2Fgoogle-admin-8.webp?alt=media&amp;token=749f1b43-8521-432a-9807-d8fbd724d0a1" alt=""><figcaption></figcaption></figure>

* Under "Unconfigured third-party apps", verify which access level is selected. If it is set to "Allow users to access any third-party apps", no further action is required. If access is restricted, proceed with the next step to pre-authorize the Mago application at domain level.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FfFTtp3smBt53QIl3T0mn%2Fgoogle-admin-9.webp?alt=media&amp;token=bd3a67f7-3abe-4333-b1db-a8ce670196c0" alt=""><figcaption></figcaption></figure>

#### Pre-authorize the Mago application

If your domain restricts third-party application access:

* Open the [Google Admin console](https://admin.google.com/)
* Go to Security > Access and data control > API controls > **Manage App Access**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FLBO8JjSrXhwrYDA1ehyy%2Fgoogle-admin-1.webp?alt=media&amp;token=009551d7-3cf1-49fe-a4b0-a3017bd82321" alt=""><figcaption></figcaption></figure>

* Click on "Configure new app"

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2Fn9wVzHleirZv1yNKXlUO%2Fgoogle-admin-2.webp?alt=media&amp;token=bace8861-3ebd-4fb6-90d3-9c4d173d2dcd" alt=""><figcaption></figcaption></figure>

* Search for the following Mago app client IDs and add them as trusted app (one by one).

<table><thead><tr><th width="148.30078125">Application</th><th>Client ID</th></tr></thead><tbody><tr><td>Mago app for display / web</td><td><code>436832489008-nl03st57foo9su4qg5mddnadhl7ql5oe.apps.googleusercontent.com</code></td></tr><tr><td>Mago mobile app for Android</td><td><code>436832489008-5ie2c8hme7jucfh4vn4hul7sdkm8mhuk.apps.googleusercontent.com</code></td></tr><tr><td>Mago mobile app for iOS</td><td><code>436832489008-l3lejr6nqvgmevau7u999gm6c17jdci2.apps.googleusercontent.com</code></td></tr></tbody></table>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FDV0BTak78sohRm8CuHTU%2Fgoogle-admin-3.webp?alt=media&amp;token=640cf9e0-aa1c-4256-b7f2-38c523ae2e8f" alt=""><figcaption></figcaption></figure>

* Set your desired Scope and click **Continue**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FvACXSCMdnXaHQ3hwj7Mr%2Fgoogle-admin-4.webp?alt=media&amp;token=2a835ece-3797-4eb8-8e30-77feb62bba04" alt=""><figcaption></figcaption></figure>

* Set the app as **Trusted**, then click **Continue**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F5F0gatfqwQOSK73GFKlI%2Fgoogle-admin-5.webp?alt=media&amp;token=e7267572-68c7-476d-b975-5fee7fb8691e" alt=""><figcaption></figcaption></figure>

* Review and click **Finish**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FTuwZjSqWikY1JVFXHdpE%2Fgoogle-admin-6.webp?alt=media&amp;token=43656f5d-1749-4b55-b5db-dadeb013b3bb" alt=""><figcaption></figcaption></figure>

* Make sure to repeat the steps to configure all 3 Mago app client IDs.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FnXEy7r2WmJajKoenAsQk%2Fgoogle-admin-7.webp?alt=media&amp;token=db859a20-1821-444f-b82f-a28b6b06317b" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
This ensures that users and room resources are not blocked when Mago requests additional scopes (such as calendar access) during device activation or configuration.
{% endhint %}

{% hint style="info" %}
See [Google Workspace](/mago/requirements/third-party-providers/google-workspace) for the full list of **Required features and scopes**.
{% endhint %}
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Prepare the room resource and calendar

A room resource account is required for calendar integration and instant meeting hosting. Create and provision the account in your calendar provider before proceeding.

* **Microsoft 365** — create and provision a room resource account, grant the required OAuth scopes, and run the PowerShell command to correctly display meeting titles — see the full guide here: [Microsoft 365 calendar](/mago/requirements/calendar/microsoft-365-calendar)
* **Google Workspace** — create a service account for conference room calendars and configure resource delegation — see the full guide here: [Google Workspace calendar](/mago/requirements/calendar/google-workspace-calendar)
  {% endstep %}

{% step %}

### Prepare video conferencing

With Room System, the room has its own identity and can join meetings independently. The configuration depends on the video conferencing provider you plan to use. BYOM User Join is also available to users connected to the room. Complete the steps for each provider that applies to your deployment.

{% tabs %}
{% tab title="Microsoft Teams" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest and always goes to the lobby. No additional setup is required.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, you will configure the following:

* Install the **Azure Communication Services service principal** in the tenant
* Provision the room resource with a Microsoft Teams **license**

See [Authenticated Calls with Microsoft Teams](/mago/requirements/video-conferencing/authenticated-calls/authenticated-calls-with-microsoft-teams) for the full procedure.

**User Join (BYOM Authenticated Calls)**

Regardless of the room configuration, User Join (BYOM Authenticated Calls) is always available.

{% hint style="info" %}
When a user connects to the room with their personal device and starts a meeting, their user identity takes precedence over the room identity for the duration of the connection. Once the user disconnects, the room reverts to its own join mode.
{% endhint %}

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FTCtSK0GAuIvosfgjFF3h%2Frs-setup-auth.jpg?alt=media&amp;token=5dfa78cf-17c5-4822-bc44-32c7a5ff89e8" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Zoom" %}
**Guest Join (ID and Passcode)**

{% hint style="warning" %}
Since March 2026, Zoom no longer allows unauthenticated participants to join meetings from room systems.
{% endhint %}

* A Zoom account is required for all join modes, including Guest Join. Any Zoom account type is supported (Free, Pro, Business, Enterprise). Have the Zoom account credentials ready, as they will be entered during the activation wizard.
* The "Mago Room" app from the Zoom Marketplace must also be approved on the Zoom tenant or on the individual user account. See [Zoom](/mago/requirements/third-party-providers/zoom) for the approval procedure.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, you will assign the appropriate host license to the room resource Zoom account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}

{% tab title="Webex" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, a Webex account with host license is required (Free, Starter, Business, or Enterprise). Assign the appropriate license to the room resource account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}

{% tab title="Google Meet" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, a Google Workspace account is required (Free, Business Starter, Business Standard, Business Plus, or Enterprise). Assign the appropriate license to the room resource account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Enroll the device in Neat Pulse

Make sure the Neat device is already enrolled in your Neat Pulse account. If it is not, follow the Neat onboarding flow to add it before proceeding. See <https://neat.no/pulse/>
{% endstep %}

{% step %}

### Install Mago from Neat AppHub

On your Neat device, open the Neat Pulse management portal and navigate to the AppHub. Search for Mago and install it. Alternatively, you can push the app remotely to one or more devices directly from Neat Pulse.
{% endstep %}

{% step %}

### Grant required permissions

On first launch, Mago will request permissions for microphone, camera, networking, and local discovery. Grant all permissions when prompted. These are required for video conferencing, pairing, and screen sharing to function correctly.
{% endstep %}

{% step %}

### Sign in or Sign up to Mago Admin Center

If you do not already have an account, register at [admin.mago.io](https://admin.mago.io). You will also need a valid Mago license key. If you do not have one, you can select a free trial during device activation.
{% endstep %}

{% step %}

### Activate the device and complete the setup wizard

On first launch, Mago displays an activation screen with a QR code or a 6-digit code. Open [admin.mago.io](https://admin.mago.io) in a browser, go to Devices > Activate, and follow the on-screen steps to activate. Name the device when prompted. The device will appear under Devices in the Admin Center once activation is complete.

During the activation wizard, complete the following configuration steps.

* *Connect the calendar.* Select the calendar provider (Microsoft 365 or Google Workspace) and connect the room resource account you prepared. Complete the authentication flow and continue to the next step.
* *Configure video call providers.* For each video conferencing provider you plan to use (Microsoft Teams, Zoom, Cisco Webex, Google Meet, Mago Meet), enable the features that apply to your deployment: Guest Join with meeting ID and Passcode, Authenticated Calls, and Host Instant Meetings. The provider credentials and licenses you prepared are required to complete this configuration.
  {% endstep %}

{% step %}

### Pair the Touch Controller

*Neat Pad Controller.* Input the 6-digit code displayed on the Neat device to pair the Neat Pad.

*Wireless Touch Controller.* On the iPad or Android tablet, open the Mago Controller app and follow the pairing instructions. The app discovers the room device automatically when both are on the same network. After pairing, the tablet displays the room calendar and meeting controls.
{% endstep %}

{% step %}

### Configure policies

In Mago Admin Center, go to Policies and create or assign a policy for the device. Configure appearance, device settings, and any restrictions as needed. The device will update over the air.
{% endstep %}

{% step %}

### Verify

* Confirm date and time are correct
* Verify network connectivity
* Test wireless screen sharing
* Test video calls

{% hint style="success" %}
The room is now ready for Room System use!
{% endhint %}
{% endstep %}
{% endstepper %}


# Install on Android (All-in-One Interactive Flat Panel)

With Room System, Mago turns an Android interactive all-in-one device into a fully independent meeting room. The display, camera, microphone, and speaker are integrated in the unit. The room calendar is displayed on screen, meetings can be joined or started with a single tap, and a wireless Touch Controller lets anyone in the room manage the session.

### Installation steps

{% stepper %}
{% step %}

### Check hardware and peripherals

Verify that your device is on the [Android All-in-One Interactive Flat Panels](/mago/certified-devices/android-all-in-one-interactive-flat-panels) devices list.
{% endstep %}

{% step %}

### Prepare the Touch Controller (optional)

**Wireless Touch Controller**

You will use an iPad (iPadOS 13+) or Android tablet (Android 10.0+, minimum resolution 1024x600) as a wireless touch controller by installing the Mago Controller app from the App Store or Google Play. See [Wireless touch controllers](/mago/requirements/wireless-touch-controllers) for instructions. The wireless touch controller tablet requires an active Wi-Fi internet connection.
{% endstep %}

{% step %}

### Prepare the network

Connect the device to wired Gigabit Ethernet. Verify that the connection provides at least 2 Mbps of internet bandwidth. Configure firewall rules and FQDN allowlisting according to the [Network](/mago/requirements/network) requirements. Proxy connections are not supported.
{% endstep %}

{% step %}

### Prepare wireless screen sharing

Mago on Android supports two wireless screen sharing methods:

**Mago Link** allows any user to share their screen by visiting [magolink.com](https://magolink.com) from a browser on their laptop or mobile. No app install is required. Verify that the network meets the requirements described in [Mago Link](/mago/requirements/presentation/wireless-screen-sharing/mago-link).
{% endstep %}

{% step %}

### Authorize the Mago app in your organization

Before Mago can access **room calendars** and **video conferencing services** on behalf of your organization, a tenant administrator must grant consent to the Mago application in your identity or services provider, such as Microsoft 365 or Google Workspace.

This is a one-time operation that authorizes Mago to request the permissions it requires, such as reading calendar events and authenticating meeting participants.

{% hint style="warning" %}
Without this consent, devices will not be able to display room calendars or join meetings as authenticated participants.
{% endhint %}

Select your provider below and follow the setup steps.

{% tabs %}
{% tab title="Microsoft 365" %}
When using Mago with Microsoft 365 room resources and users, the Mago app for display and Mago mobile app access Microsoft 365 services through the Microsoft Graph and Azure Communication Services APIs. To enable these features, a tenant administrator must grant consent to the Mago enterprise application.

{% hint style="success" %}
Mago is a verified enterprise application in the **Microsoft Entra app gallery** (application ID `17781659-6867-4c77-9ba3-40670305181c)` and it is listed under the official **Azure Marketplace**.
{% endhint %}

#### Add the Mago application to your tenant

Open [admin.mago.io](https://admin.mago.io/) and sign in with a Microsoft 365 account that has **Global Administrator**, **Application Administrator**, or **Cloud Application Administrator privileges**. When prompted, review the requested permissions and select "Accept" on behalf of your organization. The Mago application is now registered in your tenant.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FSBktWH6jXKKddXFxxkng%2Fmago-admin-center-signin.jpg?alt=media&amp;token=c43b0523-dd1e-41c8-ad4f-3128de74f9f6" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FN9mgBPd1TFeHfU552urg%2Fmago-admin-consent.webp?alt=media&amp;token=e5c8903b-50cf-4b05-a05d-8cfe473e7949" alt="" width="375"><figcaption></figcaption></figure>

#### Grant admin consent to the required scopes

To review and grant admin consent to the required scopes in the Mago application permissions:

* Open the [**Azure portal**](https://portal.azure.com/) and sign in with a Microsoft 365 Administrator account.
* Go to Microsoft Entra ID > Enterprise Applications (or search directly for "**Enterprise Applications**").

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FiBdqVUpQpQSLQNL4Bkj2%2Fenterprise-apps.webp?alt=media&amp;token=bb4655ed-312c-4e3f-b80f-c39eb9fc2b96" alt=""><figcaption></figcaption></figure>

* Under the Application list, search for "**Mago**" (Application ID `17781659-6867-4c77-9ba3-40670305181c`).

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FWFi1wmwO2BlhLbgwTSM2%2Fenterprise-apps-mago.webp?alt=media&amp;token=d07d68d8-774a-43d5-af96-76624b67bc67" alt=""><figcaption></figcaption></figure>

* Enter the Mago application, go to **Security** > **Permissions** and verify that admin consent has been granted to the required scopes. To grant admin consent to all the required scopes, click the "Grant admin consent for *YourCompanyName*" button.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F5Hql2RRyQEziNdUZfP4Z%2Fenterprise-apps-mago-grant.webp?alt=media&amp;token=d6b8ad4b-6d29-468c-b84f-0830557e8703" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
See [Microsoft 365](/mago/requirements/third-party-providers/microsoft-365) for **Advanced consent options** and the full list of **Required features and scopes**.
{% endhint %}
{% endtab %}

{% tab title="Google Workspace" %}
When using Mago with Google Workspace room resources and users, the Mago app for display and Mago mobile app access Google services through Google APIs. To enable these features, a Google Workspace administrator must authorize the Mago application in the domain.

{% hint style="success" %}
Mago is a Google OAuth verified application.
{% endhint %}

#### Authorize the Mago application

Open [admin.mago.io](https://admin.mago.io/) and sign in with a Google Workspace account that has Super Admin privileges. When prompted, review the requested permissions and approve. The Mago application is now authorized in your domain.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FptqZeG1KKA7Q7fEhjAQB%2Fmago-admin-login.webp?alt=media&amp;token=1fc130ad-9776-40dc-a31a-fc435119cf84" alt="" width="351"><figcaption></figcaption></figure>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FInoQcmkioq9RJMDOtDjL%2Fmago-admin-center-google-signin.webp?alt=media&amp;token=ec711228-8371-4e61-b9a4-381cb93b3ea4" alt="" width="375"><figcaption></figcaption></figure>

#### Verify third-party app access and allow the Mago application if restricted

When room resources or users sign in later during device activation, Google will prompt them to approve additional scopes (such as calendar and meeting access).

{% hint style="warning" %}
If your domain restricts third-party application access, these prompts will be blocked with a **`400 admin_policy_enforced`** error.
{% endhint %}

#### Check third-party app access policy

To check if your domain restricts third-party application access:

* Open the [Google Admin console](https://admin.google.com/)
* Go to Security > Access and data control > **API controls**
* Click on **Settings**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FVI5V0TmYfaAJIY45So49%2Fgoogle-admin-8.webp?alt=media&amp;token=749f1b43-8521-432a-9807-d8fbd724d0a1" alt=""><figcaption></figcaption></figure>

* Under "Unconfigured third-party apps", verify which access level is selected. If it is set to "Allow users to access any third-party apps", no further action is required. If access is restricted, proceed with the next step to pre-authorize the Mago application at domain level.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FfFTtp3smBt53QIl3T0mn%2Fgoogle-admin-9.webp?alt=media&amp;token=bd3a67f7-3abe-4333-b1db-a8ce670196c0" alt=""><figcaption></figcaption></figure>

#### Pre-authorize the Mago application

If your domain restricts third-party application access:

* Open the [Google Admin console](https://admin.google.com/)
* Go to Security > Access and data control > API controls > **Manage App Access**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FLBO8JjSrXhwrYDA1ehyy%2Fgoogle-admin-1.webp?alt=media&amp;token=009551d7-3cf1-49fe-a4b0-a3017bd82321" alt=""><figcaption></figcaption></figure>

* Click on "Configure new app"

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2Fn9wVzHleirZv1yNKXlUO%2Fgoogle-admin-2.webp?alt=media&amp;token=bace8861-3ebd-4fb6-90d3-9c4d173d2dcd" alt=""><figcaption></figcaption></figure>

* Search for the following Mago app client IDs and add them as trusted app (one by one).

<table><thead><tr><th width="148.30078125">Application</th><th>Client ID</th></tr></thead><tbody><tr><td>Mago app for display / web</td><td><code>436832489008-nl03st57foo9su4qg5mddnadhl7ql5oe.apps.googleusercontent.com</code></td></tr><tr><td>Mago mobile app for Android</td><td><code>436832489008-5ie2c8hme7jucfh4vn4hul7sdkm8mhuk.apps.googleusercontent.com</code></td></tr><tr><td>Mago mobile app for iOS</td><td><code>436832489008-l3lejr6nqvgmevau7u999gm6c17jdci2.apps.googleusercontent.com</code></td></tr></tbody></table>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FDV0BTak78sohRm8CuHTU%2Fgoogle-admin-3.webp?alt=media&amp;token=640cf9e0-aa1c-4256-b7f2-38c523ae2e8f" alt=""><figcaption></figcaption></figure>

* Set your desired Scope and click **Continue**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FvACXSCMdnXaHQ3hwj7Mr%2Fgoogle-admin-4.webp?alt=media&amp;token=2a835ece-3797-4eb8-8e30-77feb62bba04" alt=""><figcaption></figcaption></figure>

* Set the app as **Trusted**, then click **Continue**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F5F0gatfqwQOSK73GFKlI%2Fgoogle-admin-5.webp?alt=media&amp;token=e7267572-68c7-476d-b975-5fee7fb8691e" alt=""><figcaption></figcaption></figure>

* Review and click **Finish**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FTuwZjSqWikY1JVFXHdpE%2Fgoogle-admin-6.webp?alt=media&amp;token=43656f5d-1749-4b55-b5db-dadeb013b3bb" alt=""><figcaption></figcaption></figure>

* Make sure to repeat the steps to configure all 3 Mago app client IDs.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FnXEy7r2WmJajKoenAsQk%2Fgoogle-admin-7.webp?alt=media&amp;token=db859a20-1821-444f-b82f-a28b6b06317b" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
This ensures that users and room resources are not blocked when Mago requests additional scopes (such as calendar access) during device activation or configuration.
{% endhint %}

{% hint style="info" %}
See [Google Workspace](/mago/requirements/third-party-providers/google-workspace) for the full list of **Required features and scopes**.
{% endhint %}
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Prepare the room resource and calendar

A room resource account is required for calendar integration and instant meeting hosting. Create and provision the account in your calendar provider before proceeding.

* **Microsoft 365** — create and provision a room resource account, grant the required OAuth scopes, and run the PowerShell command to correctly display meeting titles — see the full guide here: [Microsoft 365 calendar](/mago/requirements/calendar/microsoft-365-calendar)
* **Google Workspace** — create a service account for conference room calendars and configure resource delegation — see the full guide here: [Google Workspace calendar](/mago/requirements/calendar/google-workspace-calendar)
  {% endstep %}

{% step %}

### Prepare video conferencing

With Room System, the room has its own identity and can join meetings independently. The configuration depends on the video conferencing provider you plan to use. BYOM User Join is also available to users connected to the room. Complete the steps for each provider that applies to your deployment.

{% tabs %}
{% tab title="Microsoft Teams" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest and always goes to the lobby. No additional setup is required.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, you will configure the following:

* Install the **Azure Communication Services service principal** in the tenant
* Provision the room resource with a Microsoft Teams **license**

See [Authenticated Calls with Microsoft Teams](/mago/requirements/video-conferencing/authenticated-calls/authenticated-calls-with-microsoft-teams) for the full procedure.

**User Join (BYOM Authenticated Calls)**

Regardless of the room configuration, User Join (BYOM Authenticated Calls) is always available.

{% hint style="info" %}
When a user connects to the room with their personal device and starts a meeting, their user identity takes precedence over the room identity for the duration of the connection. Once the user disconnects, the room reverts to its own join mode.
{% endhint %}

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FTCtSK0GAuIvosfgjFF3h%2Frs-setup-auth.jpg?alt=media&amp;token=5dfa78cf-17c5-4822-bc44-32c7a5ff89e8" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Zoom" %}
**Guest Join (ID and Passcode)**

{% hint style="warning" %}
Since March 2026, Zoom no longer allows unauthenticated participants to join meetings from room systems.
{% endhint %}

* A Zoom account is required for all join modes, including Guest Join. Any Zoom account type is supported (Free, Pro, Business, Enterprise). Have the Zoom account credentials ready, as they will be entered during the activation wizard.
* The "Mago Room" app from the Zoom Marketplace must also be approved on the Zoom tenant or on the individual user account. See [Zoom](/mago/requirements/third-party-providers/zoom) for the approval procedure.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, you will assign the appropriate host license to the room resource Zoom account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}

{% tab title="Webex" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, a Webex account with host license is required (Free, Starter, Business, or Enterprise). Assign the appropriate license to the room resource account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}

{% tab title="Google Meet" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, a Google Workspace account is required (Free, Business Starter, Business Standard, Business Plus, or Enterprise). Assign the appropriate license to the room resource account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Install Mago

{% hint style="info" %}
Some All-in-One Interactive Flat Panels come with Mago pre-installed by the manufacturer. Check with your device vendor before proceeding. If Mago is already present, skip the installation and launch the app directly.
{% endhint %}

If Mago is not pre-installed, install it using one of the following methods depending on what is available on your device:

* **Google Play Store** — available on GoogleTV and AndroidTV devices, search for "Mago for Display" and install (Google Play store link [here](https://play.google.com/store/apps/details?id=com.remago.receiver))
* **Amazon Appstore** — available on FireTV devices, search for "Mago for Display" and install (Amazon Appstore link [here](https://www.amazon.com/gp/product/B0F19DGJB2))
* **Direct APK** — download the APK from [admin.mago.io/download-software](https://admin.mago.io/download-software) and sideload it on the device

After installation, launch the Mago app.
{% endstep %}

{% step %}

### Grant required permissions

On first launch, Mago will request permissions for microphone, camera, networking, local discovery, and display over other apps. Grant all permissions when prompted. You can review permissions later via Settings → Apps → Mago → Permissions.
{% endstep %}

{% step %}

### Disable "Pause app activity if unused"

Android may automatically restrict apps that have not been used recently, revoking permissions or suspending background services. To prevent this from interrupting screen sharing, pairing, or meeting startup, disable this option on the device via Settings → Apps → Mago.
{% endstep %}

{% step %}

### Sign in or Sign up to Mago Admin Center

If you do not already have an account, register at [admin.mago.io](https://admin.mago.io). You will also need a valid Mago license key. If you do not have one, you can select a free trial during device activation.
{% endstep %}

{% step %}

### Activate the device and complete the setup wizard

On first launch, Mago displays an activation screen with a QR code or a 6-digit code. Open [admin.mago.io](https://admin.mago.io) in a browser, go to Devices > Activate, and follow the on-screen steps to activate. Name the device when prompted. The device will appear under Devices in the Admin Center once activation is complete.

During the activation wizard, complete the following configuration steps.

* *Connect the calendar.* Select the calendar provider (Microsoft 365 or Google Workspace) and connect the room resource account you prepared. Complete the authentication flow and continue to the next step.
* *Configure video call providers.* For each video conferencing provider you plan to use (Microsoft Teams, Zoom, Cisco Webex, Google Meet, Mago Meet), enable the features that apply to your deployment: Guest Join with meeting ID and Passcode, Authenticated Calls, and Host Instant Meetings. The provider credentials and licenses you prepared are required to complete this configuration.
  {% endstep %}

{% step %}

### Pair the Touch Controller (optional)

On the iPad or Android tablet, open the Mago Controller app and follow the pairing instructions. The app discovers the room device automatically when both are on the same network. After pairing, the tablet displays the room calendar and meeting controls.
{% endstep %}

{% step %}

### Configure policies

In Mago Admin Center, go to Policies and create or assign a policy for the device. Configure appearance, device settings, and any restrictions as needed. The device will update over the air.
{% endstep %}

{% step %}

### Verify

* Confirm date and time are correct
* Verify network connectivity
* Test wireless screen sharing
* Test USB peripherals

{% hint style="success" %}
The room is now ready for Room System use!
{% endhint %}
{% endstep %}
{% endstepper %}


# Install on Android (Display / Smart TV)

With Room System, Mago turns an Android display or Smart TV into a fully independent meeting room. USB audio and video peripherals provide the conferencing hardware. The room calendar is displayed on screen, meetings can be joined or started with a single tap, and a wireless Touch Controller lets anyone in the room manage the session.

### Installation steps

{% stepper %}
{% step %}

### Check hardware and peripherals

Verify that your device (Android display, Smart TV, GoogleTV, AndroidTV, or FireTV) is on the [Android Displays / Smart TVs](/mago/certified-devices/android-displays-smart-tvs) devices list. Connect a USB videobar or separate USB camera, microphone, and speaker before launching Mago so they are detected correctly on first startup.
{% endstep %}

{% step %}

### Prepare the Touch Controller

**Wireless Touch Controller**

You will use an iPad (iPadOS 13+) or Android tablet (Android 10.0+, minimum resolution 1024x600) as a wireless touch controller by installing the Mago Controller app from the App Store or Google Play. See [Wireless touch controllers](/mago/requirements/wireless-touch-controllers) for instructions. The wireless touch controller tablet requires an active Wi-Fi internet connection.
{% endstep %}

{% step %}

### Prepare the network

Connect the device to wired Gigabit Ethernet. Verify that the connection provides at least 2 Mbps of internet bandwidth. Configure firewall rules and FQDN allowlisting according to the [Network](/mago/requirements/network) requirements. Proxy connections are not supported.
{% endstep %}

{% step %}

### Prepare wireless screen sharing

**Mago Link** allows any user to share their screen by visiting [magolink.com](https://magolink.com) from a browser on their laptop or mobile. No app install is required. Verify that the network meets the requirements described in [Mago Link](/mago/requirements/presentation/wireless-screen-sharing/mago-link).
{% endstep %}

{% step %}

### Authorize the Mago app in your organization

Before Mago can access **room calendars** and **video conferencing services** on behalf of your organization, a tenant administrator must grant consent to the Mago application in your identity or services provider, such as Microsoft 365 or Google Workspace.

This is a one-time operation that authorizes Mago to request the permissions it requires, such as reading calendar events and authenticating meeting participants.

{% hint style="warning" %}
Without this consent, devices will not be able to display room calendars or join meetings as authenticated participants.
{% endhint %}

Select your provider below and follow the setup steps.

{% tabs %}
{% tab title="Microsoft 365" %}
When using Mago with Microsoft 365 room resources and users, the Mago app for display and Mago mobile app access Microsoft 365 services through the Microsoft Graph and Azure Communication Services APIs. To enable these features, a tenant administrator must grant consent to the Mago enterprise application.

{% hint style="success" %}
Mago is a verified enterprise application in the **Microsoft Entra app gallery** (application ID `17781659-6867-4c77-9ba3-40670305181c)` and it is listed under the official **Azure Marketplace**.
{% endhint %}

#### Add the Mago application to your tenant

Open [admin.mago.io](https://admin.mago.io/) and sign in with a Microsoft 365 account that has **Global Administrator**, **Application Administrator**, or **Cloud Application Administrator privileges**. When prompted, review the requested permissions and select "Accept" on behalf of your organization. The Mago application is now registered in your tenant.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FSBktWH6jXKKddXFxxkng%2Fmago-admin-center-signin.jpg?alt=media&amp;token=c43b0523-dd1e-41c8-ad4f-3128de74f9f6" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FN9mgBPd1TFeHfU552urg%2Fmago-admin-consent.webp?alt=media&amp;token=e5c8903b-50cf-4b05-a05d-8cfe473e7949" alt="" width="375"><figcaption></figcaption></figure>

#### Grant admin consent to the required scopes

To review and grant admin consent to the required scopes in the Mago application permissions:

* Open the [**Azure portal**](https://portal.azure.com/) and sign in with a Microsoft 365 Administrator account.
* Go to Microsoft Entra ID > Enterprise Applications (or search directly for "**Enterprise Applications**").

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FiBdqVUpQpQSLQNL4Bkj2%2Fenterprise-apps.webp?alt=media&amp;token=bb4655ed-312c-4e3f-b80f-c39eb9fc2b96" alt=""><figcaption></figcaption></figure>

* Under the Application list, search for "**Mago**" (Application ID `17781659-6867-4c77-9ba3-40670305181c`).

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FWFi1wmwO2BlhLbgwTSM2%2Fenterprise-apps-mago.webp?alt=media&amp;token=d07d68d8-774a-43d5-af96-76624b67bc67" alt=""><figcaption></figcaption></figure>

* Enter the Mago application, go to **Security** > **Permissions** and verify that admin consent has been granted to the required scopes. To grant admin consent to all the required scopes, click the "Grant admin consent for *YourCompanyName*" button.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F5Hql2RRyQEziNdUZfP4Z%2Fenterprise-apps-mago-grant.webp?alt=media&amp;token=d6b8ad4b-6d29-468c-b84f-0830557e8703" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
See [Microsoft 365](/mago/requirements/third-party-providers/microsoft-365) for **Advanced consent options** and the full list of **Required features and scopes**.
{% endhint %}
{% endtab %}

{% tab title="Google Workspace" %}
When using Mago with Google Workspace room resources and users, the Mago app for display and Mago mobile app access Google services through Google APIs. To enable these features, a Google Workspace administrator must authorize the Mago application in the domain.

{% hint style="success" %}
Mago is a Google OAuth verified application.
{% endhint %}

#### Authorize the Mago application

Open [admin.mago.io](https://admin.mago.io/) and sign in with a Google Workspace account that has Super Admin privileges. When prompted, review the requested permissions and approve. The Mago application is now authorized in your domain.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FptqZeG1KKA7Q7fEhjAQB%2Fmago-admin-login.webp?alt=media&amp;token=1fc130ad-9776-40dc-a31a-fc435119cf84" alt="" width="351"><figcaption></figcaption></figure>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FInoQcmkioq9RJMDOtDjL%2Fmago-admin-center-google-signin.webp?alt=media&amp;token=ec711228-8371-4e61-b9a4-381cb93b3ea4" alt="" width="375"><figcaption></figcaption></figure>

#### Verify third-party app access and allow the Mago application if restricted

When room resources or users sign in later during device activation, Google will prompt them to approve additional scopes (such as calendar and meeting access).

{% hint style="warning" %}
If your domain restricts third-party application access, these prompts will be blocked with a **`400 admin_policy_enforced`** error.
{% endhint %}

#### Check third-party app access policy

To check if your domain restricts third-party application access:

* Open the [Google Admin console](https://admin.google.com/)
* Go to Security > Access and data control > **API controls**
* Click on **Settings**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FVI5V0TmYfaAJIY45So49%2Fgoogle-admin-8.webp?alt=media&amp;token=749f1b43-8521-432a-9807-d8fbd724d0a1" alt=""><figcaption></figcaption></figure>

* Under "Unconfigured third-party apps", verify which access level is selected. If it is set to "Allow users to access any third-party apps", no further action is required. If access is restricted, proceed with the next step to pre-authorize the Mago application at domain level.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FfFTtp3smBt53QIl3T0mn%2Fgoogle-admin-9.webp?alt=media&amp;token=bd3a67f7-3abe-4333-b1db-a8ce670196c0" alt=""><figcaption></figcaption></figure>

#### Pre-authorize the Mago application

If your domain restricts third-party application access:

* Open the [Google Admin console](https://admin.google.com/)
* Go to Security > Access and data control > API controls > **Manage App Access**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FLBO8JjSrXhwrYDA1ehyy%2Fgoogle-admin-1.webp?alt=media&amp;token=009551d7-3cf1-49fe-a4b0-a3017bd82321" alt=""><figcaption></figcaption></figure>

* Click on "Configure new app"

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2Fn9wVzHleirZv1yNKXlUO%2Fgoogle-admin-2.webp?alt=media&amp;token=bace8861-3ebd-4fb6-90d3-9c4d173d2dcd" alt=""><figcaption></figcaption></figure>

* Search for the following Mago app client IDs and add them as trusted app (one by one).

<table><thead><tr><th width="148.30078125">Application</th><th>Client ID</th></tr></thead><tbody><tr><td>Mago app for display / web</td><td><code>436832489008-nl03st57foo9su4qg5mddnadhl7ql5oe.apps.googleusercontent.com</code></td></tr><tr><td>Mago mobile app for Android</td><td><code>436832489008-5ie2c8hme7jucfh4vn4hul7sdkm8mhuk.apps.googleusercontent.com</code></td></tr><tr><td>Mago mobile app for iOS</td><td><code>436832489008-l3lejr6nqvgmevau7u999gm6c17jdci2.apps.googleusercontent.com</code></td></tr></tbody></table>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FDV0BTak78sohRm8CuHTU%2Fgoogle-admin-3.webp?alt=media&amp;token=640cf9e0-aa1c-4256-b7f2-38c523ae2e8f" alt=""><figcaption></figcaption></figure>

* Set your desired Scope and click **Continue**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FvACXSCMdnXaHQ3hwj7Mr%2Fgoogle-admin-4.webp?alt=media&amp;token=2a835ece-3797-4eb8-8e30-77feb62bba04" alt=""><figcaption></figcaption></figure>

* Set the app as **Trusted**, then click **Continue**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F5F0gatfqwQOSK73GFKlI%2Fgoogle-admin-5.webp?alt=media&amp;token=e7267572-68c7-476d-b975-5fee7fb8691e" alt=""><figcaption></figcaption></figure>

* Review and click **Finish**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FTuwZjSqWikY1JVFXHdpE%2Fgoogle-admin-6.webp?alt=media&amp;token=43656f5d-1749-4b55-b5db-dadeb013b3bb" alt=""><figcaption></figcaption></figure>

* Make sure to repeat the steps to configure all 3 Mago app client IDs.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FnXEy7r2WmJajKoenAsQk%2Fgoogle-admin-7.webp?alt=media&amp;token=db859a20-1821-444f-b82f-a28b6b06317b" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
This ensures that users and room resources are not blocked when Mago requests additional scopes (such as calendar access) during device activation or configuration.
{% endhint %}

{% hint style="info" %}
See [Google Workspace](/mago/requirements/third-party-providers/google-workspace) for the full list of **Required features and scopes**.
{% endhint %}
{% endtab %}
{% endtabs %}

### Prepare the room resource and calendar

A room resource account is required for calendar integration and instant meeting hosting. Create and provision the account in your calendar provider before proceeding.

* **Microsoft 365** — create and provision a room resource account, grant the required OAuth scopes, and run the PowerShell command to correctly display meeting titles — see the full guide here: [Microsoft 365 calendar](/mago/requirements/calendar/microsoft-365-calendar)
* **Google Workspace** — create a service account for conference room calendars and configure resource delegation — see the full guide here: [Google Workspace calendar](/mago/requirements/calendar/google-workspace-calendar)

### Prepare video conferencing

With Room System, the room has its own identity and can join meetings independently. The configuration depends on the video conferencing provider you plan to use. BYOM User Join is also available to users connected to the room. Complete the steps for each provider that applies to your deployment.

{% tabs %}
{% tab title="Microsoft Teams" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest and always goes to the lobby. No additional setup is required.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, you will configure the following:

* Install the **Azure Communication Services service principal** in the tenant
* Provision the room resource with a Microsoft Teams **license**

See [Authenticated Calls with Microsoft Teams](/mago/requirements/video-conferencing/authenticated-calls/authenticated-calls-with-microsoft-teams) for the full procedure.

**User Join (BYOM Authenticated Calls)**

Regardless of the room configuration, User Join (BYOM Authenticated Calls) is always available.

{% hint style="info" %}
When a user connects to the room with their personal device and starts a meeting, their user identity takes precedence over the room identity for the duration of the connection. Once the user disconnects, the room reverts to its own join mode.
{% endhint %}

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FTCtSK0GAuIvosfgjFF3h%2Frs-setup-auth.jpg?alt=media&amp;token=5dfa78cf-17c5-4822-bc44-32c7a5ff89e8" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Zoom" %}
**Guest Join (ID and Passcode)**

{% hint style="warning" %}
Since March 2026, Zoom no longer allows unauthenticated participants to join meetings from room systems.
{% endhint %}

* A Zoom account is required for all join modes, including Guest Join. Any Zoom account type is supported (Free, Pro, Business, Enterprise). Have the Zoom account credentials ready, as they will be entered during the activation wizard.
* The "Mago Room" app from the Zoom Marketplace must also be approved on the Zoom tenant or on the individual user account. See [Zoom](/mago/requirements/third-party-providers/zoom) for the approval procedure.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, you will assign the appropriate host license to the room resource Zoom account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}

{% tab title="Webex" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, a Webex account with host license is required (Free, Starter, Business, or Enterprise). Assign the appropriate license to the room resource account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}

{% tab title="Google Meet" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, a Google Workspace account is required (Free, Business Starter, Business Standard, Business Plus, or Enterprise). Assign the appropriate license to the room resource account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Prepare video conferencing

With Room System, the room has its own identity and can join meetings independently. The configuration depends on the video conferencing provider you plan to use. BYOM User Join is also available to users connected to the room. Complete the steps for each provider that applies to your deployment.

{% tabs %}
{% tab title="Microsoft Teams" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest and always goes to the lobby. No additional setup is required.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, you will configure the following:

* Install the **Azure Communication Services service principal** in the tenant
* Provision the room resource with a Microsoft Teams **license**

See [Authenticated Calls with Microsoft Teams](/mago/requirements/video-conferencing/authenticated-calls/authenticated-calls-with-microsoft-teams) for the full procedure.

**User Join (BYOM Authenticated Calls)**

Regardless of the room configuration, User Join (BYOM Authenticated Calls) is always available.

{% hint style="info" %}
When a user connects to the room with their personal device and starts a meeting, their user identity takes precedence over the room identity for the duration of the connection. Once the user disconnects, the room reverts to its own join mode.
{% endhint %}

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FTCtSK0GAuIvosfgjFF3h%2Frs-setup-auth.jpg?alt=media&amp;token=5dfa78cf-17c5-4822-bc44-32c7a5ff89e8" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Zoom" %}
**Guest Join (ID and Passcode)**

{% hint style="warning" %}
Since March 2026, Zoom no longer allows unauthenticated participants to join meetings from room systems.
{% endhint %}

* A Zoom account is required for all join modes, including Guest Join. Any Zoom account type is supported (Free, Pro, Business, Enterprise). Have the Zoom account credentials ready, as they will be entered during the activation wizard.
* The "Mago Room" app from the Zoom Marketplace must also be approved on the Zoom tenant or on the individual user account. See [Zoom](/mago/requirements/third-party-providers/zoom) for the approval procedure.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, you will assign the appropriate host license to the room resource Zoom account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}

{% tab title="Webex" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, a Webex account with host license is required (Free, Starter, Business, or Enterprise). Assign the appropriate license to the room resource account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}

{% tab title="Google Meet" %}
**Guest Join (ID and Passcode)**

Guest Join is available out of the box. The room joins as a guest with no additional setup.

**Room Join (Authenticated Calls) and Host Instant Meetings**

To enable Room Join and Host Instant Meetings, which allow the room to bypass the lobby, appear with its own identity, and start new meetings as a host, a Google Workspace account is required (Free, Business Starter, Business Standard, Business Plus, or Enterprise). Assign the appropriate license to the room resource account according to the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) table.
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Sign in or Sign up to Mago Admin Center

If you do not already have an account, register at [admin.mago.io](https://admin.mago.io). You will also need a valid Mago license key. If you do not have one, you can select a free trial during device activation.
{% endstep %}

{% step %}

### Install Mago

Install Mago on the device using one of the following methods depending on your device type:

* **Google Play Store** — available on GoogleTV and AndroidTV devices, search for "Mago for Display" and install (Google Play store link [here](https://play.google.com/store/apps/details?id=com.remago.receiver))
* **Amazon Appstore** — available on FireTV devices, search for "Mago for Display" and install (Amazon Appstore link [here](https://www.amazon.com/gp/product/B0F19DGJB2))
* **Direct APK** — download the APK from [admin.mago.io/download-software](https://admin.mago.io/download-software) and sideload it on the device

After installation, launch the Mago app.
{% endstep %}

{% step %}

### Grant required permissions

On first launch, Mago will request permissions for microphone, camera, networking, local discovery, and display over other apps. Grant all permissions when prompted. You can review permissions later via Settings → Apps → Mago → Permissions.
{% endstep %}

{% step %}

### Disable "Pause app activity if unused"

Android may automatically restrict apps that have not been used recently, revoking permissions or suspending background services. To prevent this from interrupting screen sharing, pairing, or meeting startup, disable this option on the device via Settings → Apps → Mago.
{% endstep %}

{% step %}

### Activate the device and complete the setup wizard

On first launch, Mago displays an activation screen with a QR code or a 6-digit code. Open [admin.mago.io](https://admin.mago.io) in a browser, go to Devices > Activate, and follow the on-screen steps to activate. Name the device when prompted. The device will appear under Devices in the Admin Center once activation is complete.

During the activation wizard, complete the following configuration steps.

* *Connect the calendar.* Select the calendar provider (Microsoft 365 or Google Workspace) and connect the room resource account you prepared. Complete the authentication flow and continue to the next step.
* *Configure video call providers.* For each video conferencing provider you plan to use (Microsoft Teams, Zoom, Cisco Webex, Google Meet, Mago Meet), enable the features that apply to your deployment: Guest Join with meeting ID and Passcode, Authenticated Calls, and Host Instant Meetings. The provider credentials and licenses you prepared are required to complete this configuration.
  {% endstep %}

{% step %}

### Configure policies

In Mago Admin Center, go to Policies and create or assign a policy for the device. Configure appearance, device settings, and any restrictions as needed. The device will update over the air.
{% endstep %}

{% step %}

### Verify

* Confirm date and time are correct
* Verify network connectivity
* Test wireless screen sharing
* Test AV peripherals

{% hint style="success" %}
The room is now ready for Room System use!
{% endhint %}
{% endstep %}
{% endstepper %}


# Certified Devices

Mago is available on Windows and Android hardware. Select your platform below to see the full list of certified devices and minimum specifications. Devices not listed may still work if they meet the minimum specifications, but support for non-certified installations is limited.

<table><thead><tr><th width="200.80859375">Platform</th><th width="199.5">→ Go to</th><th>OS</th><th>Display</th><th>AV peripherals</th></tr></thead><tbody><tr><td><strong>Windows (PC / OPS)</strong></td><td><a data-mention href="/mago/certified-devices/windows-devices">Windows Devices</a></td><td>Windows 11</td><td>External, passive or interactive</td><td>USB (camera, mic, speaker)</td></tr><tr><td><strong>Neat</strong></td><td><a data-mention href="/mago/certified-devices/neat-devices">Neat Devices</a></td><td>Neat OS (Neat Pulse)</td><td>External passive (Bar) or integrated interactive (Board)</td><td>Integrated</td></tr><tr><td><strong>All-in-One Interactive Flat Panel</strong></td><td><a data-mention href="/mago/certified-devices/android-all-in-one-interactive-flat-panels">Android All-in-One Interactive Flat Panels</a></td><td>Android 10+</td><td>Integrated, interactive</td><td>Integrated in the unit</td></tr><tr><td><strong>Display / Smart TV</strong></td><td><a data-mention href="/mago/certified-devices/android-displays-smart-tvs">Android Displays / Smart TVs</a></td><td>Android, GoogleTV, FireTV</td><td>Integrated, passive</td><td>USB (camera, mic, speaker)</td></tr><tr><td><strong>Video Bar (MDM)</strong></td><td><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Coming soon</p></div></td><td>Android</td><td>External, passive</td><td>Integrated in the bar</td></tr></tbody></table>


# Windows Devices

### Certified PC / Mini PC / NUC / Room Kits

| Brand      | Model                                     |
| ---------- | ----------------------------------------- |
| Mago       | Core Pro S104C OPS/NUC (MH-CORE-PRO)      |
| HP         | ProDesk 4 Mini G1i Desktop AI PC          |
| HP         | Elite Mini 400 G9                         |
| HP         | Elite Mini 600 G9                         |
| HP         | Elite Mini 800 G9                         |
| ASUS       | NUC 14 PRO (NUC14RVH, Ultra Core 5)       |
| Yealink    | MCore PC (MVC400, MVC840, MVC860)         |
| Lenovo     | ThinkSmart One                            |
| Lenovo     | ThinkSmart Core Kit                       |
| Lenovo     | ThinkSmart HUB 500                        |
| Lenovo     | ThinkSmart HUB Gen2                       |
| TERRA      | PC-Micro 6000 (i1135G7)                   |
| SiComputer | Embedded OPS for Ricoh IFP                |
| XATROM     | System OPS Intel 12 Core (Alder Lake-U/P) |
| Cubi NUC   | 1MX (1MG / 1M)                            |

Any OPS module included in a certified interactive display also qualifies as a certified Windows device.

***

### Certified Interactive Displays with Integrated OPS

| Brand               | Model                        |
| ------------------- | ---------------------------- |
| Mago                | One 55"                      |
| Huawei              | IdeaHub B2                   |
| Huawei              | IdeaHub B3                   |
| Huawei              | IdeaHub S                    |
| Huawei              | IdeaHub S2                   |
| Huawei              | IdeaHub Pro                  |
| Huawei              | IdeaHub G2                   |
| Huawei              | IdeaHub ES2                  |
| Huawei              | IdeaHub ES2 Plus             |
| Yealink             | MeetingBoard 65"             |
| Yealink             | MeetingBoard 86"             |
| LG                  | ONE:QUICK WORKS 55"          |
| LG                  | ONE:QUICK FLEX 43"           |
| LG                  | CreateBoard                  |
| Jupiter             | Pana 34"                     |
| Jupiter             | Pana 81"                     |
| Jupiter             | Pana 105"                    |
| Ricoh               | IWB A6500                    |
| Ricoh               | IWB A6510                    |
| Ricoh               | IWB A7500                    |
| Ricoh               | IWB A7510                    |
| Ricoh               | IWB A8600                    |
| Ricoh               | IWB A8610                    |
| Newline Interactive | SDM-L Module (Gen11 i5 / i7) |

***

### Minimum specifications for non-certified Windows hardware

{% hint style="warning" %}
Installing Mago on a non-certified Windows device does not guarantee correct functionality and performance. Support for non-certified installations is limited.
{% endhint %}

| Specification  | Requirement                                                        |
| -------------- | ------------------------------------------------------------------ |
| OS             | Windows 11 version 24H2 or later (Pro, Enterprise, IoT Enterprise) |
| CPU            | Intel Core i7, 11th generation or newer                            |
| RAM            | 8 GB (16 GB recommended)                                           |
| Storage        | 128 GB SSD                                                         |
| Network        | Ethernet and Wi-Fi, NDIS 6.3 or later                              |
| Display output | Miracast-compatible graphics card                                  |
| Peripherals    | USB camera and USB microphone                                      |
| GPU memory     | 1 GB dedicated DVMT (for shared GPU systems)                       |


# How to Prepare Your Own Windows Hardware

This page describes how to prepare a non-certified Windows device for Mago. If you are using a certified Mago Core device, it comes with Mago pre-installed and you can skip this page entirely.

{% hint style="danger" %}
**A fresh installation of Windows is mandatory**. Installing Mago on modified OEM images, collaboration appliance images (such as Microsoft Teams Rooms or Zoom Rooms), or preconfigured firmware is **not supported**.
{% endhint %}

{% stepper %}
{% step %}

### Install Windows 11

1. Create a Windows 11 installation USB using the Microsoft Media Creation Tool. Refer to this guide: <https://support.microsoft.com/en-us/windows/create-installation-media-for-windows-99a58364-8c02-206f-aa6f-40c3b507420d>
2. Boot from the USB key using BIOS or Advanced Recovery options.
3. When prompted, delete **all partitions** until only “Unallocated space” remains, then install Windows.
4. Complete OOBE:
   * Select region and keyboard
   * At the account step, **create a local Administrator user**
   * If Windows forces online login, disconnect all network connections (Ethernet and WiFi), reboot, press **SHIFT + F10** to open the Command Prompt and run "**OOBE\BYPASSNRO**" (without quotes)
5. Once on the desktop, connect to the internet.
6. Activate Windows with a valid Windows 11 Pro, IoT or Enterprise license.
7. Rename the PC (room name or device name) and restart.
   {% endstep %}

{% step %}

### Update the system

1. Install all Windows Updates.
2. Install **Optional Updates** (drivers, firmware, .NET components).
3. Open Device Manager and confirm that **no devices** are missing drivers.
4. Install any required vendor clients for peripherals (Jabra, Logitech, Poly).
   {% endstep %}

{% step %}

### Configure Windows 11

#### Power and performance

* Control Panel → Power Options → set to Ultimate Performance (preferred) or High Performance.
* Optional: Enable Fast Startup (if available on the hardware).

#### Security settings

* User Access Control (UAC): set to **Always notify** (highest level).
* Add Mago and all files inside *Program Files\Mago* to Antivirus and Firewall **exclusions**.
* Ensure the admin account is able to create a local unprivileged user (required during installation).

#### System and language

* Enable **Location Services** and allow apps to use location.
* Set Language, Region, and Time Zone correctly.
* Enable automatic Date & Time and NTP sync (time.windows.com).

#### Display configuration

* Windows Settings → System → Display:
  * Set the main display as **Primary**
  * Set additional displays (including wired tabletop touch controllers) as **Extended**
  * Refresh rate: **60 Hz or higher**, where possible
  * Recommended scale for main screen: **250 percent**
* For touch controllers:
  * Control Panel → Tablet PC Settings → **Calibrate touch** for each screen

Restart the PC.
{% endstep %}

{% step %}

### Enable Bluetooth for Proximity Join

* Enable Bluetooth on the device (BLE 4.0 or higher required).
* Bluetooth is used only for proximity detection using **ADV\_NONCONN\_INT** beacons.
* No pairing is required.
* All data transfer occurs through secure E2E encrypted HTTPS signaling.
  {% endstep %}

{% step %}

### Remove unnecessary components

* Uninstall Microsoft Teams (any preinstalled variant).
* Remove unwanted OEM apps or bloatware.
* Remove OneDrive (optional, improves boot speed).
  {% endstep %}

{% step %}

### Install and activate Mago

1. Log in as the Administrator.
2. Download the latest Mago release from: [**https://admin.mago.io**](https://admin.mago.io) **→ Downloads**.
3. Run the installer.
4. When prompted, launch the **Mago Configuration Wizard**.
5. Activate Mago (locally or online)

{% hint style="info" %}
At the Local User step, choose a username and optional password. Complete all remaining steps and restart.
{% endhint %}

{% hint style="success" %}
Windows will automatically log into the new **Mago** local user and launch Mago.
{% endhint %}
{% endstep %}

{% step %}

### Configure the Mago user

1. Close the Mago app:
   * If kiosk mode is enabled, disable it via “Mago Settings → Advanced” as Admin user (<kbd>CTRL+ALT+DEL</kbd> → Logout → Login as Admin → Open Mago Room Settings) or via Admin Center policy.
   * If kiosk mode is disabled: long-press the top Mago logo for 5 seconds and confirm exit.
2. Set audio input/output devices correctly under Windows Settings.
3. Confirm Google Chrome is the default browser. If not, set it manually.
4. Disable all Windows notifications.

Optional performance tuning

* Unpin all taskbar icons.
* Disable Search, Widgets and Task View.
* Set Dark mode theme.
  {% endstep %}

{% step %}

### Optional (up to Mago v7.0): Install and configure the Microsoft Teams desktop client

1. Login with the Mago local user.
2. Close the Mago app (disable kiosk mode, if enabled, and long-press the Mago logo for 5 seconds).&#x20;
3. Uninstall any preinstalled Teams or Teams Personal.
4. Download the latest Teams desktop client using Chrome.
5. Sign in with the **same room resource account** used in Mago settings (Calendar and Instant Meetings).
6. Apply these Teams settings:
   * Disable Auto-start
   * Enable Open in background
   * Enable Keep running when closed
   * Enable Turn off animations
7. Start a Meet Now and check microphone, speaker and camera settings.
8. Close Teams.
9. Enable “Use Teams Desktop Client” in Mago Settings → Advanced, and save.
10. Restart the PC.
    {% endstep %}

{% step %}

### First-use validation

Verify that the room behaves correctly.

1. Automatic login to the Mago user.
2. Launch a Teams meeting from Mago and verify:
   * Auto-join
   * Camera works
   * Microphone works
   * Speaker output is correct
3. Repeat with Zoom, Google Meet and Webex, or any preferred provider.
4. Test all configured screen sharing methods:
   * HDMI ingest
   * Miracast
   * AirPlay
   * Google Cast
   * Mago Link (magolink.com)
5. Test Mago whiteboard (offline and online).
6. Test installed apps (e.g. Chrome).
7. End the meeting and confirm full session cleanup.
   {% endstep %}
   {% endstepper %}


# How to Install Using Software Distribution (Silent Install)

{% hint style="warning" %}
**IMPORTANT**\
Before performing silent installations, it is recommended to:

* Sign in to the Admin Portal at [**https://admin.mago.io**](https://admin.mago.io/)
* Pre-configure the global and room-specific Mago policies
* Add all license keys to your tenant in advance

This ensures that newly installed Mago instances will apply the correct configuration immediately after activation.
{% endhint %}

{% stepper %}
{% step %}

### Prepare for software distribution

1. Download the latest **Mago installer** (.exe) from the Admin Portal.
2. Copy the installer to your deployment system or file repository.
3. Ensure the deployment is executed with **administrator privileges** on the target machine.
4. Confirm that the device meets the required Windows 11, hardware and driver requirements.
   {% endstep %}

{% step %}

### Silent installation commands

The following commands perform a fully silent installation with no visible UI or prompts.

All commands must be executed in an elevated **cmd.exe** or by a software distribution tool running as Administrator.

**Option A) Install with default configuration (no local Mago user created)**

`Magoroom_installer.exe /KEY {Serial} /DEFAULT-CONFIG /S`&#x20;

Use this when your environment manages user accounts separately or when using Azure AD/Intune-based device provisioning.

**Option B) Install with default configuration and creation of local Mago user**

`Magoroom_installer.exe /KEY {Serial} /DEFAULT-CONFIG /LOCAL-USER /S`&#x20;

Creates a default **Mago** local user account automatically during installation.

**Option C) Install with default configuration and creation of custom local user with password**

`Magoroom_installer.exe /KEY {Serial} /DEFAULT-CONFIG /LOCAL-USER-USERNAME {username} /LOCAL-USER-PASSWORD {password} /S`&#x20;

Use this when your security policies require custom-defined local account names or passwords.
{% endstep %}

{% step %}

### Post-installation behavior

After a successful silent installation:

* The Mago application will be installed and registered as the primary shell for the Mago user
* The system will be ready to auto-login to the local Mago user (if created)
* Upon first launch, Mago will automatically activate using the provided license key
* The device will immediately apply all policies configured in the Admin Portal
  {% endstep %}

{% step %}

### Notes for mass deployments

* Ensure all required Windows 11 updates and hardware drivers are installed before pushing Mago.
* For environments with strict firewalls, validate that Mago required ports and URLs are whitelisted.
* Use the Admin Portal to centrally manage policies and room settings across all deployed devices.
* Reboots may be required depending on software distribution platform behavior.
  {% endstep %}
  {% endstepper %}


# Supported display types

## Supported display types

* Passive display (e.g. LCD/OLED screen)
* Interactive displays (e.g. multitouch whiteboards)
* Video wall (with multitouch frame)
* Passive projector
* Interactive projector (e.g. with touch pen)
* Dual projectors with edge blending

## Supported Resolutions

* Full HD, 16:9 aspect ratio (1920 x 1080 pixels)
* 4K, 16:9 aspect ratio (3840 x 2160 pixels)
* 5K, 21:9 aspect ratio (5120 x 2160 pixels)

## Recommended settings

* On interactive displays, for a smooth writing experience, set the refresh rate of your video card to 60 Hz or higher (please note that generally only one video input port can support this setting. If in doubt, check the hardware manual).
* Use HDMI 2.0+ cables

## Consumer Electronics Control (CEC)

Configure the settings of your Front of Room displays to support Consumer Electronics Control (CEC) or enable PC mode.\
If you want the room display to automatically switch to Mago when it wakes up from standby mode, certain conditions must be met. This feature is optional but supported by the Mago software, as long as the underlying hardware supports the feature. A consumer TV used as a display in the living room must support the Consumer Electronics Control (CEC) feature of HDMI. Depending on the dock or console selected (which may not support CEC, refer to the manufacturer's support documentation), a controller such as the Crestron HD-RX-4K-201-C-E, Liberty's DL-UHDILC, or the Extron HD CTL 100 may be required to enable the desired behavior.


# Wired touch controllers

### Certified devices

The following interactive, wired tabletop controllers are certified for Mago on Windows.

* Mimo Myst Capture USB My-1090CP (SKU MI-MY-1090CP-G)
* Mimo Myst Capture IP My-1090VP (SKU MI-MY-1090CV)
* Poly GC8 (SKU 2200-30780-001)
* Lenovo ThinkSmart Controller
* Yealink MTouch II Controller (MVC400, MVC840, MVC860)
* Logitech TAP USB (SKU 939-001796), firmware 1.1.15 or higher
* Logitech TAP with CAT5e kit (SKU 939-001950), firmware 1.1.15 or higher

### Configurations

Mago on Windows supports dual display configurations with both passive and interactive screens. In a dual display setup, the system automatically assigns the role of each screen to provide the best meeting and collaboration experience.

The main screen is used for all interactive and content based activities. This includes:

* Mago Launcher UI
* Mago Whiteboard
* UCC content gallery
* Wireless screen sharing
* HDMI ingest
* Applications

The extended screen is dedicated to the UCC video layout to keep remote participants visible at all times during collaboration, content viewing or whiteboarding.

An optional touch controller can be added to the room, available either as a wireless tablet or as a certified USB or USB-C hardware console. The touch controller allows users to operate the room system without touching the front displays.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FxI3CKQDdVeyabJ7Ur7SI%2Fdual-display.png?alt=media&amp;token=a92b83f9-1f65-42a2-a555-998628a51f1f" alt=""><figcaption></figcaption></figure>


# (Optional) HDMI capture cards and Third-party BYOD / BYOM systems

## HDMI Capture cards

The following HDMI capture cards are certified for use with Mago:

* INOGENI 4K2USB3 USB 3.0 Capture Card (<https://inogeni.com/product/4k2usb3/>)
* Capture cards integrated into wired tabletop controllers

## Third-party BYOD / BYOM systems

The following third-party systems for Bring Your Own Device (content presentation) and Bring Your Own Meeting (videoconferencing from your own device, with virtualization of room peripherals) are tested for Mago:

* Barco ClickShare Present
* Barco ClickShare Conference
* AirServer Connect
* Crestron AirMedia
* Evoko MPX200 (in MTR Mode)

{% hint style="info" %}
Any other third-party system with HDMI output can be used as a source for the ingest HDMI in Mago on Windows.
{% endhint %}


# Neat Devices

### Certified Neat devices

| Device         | Type            | Display                            |
| -------------- | --------------- | ---------------------------------- |
| Neat Bar Gen 2 | Video bar       | External passive display via HDMI  |
| Neat Bar Pro   | Video bar       | External passive display via HDMI  |
| Neat Board 50  | All-in-one      | Integrated 50" interactive display |
| Neat Board Pro | All-in-one      | Integrated interactive display     |
| Neat Frame     | Personal device | Integrated display                 |

Neat Bar Gen 2 and Neat Bar Pro can be paired with a Neat Pad as a Touch Controller. If no Neat Pad is available, an iPad or Android tablet with the Mago Controller app can be used as an alternative wireless Touch Controller.


# Android All-in-One Interactive Flat Panels

### Certified devices

| Brand              | Model                   | Size            |
| ------------------ | ----------------------- | --------------- |
| BenQ               | RE8604                  | 86"             |
| Clevertouch        | Edge                    | Various         |
| Clevertouch        | Impact Lux              | Various         |
| Clevertouch        | Impact Max 2Gen         | Various         |
| Huawei             | IdeaHub S2 65 / 75 / 86 | 65" / 75" / 86" |
| LG                 | CreateBoard             | Various         |
| Ricoh              | A6510 / A7510 / A8610   | 65" / 75" / 86" |
| SMART Technologies | MX QX V2, MX V4, MX V5  | Various         |
| ViewSonic          | IFP8652-1C              | 86"             |
| Yealink            | MeetingBoard 65         | 65"             |

***

### Minimum system requirements

| Specification | Requirement                                                                      |
| ------------- | -------------------------------------------------------------------------------- |
| OS            | Android 10 or newer, 64-bit only                                                 |
| Network       | Wired Ethernet (recommended) or Wi-Fi 802.11ac with signal stronger than -60 dBm |


# Android Displays / Smart TVs

### Certified devices

| Brand              | Model        | Type                    |
| ------------------ | ------------ | ----------------------- |
| Amazon             | FireTV       | Streaming device        |
| Amazon             | FireTV Stick | Streaming device        |
| Philips            | 4650D        | Digital signage display |
| Samsung            | WEX          | Display                 |
| SMART Technologies | AM60         | OPS appliance           |

***

### Supported USB videobars

A USB videobar or separate USB camera, microphone, and speaker must be connected to the display for video conferencing.

| Brand      | Model             |
| ---------- | ----------------- |
| Jabra      | PanaCast 50       |
| Logitech   | MeetUp 2          |
| Huddly     | IQ                |
| Sennheiser | TeamConnect S / M |

***

### Minimum system requirements

| Specification | Requirement                                                                      |
| ------------- | -------------------------------------------------------------------------------- |
| OS            | Android 10 or newer, 64-bit only                                                 |
| Network       | Wired Ethernet (recommended) or Wi-Fi 802.11ac with signal stronger than -60 dBm |


# Android Video Bars (MDM)

{% hint style="info" %}
Coming soon
{% endhint %}

Support for Android-based video bars managed via MDM is coming soon. Check back for updates.


# Requirements


# Network

### Network Requirements

{% content-ref url="/pages/h3g48sU4qwoaLe0eRu6c" %}
[FQDN whitelisting](/mago/requirements/network/fqdn-whitelisting)
{% endcontent-ref %}

{% content-ref url="/pages/Pixa1augjXcsw1rw3ezF" %}
[Ports and services](/mago/requirements/network/ports-and-services)
{% endcontent-ref %}

{% content-ref url="/pages/CaZ4Cny5NtgJvsxiCJ5O" %}
[DNS and NTP](/mago/requirements/network/dns-and-ntp)
{% endcontent-ref %}

### Network and Internet access

It is recommended to use a Gigabit Ethernet network or higher, or a WiFi network, over a dedicated VLAN. Minimum internet bandwidth: 2 Mbps.

{% hint style="warning" %}
Proxy connections are not supported
{% endhint %}

### WiFi Network Tips

Wireless networks can be subject to network interference that leads to degradation in quality. We recommend following your wireless equipment vendor's best practices when setting up a wireless connection to improve video and audio quality and the smoothest possible visual collaboration user experience.

Here are some examples of best practices for setting up your wireless network recommended by various manufacturers:

Deploy wireless equipment, such as access points and routers, that can manage and distribute the bandwidth load across all connected devices in the network.

* Use, as far as possible, access points and routers from a single manufacturer to avoid further congesting the radio spectrum.
* Make sure that the wireless equipment is installed in a manner that reduces or eliminates interference from objects and other equipment.
* Make sure the wireless network shows strong signal strength (a Wi-Fi signal that shows full bars is preferred) on Mago and other devices' screens.
* By default, 5 GHz coverage is prioritized for devices to maximize the highest bandwidth.
* Enable band control to ensure that the 5GHz band is always given higher priority when sharing

  the same network name (SSID) as the 2.4 GHz band.
* Keep wireless channel usage below 50%.
* Keep the firmware of your access point and router up to date with the latest firmware  versions

  and hotfixes.
* Verify that Mago devices and at least one access point are seen with a signal strength of -60

  dBm or greater. A dBm value closer to zero is preferred. Follow the equipment manufacturer's

  recommendations.
* Implement QoS whenever possible to enable real-time monitoring and troubleshooting.

  For additional best practices specific to your wireless network hardware, see the manufacturer's documentation.

### Bandwidth

Minimum bandwidth: 2 Mbps

{% hint style="info" %}
When using third-party video conferencing applications, you will need more bandwidth. Users should refer to the guidelines recommended by each manufacturer.
{% endhint %}

#### Bandwidth for Video Conferencing

{% hint style="warning" %}
A 1080p video stream requires sufficient bandwidth on both the sending and receiving end for every participant.
{% endhint %}

<table><thead><tr><th width="130.13671875">Resolution</th><th width="124.8125">Min framerate</th><th width="125.03125">Max framerate</th><th>Max bitrate (downstream and upstream</th></tr></thead><tbody><tr><td>1080p</td><td>30</td><td>30</td><td>4 M</td></tr><tr><td>720p</td><td>30</td><td>30</td><td>2.5 M</td></tr><tr><td>540p</td><td>30</td><td>30</td><td>2 M</td></tr><tr><td>360p</td><td>30</td><td>30</td><td>1 M</td></tr><tr><td>240p</td><td>15</td><td>15</td><td>650 K</td></tr><tr><td>180p</td><td>7.5</td><td>15</td><td>250 K (350 K if 15 FPS)</td></tr></tbody></table>


# FQDN whitelisting

#### Licensing and Activation

```
api.remago.com
activation.airserver.com
```

#### Mago Agent and Mago Admin Center

```
admin.mago.io
admin-hub.mago.io (HTTPS and WSS protocols, on port 443)
admin-api.mago.io
pod-pmc-production-signalr.azurewebsites.net
api.mago.io
pmc.mago.io
rms.mago.io
prd-rms.mago.io
vmc-api.valarea.com
pmc.valarea.com
prd-rms.valarea.com
rms.valarea.com
```

#### Mago Link Service (Mago Cast protocol)

```
r.magolink.com (HTTPS and WSS protocols, on 443)
magolink.com
share.mago.io (HTTPS and WSS protocols, on 443)
cast.mago.io (HTTPS and WSS protocols, on 443)
cast-turn.mago.io
cast-whip.mago.io
cast-us.mago.io
cast-us-turn.mago.io
magocast.com
vc.mago.io (HTTPS and WSS protocols, on 443)
```

#### Video Conferencing

```
call.mago.io
vc-sdk.mago.io
meet.mago.io (HTTPS and WSS protocols, on 443)
```

**Microsoft Teams**\
For MS365 and Teams Services: [Office 365 URLs and IP address range](https://docs.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide#skype-for-business-online-and-microsoft-teams)\
For Azure Communication Services: <https://learn.microsoft.com/en-us/azure/communication-services/concepts/voice-video-calling/network-requirements>​

**Zoom**\
See: <https://support.zoom.us/hc/en-us/articles/201362683-Zoom-network-firewall-or-proxy-server-settings>​

**Google Meet**\
See: <https://support.google.com/a/answer/1279090?hl=en>​

**Cisco Webex**\
See: <https://help.webex.com/en-us/article/WBX000028782/Network-Requirements-for-Webex-Services>

#### Mago Whiteboard and Mago mobile (iOS / Android) and web apps

```
wb.mago.io
app.mago.io
chat1.mago.io
chat1.valarea.com
globalchat1.azurewebsites.net
meet1.mago.io
meet1.valarea.com
arcrop.mago.io
rgo.li
```

#### Third-party Services

<pre><code><strong>oauth-apple.valarea.com
</strong>oauth-apple.mago.io
oauth-google.valarea.com
oauth-google.mago.io
oauth-msft.valarea.com
oauth-msft.mago.io
oauth-webex.valarea.com
oauth-webex.mago.io
oauth-zoom.valarea.com
oauth-zoom.mago.io
graph.microsoft.com
inputtols.google.com
googleapis.com
autodraw.com
dropbox.com
eu.docusign.net
account.docusign.com
</code></pre>


# Ports and services

Please note that all required network ports for Mago must be **allowed at the VLAN infrastructure level**, not just on individual client devices. This ensures proper communication between Mago and user devices across the network. Make sure your network switches, firewalls, and access points are configured to permit the necessary traffic within and across VLANs.

## Generic ports

<table><thead><tr><th width="99.5625">Port</th><th width="122.33203125">Type</th><th width="142.59765625">Direction</th><th>Service</th></tr></thead><tbody><tr><td>80</td><td>TCP</td><td>Outbound</td><td>HTTP</td></tr><tr><td>443</td><td>TCP</td><td>Outbound</td><td>HTTPS</td></tr><tr><td>53</td><td>TCP/UDP</td><td>Outbound</td><td>DNS (internal or external)</td></tr><tr><td>123</td><td>UDP</td><td>Outbound</td><td>NTP (internal or external)</td></tr></tbody></table>

## Screen sharing protocols

### Mago Link

See [Mago Link](/mago/requirements/presentation/wireless-screen-sharing/mago-link)

### Miracast

See [Miracast](/mago/requirements/presentation/wireless-screen-sharing/miracast)

### AirPlay

See [AirPlay](/mago/requirements/presentation/wireless-screen-sharing/airplay)

### Google Cast

See [Google Cast](/mago/requirements/presentation/wireless-screen-sharing/google-cast)

## Local discovery service of Mago devices (optional)

To use the local discovery service, enable the following ports on the Mago device and network.

Discover more about the discovery service for Mago mobile apps here: [Proximity connection](/mago-mobile-apps/proximity-connection)

<table><thead><tr><th width="99.2890625">Port</th><th width="102.0859375">Type</th><th width="164.1953125">Direction</th><th>Service</th></tr></thead><tbody><tr><td>8034</td><td>TCP</td><td>Both</td><td>Local Discovery Service</td></tr><tr><td>8035</td><td>UDP</td><td>Both</td><td>Local Discovery Service</td></tr></tbody></table>


# DNS and NTP

Mago Essential requires access to DNS services to resolve domain names for functions such as software updates, authentication, and cloud-based services (e.g., magolink.com, admin.mago.io). Accurate time synchronization is also critical for certificate validation and secure communication. Ensure the device can access a reliable NTP server (e.g., time.windows.com or a local NTP source) to maintain correct system time.


# Third-party providers


# Microsoft 365

## How add the Mago enterprise application in your Microsoft 365 tenant and grant admin consent

When using Mago with Microsoft 365 room resources and users, the Mago app for display and Mago mobile app access Microsoft 365 services through the Microsoft Graph and Azure Communication Services APIs. To enable these features, a tenant administrator must grant consent to the Mago enterprise application.

{% hint style="success" %}
Mago is a verified enterprise application in the **Microsoft Entra app gallery** (application ID `17781659-6867-4c77-9ba3-40670305181c)` and it is listed under the official **Azure Marketplace** (see <https://marketplace.microsoft.com/nb-no/product/saas/aad.valarea?tab=overview>).
{% endhint %}

{% stepper %}
{% step %}

### Add the Mago application to your tenant

Open [admin.mago.io](https://admin.mago.io/) and sign in with a Microsoft 365 account that has **Global Administrator**, **Application Administrator**, or **Cloud Application Administrator privileges**. When prompted, review the requested permissions and select "Accept" on behalf of your organization. The Mago application is now registered in your tenant.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FSBktWH6jXKKddXFxxkng%2Fmago-admin-center-signin.jpg?alt=media&amp;token=c43b0523-dd1e-41c8-ad4f-3128de74f9f6" alt="" width="375"><figcaption><p>Mago Admin Center (https://admin.mago.io)</p></figcaption></figure>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FN9mgBPd1TFeHfU552urg%2Fmago-admin-consent.webp?alt=media&amp;token=e5c8903b-50cf-4b05-a05d-8cfe473e7949" alt="" width="375"><figcaption><p>Mago app Permission Request</p></figcaption></figure>
{% endstep %}

{% step %}

### Grant admin consent to the required scopes

To review and grant admin consent to the required scopes in the Mago application permissions:

* Open the [**Azure portal**](https://portal.azure.com/) and sign in with a Microsoft 365 Administrator account.
* Go to Microsoft Entra ID > Enterprise Applications (or search directly for "**Enterprise Applications**").

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FiBdqVUpQpQSLQNL4Bkj2%2Fenterprise-apps.webp?alt=media&amp;token=bb4655ed-312c-4e3f-b80f-c39eb9fc2b96" alt=""><figcaption></figcaption></figure>

* Under the Application list, search for "**Mago**" (Application ID `17781659-6867-4c77-9ba3-40670305181c`).

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FWFi1wmwO2BlhLbgwTSM2%2Fenterprise-apps-mago.webp?alt=media&amp;token=d07d68d8-774a-43d5-af96-76624b67bc67" alt=""><figcaption></figcaption></figure>

* Enter the Mago application, go to **Security** > **Permissions** and verify that admin consent has been granted to the required scopes. To grant admin consent to all the required scopes, click the "Grant admin consent for *YourCompanyName*" button.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F5Hql2RRyQEziNdUZfP4Z%2Fenterprise-apps-mago-grant.webp?alt=media&amp;token=d6b8ad4b-6d29-468c-b84f-0830557e8703" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## Advanced consent options

Below are the official Microsoft guides to grant consent to the Mago app in different ways.

### Tenant-wide consent

{% embed url="<https://learn.microsoft.com/azure/active-directory/manage-apps/grant-admin-consent>" %}

### Single user consent

{% embed url="<https://learn.microsoft.com/entra/identity/enterprise-apps/grant-consent-single-user?pivots=msgraph-powershell>" %}

### Microsoft Intune

In case the device is managed through **Microsoft Intune**, check the app access policies in the Intune settings and allow access to the "Mago" app. Refer to the following guide:

{% embed url="<https://learn.microsoft.com/entra/identity/enterprise-apps/configure-user-consent?pivots=portal>" %}

## Required features and scopes

### Permissions requested by the Mago room app

All permissions are **delegated** permissions, granted on behalf of the Microsoft 365 account linked to the room. Mago requests no application (app only) permissions, so the room can never access data the linked account cannot already access.

Permissions are requested **per capability**. When an administrator enables a capability in the Mago console, the consent screen carries only that capability's scopes. Capabilities left disabled are never requested.

Every capability includes the baseline scopes `openid`, `profile` and `offline_access`.

#### Capabilities and their scopes

<table><thead><tr><th width="165.3984375">Capability</th><th width="184.75">Mago Admin Center</th><th width="231.59765625">Additional scopes</th><th>API</th></tr></thead><tbody><tr><td><strong>Account connection</strong></td><td>"Connect"</td><td><p><code>User.ReadBasic.All</code> <code>Calendars.ReadWrite</code></p><p><code>Mail.Read</code></p><p><code>Mail.Send</code></p></td><td>Graph</td></tr><tr><td><strong>Calendar</strong></td><td>"Calendar"</td><td><p><code>User.ReadBasic.All</code></p><p><code>Calendars.ReadWrite</code></p><p><code>Mail.Read</code></p><p><code>Mail.Send</code></p></td><td>Graph</td></tr><tr><td><strong>Join with connected account (*)</strong></td><td>"Join meetings using the connected account"</td><td><p><code>Teams.ManageCalls</code></p><p><code>Teams.ManageChats</code></p></td><td>Azure Communication Services</td></tr><tr><td><strong>Instant meetings</strong></td><td>"Enable instant meetings"</td><td><p><code>User.ReadBasic.All</code></p><p><code>OnlineMeetings.ReadWrite</code></p></td><td>Graph</td></tr><tr><td><strong>Meeting chat</strong></td><td>"Enable chat"</td><td><p><code>User.ReadBasic.All</code></p><p><code>Chat.ReadWrite</code></p><p><code>ChatMessage.Send</code></p></td><td>Graph</td></tr><tr><td><strong>Join by ID and passcode</strong></td><td>"Join meetings via ID and Passcode"</td><td>none, no account required</td><td>—</td></tr></tbody></table>

(\*) "Join meetings using the connected account" must be enabled before "Enable instant meetings" and "Enable chat", and disabling it also disables both. It requires the linked account to hold a Teams license (see [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements)).

#### What each scope is used for

<table data-search="false"><thead><tr><th width="236.80859375">Scope</th><th>Purpose</th></tr></thead><tbody><tr><td><code>openid</code>, <code>profile</code></td><td>Sign in with the room account and read its name and email address</td></tr><tr><td><code>offline_access</code></td><td>Keep the room signed in without an administrator reauthorizing it every 60 minutes</td></tr><tr><td><code>Calendars.ReadWrite</code></td><td>Read the room agenda to display upcoming meetings, create the event when a meeting is booked from the room, write the join link into the event, extend the event when a meeting runs longer than scheduled, and release the room when a meeting ends early</td></tr><tr><td><code>Mail.Read</code></td><td>Read invitation messages in the room mailbox to recover the meeting join link. This runs as part of the ordinary calendar refresh: for the events in the displayed time window the room also reads the matching invitation, because a forwarded or accepted invitation frequently carries the join link only in the mail body and not in the calendar item</td></tr><tr><td><code>Mail.Send</code></td><td>Send meeting material and invitations from the room account</td></tr><tr><td><code>User.ReadBasic.All</code></td><td>Look up participants in the organization directory when inviting them to a meeting, and resolve participant names and addresses in the call roster. Reads basic directory profile data only, never mailbox content</td></tr><tr><td><code>OnlineMeetings.ReadWrite</code></td><td>Create an ad hoc Teams meeting when an instant meeting is started from the room</td></tr><tr><td><p><code>Chat.ReadWrite</code></p><p><code>ChatMessage.Send</code></p></td><td>Read and send messages in the chat of the meeting in progress</td></tr><tr><td><p><code>Teams.ManageCalls</code></p><p><code>Teams.ManageChats</code></p></td><td>Azure Communication Services scopes: Join Teams meetings as the connected account</td></tr></tbody></table>

#### Notes for administrators

* Connecting the Microsoft 365 account already consents to the calendar and mail scopes, before any individual capability is enabled.
* At runtime the room's access token carries every scope consented for the Mago application, not only those of the capability in use. The per capability separation applies at consent time.
* Disabling a capability in the Mago console updates the Mago configuration only. It does not revoke the consent or the refresh token, which must be revoked in Microsoft Entra ID.
* **Mago Whiteboard for Windows (version <= 7.5)** additionally uses `Files.ReadWrite.All` and `User.Read` to open and save whiteboard recaps and session documents on OneDrive and SharePoint document libraries.
* A room calendar can also be connected through **Microsoft Exchange on premises** (EWS with a service account), which requires no OAuth scopes at all.

### Permissions requested by the Mago mobile app (iOS / Android)

All permissions are **delegated** permissions, granted on behalf of the signed in Microsoft 365 user. The app requests them **incrementally**: each scope is requested when the user first uses the capability that needs it, not all at sign in.

<table><thead><tr><th width="220.54296875">Capability</th><th width="211.00390625">Scope</th><th>API</th></tr></thead><tbody><tr><td>Sign in</td><td><code>User.Read</code></td><td>Graph</td></tr><tr><td>Personal calendar</td><td><code>Calendars.ReadWrite</code></td><td>Graph</td></tr><tr><td>OneDrive files</td><td><code>Files.ReadWrite.All</code></td><td>Graph</td></tr><tr><td>SharePoint document libraries</td><td><code>Sites.Read.All</code></td><td>Graph</td></tr><tr><td>Join Teams meetings</td><td><p><code>Teams.ManageCalls</code></p><p><code>Teams.ManageChats</code></p></td><td>Azure Communication Services</td></tr></tbody></table>

<table><thead><tr><th width="243.421875">Scope</th><th>Purpose</th></tr></thead><tbody><tr><td><code>User.Read</code></td><td>Sign in and read the signed in user's own profile</td></tr><tr><td><code>Calendars.ReadWrite</code></td><td>Read the user's calendar to list meetings, and create or update an event when a meeting is booked from the app</td></tr><tr><td><code>Files.ReadWrite.All</code></td><td>Browse, open, import and save documents on the user's OneDrive</td></tr><tr><td><code>Sites.Read.All</code></td><td>Browse and open documents in SharePoint document libraries the user can access</td></tr><tr><td><p><code>Teams.ManageCalls</code></p><p><code>Teams.ManageChats</code></p></td><td>Join Teams meetings and take part in the meeting chat as the signed in user</td></tr></tbody></table>


# Google Workspace

## How to add the Mago application in your Google Workspace domain and grant access

When using Mago with Google Workspace room resources and users, the Mago app for display and Mago mobile app access Google services through Google APIs. To enable these features, a Google Workspace administrator must authorize the Mago application in the domain.

{% hint style="success" %}
Mago is a Google OAuth verified application.
{% endhint %}

{% stepper %}
{% step %}

### Authorize the Mago application

Open [admin.mago.io](https://admin.mago.io/) and sign in with a Google Workspace account that has Super Admin privileges. When prompted, review the requested permissions and approve. The Mago application is now authorized in your domain.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FptqZeG1KKA7Q7fEhjAQB%2Fmago-admin-login.webp?alt=media&amp;token=1fc130ad-9776-40dc-a31a-fc435119cf84" alt="" width="351"><figcaption></figcaption></figure>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FInoQcmkioq9RJMDOtDjL%2Fmago-admin-center-google-signin.webp?alt=media&amp;token=ec711228-8371-4e61-b9a4-381cb93b3ea4" alt="" width="375"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Verify third-party app access and allow the Mago application if restricted

When room resources or users sign in later during device activation, Google will prompt them to approve additional scopes (such as calendar and meeting access).

{% hint style="warning" %}
If your domain restricts third-party application access, these prompts will be blocked with a **`400 admin_policy_enforced`** error.
{% endhint %}

#### Check third-party app access policy

To check if your domain restricts third-party application access:

* Open the [Google Admin console](https://admin.google.com/)
* Go to Security > Access and data control > **API controls**
* Click on **Settings**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FVI5V0TmYfaAJIY45So49%2Fgoogle-admin-8.webp?alt=media&amp;token=749f1b43-8521-432a-9807-d8fbd724d0a1" alt=""><figcaption></figcaption></figure>

* Under "Unconfigured third-party apps", verify which access level is selected. If it is set to "Allow users to access any third-party apps", no further action is required. If access is restricted, proceed with the next step to pre-authorize the Mago application at domain level.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FfFTtp3smBt53QIl3T0mn%2Fgoogle-admin-9.webp?alt=media&amp;token=bd3a67f7-3abe-4333-b1db-a8ce670196c0" alt=""><figcaption></figcaption></figure>

#### Pre-authorize the Mago application

If your domain restricts third-party application access:

* Open the [Google Admin console](https://admin.google.com/)
* Go to Security > Access and data control > API controls > **Manage App Access**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FLBO8JjSrXhwrYDA1ehyy%2Fgoogle-admin-1.webp?alt=media&amp;token=009551d7-3cf1-49fe-a4b0-a3017bd82321" alt=""><figcaption></figcaption></figure>

* Click on "Configure new app"

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2Fn9wVzHleirZv1yNKXlUO%2Fgoogle-admin-2.webp?alt=media&amp;token=bace8861-3ebd-4fb6-90d3-9c4d173d2dcd" alt=""><figcaption></figcaption></figure>

* Search for the following Mago app client IDs and add them as trusted app (one by one).

<table><thead><tr><th width="148.30078125">Application</th><th>Client ID</th></tr></thead><tbody><tr><td>Mago app for display / web</td><td><code>436832489008-nl03st57foo9su4qg5mddnadhl7ql5oe.apps.googleusercontent.com</code></td></tr><tr><td>Mago mobile app for Android</td><td><code>436832489008-5ie2c8hme7jucfh4vn4hul7sdkm8mhuk.apps.googleusercontent.com</code></td></tr><tr><td>Mago mobile app for iOS</td><td><code>436832489008-l3lejr6nqvgmevau7u999gm6c17jdci2.apps.googleusercontent.com</code></td></tr></tbody></table>

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FDV0BTak78sohRm8CuHTU%2Fgoogle-admin-3.webp?alt=media&amp;token=640cf9e0-aa1c-4256-b7f2-38c523ae2e8f" alt=""><figcaption></figcaption></figure>

* Set your desired Scope and click **Continue**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FvACXSCMdnXaHQ3hwj7Mr%2Fgoogle-admin-4.webp?alt=media&amp;token=2a835ece-3797-4eb8-8e30-77feb62bba04" alt=""><figcaption></figcaption></figure>

* Set the app as **Trusted**, then click **Continue**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F5F0gatfqwQOSK73GFKlI%2Fgoogle-admin-5.webp?alt=media&amp;token=e7267572-68c7-476d-b975-5fee7fb8691e" alt=""><figcaption></figcaption></figure>

* Review and click **Finish**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FTuwZjSqWikY1JVFXHdpE%2Fgoogle-admin-6.webp?alt=media&amp;token=43656f5d-1749-4b55-b5db-dadeb013b3bb" alt=""><figcaption></figcaption></figure>

* Make sure to repeat the steps to configure all 3 Mago app client IDs.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FnXEy7r2WmJajKoenAsQk%2Fgoogle-admin-7.webp?alt=media&amp;token=db859a20-1821-444f-b82f-a28b6b06317b" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
This ensures that users and room resources are not blocked when Mago requests additional scopes (such as calendar access) during device activation or configuration.
{% endhint %}
{% endstep %}
{% endstepper %}

## Required features and scopes

| Mago – Feature                                                                                                                     | Required Scope Permissions                                                              |
| ---------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| Log in with room account and view room name and email address                                                                      | `auth/userinfo.email`                                                                   |
| Select the room calendar to list upcoming meetings on the display                                                                  | `auth/calendar.readonly`                                                                |
| Create a new instant meeting as a Host and book the room calendar                                                                  | `auth/calendar.events`                                                                  |
| Search for Google Directory contacts to add recipients to meeting invitations                                                      | <p><code>auth/contacts.readonly</code><br><code>auth/contacts.other.readonly</code></p> |
| Browse, import, open and view cloud storage files (Google Drive) during a Mago Workspace or Mago Stage session (file presentation) | <p><code>auth/drive</code></p><p><code>auth/drive.file</code></p>                       |

| Mago Workspace app – Feature                                                                                                       | Required Scope Permissions                                        |
| ---------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| Log in to Mago Workspace via a personal Google account, view the account name and email address                                    | `auth/userinfo.email`                                             |
| Choose a personal calendar to list your personal meetings in the app and start them in the meeting room                            | `auth/calendar.readonly`                                          |
| Create a new instant meeting as a Host and book the room calendar                                                                  | `auth/calendar.events`                                            |
| Browse, import, open and view cloud storage files (Google Drive) during a Mago Workspace or Mago Stage session (file presentation) | <p><code>auth/drive</code></p><p><code>auth/drive.file</code></p> |


# Zoom

## Verified Mago App for Zoom Marketplace

If you want to activate the instant meeting feature and Host access to Zoom meetings, you need to authorize the verified Mago app on the Zoom Marketplace.

{% hint style="success" %}
Note: It is not required for **guest access** to Zoom meetings.
{% endhint %}

The app can be reached at the following link:

{% embed url="<https://marketplace.zoom.us/apps/b_8zLZb8QQa-_ray1PWAKg>" %}

## Required features and scopes

| Mago – Feature                                                                                     | Required Scope Permissions                                        |
| -------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| Search for directory users to invite when starting an instant Zoom meeting from the room calendar. | <p>View user contacts</p><p><code>contact:read</code></p>         |
| Start or end an instant Zoom meeting directly from the room calendar.                              | <p>View and manage meetings</p><p><code>meetings:write</code></p> |
| View the room user's email and revoke a token when requested by the user (account logout).         | <p>View user information</p><p><code>user:read</code></p>         |
| Receive a ZAK token when requested by the user.                                                    | <p>View user's ZAK token</p><p><code>user\_zak:read</code></p>    |

{% hint style="info" %}
Before integrating your account in Mago Room it is required to approve the install of the Mago app in the Zoom marketplace, as explained below:
{% endhint %}

1. Visit [**https://marketplace.zoom.us**](https://marketplace.zoom.us) and sign in with the Zoom account used by the room.
2. Search for the "Mago" app and **Approve the install of the app** by activating the corresponding switch.

{% hint style="warning" %}
For Mago **4.1 and above**, please refer to the "Mago Room" app:

<https://marketplace.zoom.us/apps/b_8zLZb8QQa-_ray1PWAKg>

For Mago **4.0 and below (formerly "Valarea")**, please refer to the "Valarea Room 4" app:

<https://marketplace.zoom.us/apps/rYVYMDRKTXm0jc-O1_na7w>
{% endhint %}

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FdFbx4w0SL9PUb6z1CE1S%2FScreenshot%202023-02-11%20alle%2006.57.35.png?alt=media&amp;token=23394873-5e1c-445b-ad1c-95a94430ba9b" alt=""><figcaption></figcaption></figure>

### Zoom accounts that restrict Meeting SDK apps

Mago Room joins Zoom meetings through the Zoom Meeting SDK, using the verified **Mago Room** app. Some organizations configure their Zoom account to block Meeting SDK apps. If Mago Room cannot join the meetings of a specific organization, please ask the Zoom administrator of that organization to check that Meeting SDK apps are not blocked, and if they are, to add Mago Room to the allowed apps.

{% hint style="warning" %}
This setting belongs to the Zoom account that **hosts** the meeting, not to the room.
{% endhint %}

| Detail      | Value                                                     |
| ----------- | --------------------------------------------------------- |
| App name    | Mago Room                                                 |
| Marketplace | <https://marketplace.zoom.us/apps/b_8zLZb8QQa-_ray1PWAKg> |
| Client ID   | `DHGCDk6DShGhWQhRGbtFHg`                                  |

### How to disconnect a Zoom account from Mago Room (Token revocation)&#x20;

If you want to disconnect a Zoom account from Mago Room, please follow these steps:

* Open the Mago Room Wizard or Settings
* Navigate to the "Instant Meeting" step or section
* Locate the Zoom option and press "Disconnect"

{% hint style="info" %}
Mago Room will automatically revoke the authorization token. In order to enable Zoom instant meetings again, you will have to connect to your account and complete the OAuth process again.
{% endhint %}

### How to deauthorize the app

If you want to deauthorize the Mago or Mago Room app, please follow these steps:

* Visit [**https://marketplace.zoom.us**](https://marketplace.zoom.us) and sign in with the Zoom account used by the room.
* Deauthorize by turning the switch off (see image)

{% hint style="info" %}
You can also manage authorization for single users under the "Manage" section
{% endhint %}


# Webex

## Verified Mago App for Webex App Hub

If you want to turn on the instant meeting feature and host access to Webex meetings, you must authorize the verified Mago app on the Webex Hub app. You can authorize and add the app by logging in with your room account in the Mago Settings, Instant Meetings section (see dedicated chapter).

{% hint style="success" %}
Note: It is not required for **guest access** to Webex meetings.
{% endhint %}

## Required features and scopes

| Mago – Feature                                                                                                                    | Required Scope Permissions                                                                                                                                                                                                                |
| --------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p>Start or end an instant Webex meeting directly from the room calendar.<br>Log in as a Guest via the external meeting link.</p> | <p><code>meeting:schedules\_read</code><br><code>meeting:schedules\_write</code><br><code>meeting:preferences\_read</code></p>                                                                                                            |
| View meeting controls                                                                                                             | `meeting:controls_read`                                                                                                                                                                                                                   |
| View meeting participants                                                                                                         | `meeting:participants_read`                                                                                                                                                                                                               |
| Use the built-in JavaScript Web Client (official)                                                                                 | <p><code>spark:all spark:calls\_read</code><br><code>spark:devices\_read</code><br><code>spark:devices\_write</code><br><code>spark:organizations\_read</code><br><code>spark:places\_read</code><br><code>analytics:read\_all</code></p> |


# Apple

## Verified Mago App for Apple Sign in

When using Mago iOS / MacOS app with access via Apple account, simply log in via "Sign in with Apple" and authorize the reading of the full name and email address (in plain text or via Apple relay).

## Required features and scopes

| Mago mobile app – Feature                                  | Required Scope Permissions |
| ---------------------------------------------------------- | -------------------------- |
| Display your name and email, which you can use to register | `.fullName.email`          |


# Dropbox

## Verified Mago app for Dropbox

In the Mago digital Whiteboard, both on Mago and on Mago mobile app for iOS / Android, it is possible to import files as objects and/or save PDF whiteboard recaps on a Dropbox account. Simply log in with any account and authorize the necessary scopes.

## Required features and scopes

| Mago Pro / Mago app – Feature                                                                                          | Required Scope Permissions                                                      |
| ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| View account name                                                                                                      | `account_info.read`                                                             |
| <p>Browse files, view, and import files to the whiteboard<br>Save PDF recaps of the whiteboard to a desired folder</p> | <p><code>files.metadata.write</code></p><p><code>files.content.write</code></p> |
|                                                                                                                        |                                                                                 |


# Calendar

## Supported providers

Mago supports the following room calendar providers:

* Microsoft 365
* Google Workspace
* Microsoft Exchange (On Premises)
  * Exchange 2016 (default)
  * Exchange 2015, 2015 10 05
  * Exchange 2013, 2013 SP1
  * Exchange 2010, 2010 SP1, 2010 SP2
  * Exchange 2007 SP1


# Microsoft 365 calendar


# Setup a room resource

## 1. Login to Microsoft 365 Admin Center

Go to <https://admin.microsoft.com> and login with an administrator account.

![Microsoft Admin Center Login](https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2FbpP2hYI1Myy7hMs_%2F-MXhmC7L8XIcUxQkbml2%2F-MXhnIwm8guNu9Q2FGR4%2F1.jpg?alt=media\&token=0cbfbc80-dd1e-466a-aab5-60eb27eb3e50)

## 2. Access **Rooms** & Equipment and Add a New Resource

1. Choose "Rooms & equipment" in the "Resources" menu from the left sidebar
2. Select "Add resource"

![Rooms & equipment page](https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2FbpP2hYI1Myy7hMs_%2F-MXhmC7L8XIcUxQkbml2%2F-MXhoqAhhf_4WJe0VFkm%2F2.jpg?alt=media\&token=c1ae4b41-da65-4b47-a075-77e682a2afcb)

## 3. Add a New Resource

1. Enter the required resource's Name
2. Enter the required resource's Email
3. Enter optional fields, such as Capacity, Location and Phone number
4. Press "Save"

![Add a new resource](https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2FbpP2hYI1Myy7hMs_%2F-MXhmC7L8XIcUxQkbml2%2F-MXhpOCRLl6tQk9zYghY%2F3.jpg?alt=media\&token=0fd19517-4191-424c-8942-4ed241aef84b)

## 4. Check Booking Options

After the new resource has been created, press "Edit booking options"

![Resource created](https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2FbpP2hYI1Myy7hMs_%2F-MXhmC7L8XIcUxQkbml2%2F-MXhpfMt1mHzoSFSwegX%2F4.jpg?alt=media\&token=4e2ca231-858a-4b69-90ee-538a51528ab4)

Check that the "Auto accept meeting requests" option is selected. This will ensure the proper functioning of the Room resource

![Auto accept meeting requests](https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2FbpP2hYI1Myy7hMs_%2F-MXhmC7L8XIcUxQkbml2%2F-MXhq2OjSROnDYC1l1IM%2F5.jpg?alt=media\&token=81e88a01-f5c7-489e-975a-457311f9e264)

## 5. Set a Room Password

From the left sidebar:

1. Select Users > Active Users&#x20;
2. Find the newly created room resource and press the key icon ("Reset password")

![Reset password (1)](https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2FbpP2hYI1Myy7hMs_%2F-MXhmC7L8XIcUxQkbml2%2F-MXhqhIlW6vPAQxpImP8%2F6.jpg?alt=media\&token=56a1b549-a03a-4387-a134-03f4a4a49a7a)

1. Set a room password
2. Check that, "Require this user to change their password when they first sign in" option is not selected
3. Press "Reset password"

![Reset password (2)](https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2FbpP2hYI1Myy7hMs_%2F-MXhmC7L8XIcUxQkbml2%2F-MXhr3ZkPxciBwmXjszG%2F7.jpg?alt=media\&token=ae48d186-d52f-46ac-957f-aca2907d07d0)

When the password has been reset, you can choose to close or to email the sign-in info to your email. In this case:

1. Check the "Email the sign-in info to me" option
2. Add your email or multiple emails (divided by ";")
3. Press "Send email and close"

![Send sign-in details](https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2FbpP2hYI1Myy7hMs_%2F-MXhmC7L8XIcUxQkbml2%2F-MXhrd798lbCu1Dn7kwT%2F8.jpg?alt=media\&token=42749410-59c3-4fab-be36-a43fc95ff13a)


# Configure a room resource

This page will help you fix event titles and accept resource requests automatically for room resource calendars.

## How to enable the display of meeting titles

By default events scheduled on the meeting room calendars in Exchange and Microsoft 365 will show the name of the organizer instead of the actual event title, for privacy reasons (see Microsoft KB here <https://docs.microsoft.com/en-us/exchange/troubleshoot/client-connectivity/calendar-shows-organizer-name>). To make the most of Mago Room, you will want more descriptive titles. This is easily fixed through some administrative configuration via Powershell.

{% hint style="warning" %}
**You'll need to create your room resources before you can apply the fix. For newly created room resources, you will need to repeat this process again.**
{% endhint %}

{% stepper %}
{% step %}

#### Run the Azure Powershell or Azure Cloud Shell as an administrator.

{% endstep %}

{% step %}

#### Sign in with Modern Authentication

Enter the following command and follow the instructions:

```
Connect-ExchangeOnline
```

{% endstep %}

{% step %}

### Run the following command

Lastly, run this command, replacing `{RESOURCEMAILBOX}` with the room resource UPN or email (e.g. <room@company.com>)

* For Exchange Server 2016, Exchange Server 2013 or Exchange Server 2010

`Set-CalendarProcessing -Identity {RESOURCEMAILBOX} -DeleteSubject $False -AddOrganizerToSubject $False -DeleteComments $false -RemovePrivateProperty $false`

* For Exchange Server 2007

`Set-MailboxCalendarSettings -Identity {RESOURCEMAILBOX} -AutomateProcessing AutoAccept -AddOrganizerToSubject $False -DeleteSubject $False -DeleteComments $false -RemovePrivateProperty $false`

This will allow Mago to correctly retrieve an event's title and description for every room resource. Events scheduled on the room calendar will now show up in with the correct name. Private events will remain flagged as private.
{% endstep %}
{% endstepper %}

## How to enable meeting invitations from people outside your organization (optional)

To enable the receipt of invitations to room resources from users in domains not belonging to your tenant, simply set the "`-ProcessExternalMeetingMessages`" parameter to `$true` for the room resource, using PowerShell. Example PowerShell command, replacing `{RESOURCEMAILBOX}` with the room resource UPN or email (e.g. <room@company.com>):

`Set-CalendarProcessing -Identity {RESOURCEMAILBOX} -ProcessExternalMeetingMessages $true`

Refer to this guide for more information:

{% embed url="<https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/set-calendarprocessing?view=exchange-ps>" %}

## How to disable chat history for meeting room resources in Microsoft Teams for security and privacy reasons

Follow this guide to create a messaging policy and apply it to the room resources used within Mago.

{% embed url="<https://learn.microsoft.com/en-us/answers/questions/1320897/i-want-to-disable-chatting-function-in-microsoft-t>" %}


# Google Workspace calendar

### Create and configure a room resource

To create buildings and rooms in your Google Workspace admin account, follow the official guide:

{% embed url="<https://support.google.com/a/answer/1033925?hl=en>" %}

After you created the resource, see the guide on how to share its calendar with the service user for meeting rooms:

{% embed url="<https://support.google.com/a/answer/1034381?hl=en>" %}

### Choose the account pattern based on how the room will be used

Mago needs a Google account (with permission on the room's resource calendar) to read events, book the resource, and, if enabled, host instant meetings (Google Meet calls started directly from the room).

Two account patterns are supported. The right one depends on whether **Instant meeting** is enabled on the room.

#### Pattern A, calendar only: single shared service account

If the room will only display and join scheduled meetings, and **no instant meetings** will be started from the room, a single shared account (e.g. `rooms@mydomain.com`) with access to the resource calendars of all rooms is sufficient.

In the Mago calendar settings, log in once with this account and select the correct resource calendar for each room.

This is the simplest pattern to deploy and maintain when instant meetings are not in scope.

#### Pattern B, with Instant meeting: dedicated account per room

When the **Instant meeting** feature is enabled for Google Meet, the account signed in on the room becomes the **host** of any instant Meet call started from that room. For this reason, each room must have its own dedicated Google account (for example `meetingroom-london@mydomain.com`), with permission on that specific resource calendar.

{% hint style="warning" %}
Sharing a single account across multiple rooms in this scenario is not supported: the same Google user cannot cleanly host two concurrent Meet calls, and the shared identity would appear as participant in every meeting started from any room at the same time.
{% endhint %}

A dedicated account per room avoids this and also gives each room its own host identity in Meet: the display name of the per-room Google account is what other participants see as the meeting host.

#### What users see in both patterns

Three distinct names are involved, each coming from a different source:

| Where it appears                                              | Where it comes from                                       |
| ------------------------------------------------------------- | --------------------------------------------------------- |
| Room display (screen of the room)                             | **Device name**, configured in Mago from the Admin Center |
| Meeting invitations and booking UX (when users book the room) | **Resource name**, from Google Workspace                  |
| Host / participant identity inside Google Meet                | **Display name of the signed-in Google account**          |

These three names are independent and can be set separately. Admins typically align them for consistency, but there is no technical requirement to do so.

The account pattern (A or B) only affects the third one, the **host identity of instant meetings**: in Pattern A the shared service account is the host, in Pattern B the per-room dedicated account is the host.

#### Summary

| Scenario on the room                                        | Recommended account pattern                                          |
| ----------------------------------------------------------- | -------------------------------------------------------------------- |
| Calendar only (display and join scheduled meetings)         | Single shared service account with access to all resource calendars  |
| Instant meeting enabled (Google Meet started from the room) | Dedicated account per room, with permission on the resource calendar |


# Microsoft Exchange calendar (On Premises)

## How to create a room resource

Follow the official guide at the following link, to create a room resource:

{% embed url="<https://learn.microsoft.com/en-us/exchange/recipients/room-mailboxes?view=exchserver-2016>" %}


# Video Conferencing


# Supported providers

Mago supports joining meetings from many videoconferencing providers. This is possible through official SDK integrations as well as through the providers’ web or desktop clients.

{% hint style="info" %}
Mago does not include any desktop clients from third-party video conferencing providers. If you prefer to use a desktop client instead of the web client, your IT administrator is responsible for installing it.
{% endhint %}

{% hint style="warning" %}
For video conferencing providers that are already integrated into Mago through an official SDK, such as Zoom, there is no need to install the desktop client. Installing the desktop client can conflict with the SDK and may cause unexpected issues.
{% endhint %}

By integrating with the official clients, whether web, desktop or SDK, Mago provides all available features for supported video conferencing providers, always kept up to date. The table below summarizes the supported providers and the available options to join or host meetings.

{% hint style="success" %}
**Guest join** is free and **does not require any user or room license**.

Starting a meeting as a **host (instant meeting)**, however, **requires a user or room license** for the specific video conferencing system. See the [Licensing requirements](/mago/requirements/video-conferencing/licensing-requirements) page for more details.
{% endhint %}

|                       | <p><strong>Guest join</strong></p><p><strong>from calendar or direct link</strong></p> | <p><strong>Guest join</strong></p><p><strong>with meeting ID and password</strong></p> | **Start a meeting as host (instant meeting)** | **Client integration and support** |
| --------------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | --------------------------------------------- | ---------------------------------- |
| **Mago Meet**         | Yes                                                                                    | Yes                                                                                    | Yes                                           | Web Client                         |
| **Microsoft Teams**   | Yes                                                                                    | Yes                                                                                    | Yes (requires license)                        | Azure Communication Services (\*)  |
| **Zoom**              | Yes (requires authenticated Zoom user)                                                 | Yes (requires authenticated Zoom user)                                                 | Yes (requires license)                        | SDK (Windows or Web)               |
| **Cisco Webex**       | Yes                                                                                    | Yes                                                                                    | Yes (requires license)                        | Web SDK                            |
| **Google Meet**       | Yes                                                                                    | Yes                                                                                    | Yes (requires license)                        | Web Client                         |
| **GoTo**              | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |
| **Lifesize**          | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |
| **BlueJeans**         | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |
| **GoToMeeting**       | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |
| **Join.me**           | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |
| **Ring Central**      | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |
| **Dialpad**           | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |
| **Zoho Meetings**     | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |
| **Whereby**           | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |
| **InFocus ConX**      | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |
| **ClearOne**          | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |
| **Collaborate Space** | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |
| **Skype**             | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |
| **Cisco Jabber**      | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |
| **BigBlueButton**     | Yes                                                                                    | No                                                                                     | No                                            | Web Client                         |

(\*) Some Teams features are not available, either to start them or to see them when another participant uses them. This includes Microsoft Whiteboard, PowerPoint Live, live transcription and captions. If a participant needs to present slides to the room, sharing the screen (or the PowerPoint window) works normally and supports any content.


# Licensing requirements

## Joining meetings as a guest

With Mago, joining meetings as a guest with the supported video conferencing providers is free and does not require any user or room license.

{% hint style="info" %}
Beginning March 2, 2026, joining Zoom meetings from Mago will require a connected and authorized Zoom user account. This applies to all join methods, including Meeting ID and passcode, as well as starting new meetings. Make sure a Zoom user is connected in your organization settings to ensure uninterrupted access.
{% endhint %}

## Joining meetings as a host

With Mago, starting or joining a meeting as a host requires a license assigned to the account for the specific video conferencing provider.

<table><thead><tr><th width="169.296875">Provider</th><th>Supported account types</th><th>Supported licenses</th></tr></thead><tbody><tr><td><strong>Mago Meet</strong></td><td>Mago room<br>Mago app user</td><td>Mago room Pro license<br>Mago app user Pro license</td></tr><tr><td><strong>Microsoft Teams</strong></td><td>Microsoft Azure Communication Services: anonymous guest join or authenticated (licensed) user</td><td><p>Microsoft Teams Essentials</p><p>Microsoft Teams Enterprise</p><p>Microsoft 365 Business Basic Microsoft 365 Business Standard</p><p>Microsoft 365 Business Premium</p></td></tr><tr><td><strong>Zoom</strong></td><td>Standard user account (not a room account)</td><td><p>Basic (with limitations)</p><p>Pro<br>Business<br>Business Plus</p><p>Enterprise</p><p>Zoom Rooms</p></td></tr><tr><td><strong>Cisco Webex</strong></td><td>Standard user</td><td><p>Free (with limitations)</p><p>Starter<br>Business<br>Enterprise</p></td></tr><tr><td><strong>Google Meet</strong></td><td>Standard user</td><td><p>Free<br>Business Starter</p><p>Business Standard</p><p>Business Plus</p><p>Enterprise</p></td></tr></tbody></table>


# Authenticated Calls

This article explains the requirements needed to enable Authenticated Calls in Mago, allowing meetings to be joined using an authenticated user or room account instead of as a guest.

## Authenticated Calls in Mago

Authenticated Calls allow Mago to join video conferencing meetings using a verified identity instead of joining as a generic guest participant.

Depending on the platform configuration, meetings can be joined using:

• an authenticated user account\
• an authenticated account associated with the meeting room

This allows the meeting system to appear as a recognized participant within the conferencing platform.

Authentication is supported across multiple conferencing platforms, including Microsoft Teams, Google Meet, Zoom, and Webex. The available authentication methods may vary depending on the platform.

## Benefits of Authenticated Calls

### Recognized participant identity

When joining a meeting with authentication, the participant appears with the correct user or room name instead of a generic device name.

### Reduced lobby or waiting room interruptions

Authenticated participants from the same organization can often join meetings directly without waiting for manual approval, depending on the platform’s meeting policies.

### Better integration with conferencing platforms

Authentication allows the conferencing platform to treat the participant as a trusted identity, improving compatibility with meeting features and organizational policies.

### Flexible deployment options

Authenticated calls can be configured using individual user accounts or dedicated accounts associated with meeting rooms, depending on the room setup and conferencing platform capabilities.

## Authentication modes supported by Mago

### Authenticated user join

In this mode, a user signs in with their conferencing account on their personal device, such as a smartphone or laptop.

Once authenticated, the user connects their device to the meeting room system. This can be done, for example, by scanning a QR code displayed on the room screen.

The authentication is then securely transmitted to the room system, allowing the meeting to be joined using the user’s identity.

This model is commonly used in:

• BYOM environments\
• shared meeting spaces\
• scenarios where users temporarily authenticate the room for the duration of a meeting

In this configuration, the meeting participant appears as the authenticated user.

### Authenticated room join

In some deployments, the meeting room itself can authenticate using a dedicated account associated with the room.

In this configuration, the meeting system joins meetings using the identity assigned to the room, allowing scheduled meetings to be joined with a consistent room identity.

This approach is commonly used in permanent meeting spaces where the room regularly joins meetings as a recognized participant.

{% hint style="info" %}
Note that support for room resource authentication depends on the conferencing platform.
{% endhint %}


# Authenticated Calls with Microsoft Teams

## Prerequisites

{% hint style="warning" %}
**An active Azure subscription is required.**\
Registering the Azure Communication Services (ACS) service principal in your tenant only works if the tenant has an **active Azure subscription** linked. If you don't have one, create/activate a subscription in the [Azure portal](https://portal.azure.com/) before proceeding. Otherwise the service principal creation will fail.

If your tenant doesn't have one, follow the official Microsoft guide to create it: <https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/create-subscription>
{% endhint %}

You will also need:

* **Global Administrator** (or Privileged Role Administrator) rights on the Microsoft 365 tenant
* Your **Tenant ID** (Entra ID → Overview)
* PowerShell 5.1 or PowerShell 7+

## Requirements

To enable authenticated calls with Microsoft Teams, the following prerequisites must be met.

{% stepper %}
{% step %}

### Azure Communication Services service principal

Microsoft Teams interoperability for third party applications relies on **Azure Communication Services (ACS)**.

To allow authenticated calls, the Microsoft tenant must contain the **Azure Communication Services service principal**. This component allows applications to authenticate Teams identities and join meetings through the Microsoft communication APIs.

#### 🔍︎ Check if the Azure Communication Services service principal is installed

An administrator can verify whether the ACS service principal already exists in the tenant.

1. Sign in to the [Azure portal](https://portal.azure.com/)
2. Go to Microsoft Entra ID > Enterprise Applications > **All Applications**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FiBdqVUpQpQSLQNL4Bkj2%2Fenterprise-apps.webp?alt=media&amp;token=bb4655ed-312c-4e3f-b80f-c39eb9fc2b96" alt=""><figcaption></figcaption></figure>

3. Clear any filters that may be applied

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FthP8jIMRChLM9OkDfxcK%2Facs1.webp?alt=media&amp;token=dea14368-16f9-4bc0-a85c-7b478420e19e" alt=""><figcaption></figcaption></figure>

4. In the search field, search for "Azure Communication Services"

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2Ftmr6Jis6Cy04UGEJogGw%2Facs2.webp?alt=media&amp;token=f8fede73-4490-4fb1-922a-0328f5b9a04b" alt=""><figcaption></figcaption></figure>

If the application appears in the list, the **ACS service principal is already installed** and no further action is required.

If the application does not appear in the list, follow the next steps to **proceed with the installation**.

#### ✅ Installing the Azure Communication Services service principal

If the ACS service principal is not present in the tenant, it must be created by an administrator.

#### Step 1. Open PowerShell

Open the Azure Portal and start a PowerShell session with administrative privileges.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FFPJTNBUlRoeyfsMvL3GZ%2Facs3.webp?alt=media&amp;token=5695d528-c11f-481e-a197-1b63d9360e4c" alt=""><figcaption></figcaption></figure>

#### Step 2. Install the Microsoft Graph module (if not already installed)

```
Install-Module Microsoft.Graph -Scope CurrentUser
```

#### Step 3. Connect to your tenant

Replace `TENANT_ID` with your tenant ID. Find your tenant ID [here](https://entra.microsoft.com/#view/Microsoft_AAD_IAM/TenantOverview.ReactView).

```
Connect-MgGraph -TenantId "TENANT_ID" -Scopes "Application.ReadWrite.All"
```

A Microsoft authentication URL or window will appear where the administrator must sign in.

#### Step 4. Create the Azure Communication Services service principal

Run the following command:

```
New-AzureADServicePrincipal -AppId "1fd5118e-2576-4263-8130-9503064c837a"
```

This registers the **Azure Communication Services service principal** in the tenant and enables authenticated Teams calls for supported applications.

#### (Optional) Using Azure CLI instead

If you prefer not to install PowerShell modules, you can achieve the same with the Azure CLI:

```
az login --tenant TENANT_ID
az ad sp create --id 1fd5118e-2576-4263-8130-9503064c837a
```

{% endstep %}

{% step %}

### Microsoft Teams license

An account with an active Microsoft Teams license is required in order to authenticate and join Teams meetings. The specific license type depends on the organization’s Microsoft 365 subscription.
{% endstep %}
{% endstepper %}

## Setup scenarios

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FCk4wWPbJcS629kuSIIgo%2Fmago-authenticated-calls.jpg?alt=media&amp;token=7fd9214c-f8b1-483d-a274-54c028a135c4" alt=""><figcaption></figcaption></figure>

## When authentication is not configured

If authentication is not enabled, Mago can still join meetings as a guest participant.

In this scenario:

• the system may enter the meeting lobby\
• the participant appears as a generic device name\
• some meeting features may behave differently depending on the host organization’s policies


# Network requirements

## Third-party Video Conferencing providers

Generally, Mago has the same network requirements as any PC running video conferencing applications like Microsoft Teams, Zoom, Cisco Webex, Google Meet. Specific to Mago, the categories listed as "required" for the video conferencing systems must be open on your firewall. Mago also needs access to Windows Update and Microsoft Intune (if you use Microsoft Intune to manage your devices). For the full list of IPs and URLs required for Mago Room, see:

* **Microsoft Teams** [Office 365 URLs and IP address range](https://docs.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide#skype-for-business-online-and-microsoft-teams)
* **Zoom** <https://support.zoom.us/hc/en-us/articles/201362683-Zoom-network-firewall-or-proxy-server-settings>
* **Google Meet** <https://support.google.com/a/answer/1279090?hl=en>
* **Cisco Webex** <https://help.webex.com/en-us/article/WBX000028782/Network-Requirements-for-Webex-Services>
* **Windows Update** [Configure WSUS](https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/deploy/2-configure-wsus#211-connection-from-the-wsus-server-to-the-internet)
* **Microsoft Intune** [Network Endpoints for Microsoft Intune](https://docs.microsoft.com/en-us/mem/intune/fundamentals/intune-endpoints)

## Mago Meet

Mago Meet uses WebRTC. WebRTC requires a small set of standard signaling and media ports. These ports must be accessible for reliable video conferencing.

Mago Meet works via meet.mago.io or an on-premises hosted domain, and is supported on all modern browsers. It also works with the Mago app for iOS and Android.

## Required ports

<table><thead><tr><th width="109.31640625">Port</th><th width="112.30078125">Type</th><th width="126.7578125">Direction</th><th>Service</th></tr></thead><tbody><tr><td>80</td><td>TCP</td><td>Outbound</td><td>HTTP service for initial access and redirection</td></tr><tr><td>443</td><td>TCP</td><td>Outbound</td><td>HTTPS service for signaling, authentication and coordination</td></tr><tr><td>3478</td><td>UDP</td><td>Both</td><td>STUN server used for NAT traversal and ICE candidate gathering</td></tr><tr><td>5349</td><td>TCP</td><td>Both</td><td>TURN fallback (media relay) for environments where UDP is restricted</td></tr><tr><td>10000</td><td>UDP</td><td>Both</td><td>Encrypted A/V media transport (SRTP via WebRTC)</td></tr></tbody></table>

## Technical notes

**80/TCP and 443/TCP**\
Used for accessing the Mago Link webpage, exchanging signaling messages and establishing secure WebRTC sessions. These ports must be reachable by the sender device.

**3478/UDP (STUN)**\
Allows WebRTC clients to discover their public IP and negotiate NAT traversal paths. This improves connectivity on restrictive enterprise networks.

**5349/TCP (TURN over TLS, fallback media transport)**\
Used only when UDP media is blocked by network firewalls or when NAT traversal is not possible.\
If UDP is unavailable, media traffic automatically switches to 5349/TCP.

**10000/UDP (media transport)**\
Primary port used for sending audio and video over WebRTC using encrypted SRTP.\
This port must be open in both directions between the sender and the Mago device to achieve optimal low-latency performance.

When UDP 10000 is blocked, Mago Meet will fall back to TCP 5349, which works but with reduced performance.


# Presentation


# Wireless Screen Sharing

## Overview

Mago supports multiple screen sharing technologies to provide the best possible experience across all devices, networks and meeting scenarios. Each protocol has different capabilities and network requirements, allowing Mago to work reliably in modern enterprise environments as well as guest networks.

Mago offers the following screen sharing options:

**Mago Link**\
A universal browser based screen sharing method that works on any modern device without installing apps. It uses secure WebRTC communication and works even in networks where traditional casting methods are restricted.

See requirements here: [Mago Link](/mago/requirements/presentation/wireless-screen-sharing/mago-link)

Each protocol has its own strengths and ideal use cases. Mago automatically provides the best available option to ensure reliable and seamless screen sharing in meeting rooms, classrooms and collaborative spaces.

**Miracast (Currently available for Mago on Windows only)**\
A wireless display technology built into Windows and many hardware devices. It connects either through a direct peer to peer link or through the enterprise network using infrastructure mode.

See requirements here: [Miracast](/mago/requirements/presentation/wireless-screen-sharing/miracast)

**AirPlay (Currently available for Mago on Windows only)**\
Apple’s native wireless streaming protocol for macOS, iOS and iPadOS. It uses Bonjour discovery and provides high quality audio and video mirroring.

See requirements here: [AirPlay](/mago/requirements/presentation/wireless-screen-sharing/airplay)

**Google Cast (Currently available for Mago on Windows only)**\
A discovery based screen sharing technology commonly used on Android, ChromeOS and Chrome browser. It uses a combination of multicast and unicast communication to connect to receivers.

See requirements here: [Google Cast](/mago/requirements/presentation/wireless-screen-sharing/google-cast)

## Connectivity Diagram

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FISa1NCqrQGlsNXb66DJw%2FDiapositiva1.jpg?alt=media&amp;token=fb7c0134-ecf1-47d5-bd40-6c2e035f2935" alt=""><figcaption></figcaption></figure>


# Mago Link

For laptop screen sharing (via magolink.com or on-prem hosted domain) or mobile screen sharing (Mago app for iOS / Android).

## Overview

Mago Link uses the Mago Cast protocol to establish a secure WebRTC session between the sender device and the Mago on Windows / on Android device. WebRTC requires a small set of standard signaling and media ports. These ports must be accessible for reliable screen sharing.

Mago Link works via magolink.com or an on-premises hosted domain, and is supported on all modern browsers. It also powers mobile screen sharing through the Mago app for iOS and Android.

## Required ports

<table><thead><tr><th width="109.31640625">Port</th><th width="112.30078125">Type</th><th width="126.7578125">Direction</th><th>Service</th></tr></thead><tbody><tr><td>80</td><td>TCP</td><td>Outbound</td><td>HTTP service for initial access and redirection</td></tr><tr><td>443</td><td>TCP</td><td>Outbound</td><td>HTTPS service for signaling, authentication and coordination</td></tr><tr><td>3478</td><td>UDP</td><td>Both</td><td>STUN server used for NAT traversal and ICE candidate gathering</td></tr><tr><td>7881</td><td>TCP</td><td>Both</td><td>TURN fallback (media relay) for environments where UDP is restricted</td></tr><tr><td>50000 - 60000</td><td>UDP</td><td>Both</td><td>Encrypted A/V media transport (SRTP via WebRTC)</td></tr></tbody></table>

## Technical notes

**80/TCP and 443/TCP**\
Used for accessing the Mago Link webpage, exchanging signaling messages and establishing secure WebRTC sessions. These ports must be reachable by the sender device.

**3478/UDP (STUN)**\
Allows WebRTC clients to discover their public IP and negotiate NAT traversal paths. This improves connectivity on restrictive enterprise networks.

**7881/TCP (TURN over TLS, fallback media transport)**\
Used only when UDP media is blocked by network firewalls or when NAT traversal is not possible.\
If UDP is unavailable, media traffic automatically switches to 5349/TCP.

**50000 - 60000 / UDP (media transport)**\
Primary port used for sending audio and video over WebRTC using encrypted SRTP.\
This port must be open in both directions between the sender and the Mago device to achieve optimal low-latency performance.

When UDP 50000 - 60000 is blocked, Mago Link will fall back to TCP 7881, which works but with reduced performance.

## Key advantages

Mago Link does not require:

* mDNS
* Bonjour
* SSDP
* Multicast
* WiFi Direct
* AP isolation disabled

This makes it ideal for restrictive enterprise networks and guest WiFi environments.


# Miracast

For screen sharing via Windows or Android devices.

{% hint style="warning" %}
This feature is currently available only for **Mago on Windows**.
{% endhint %}

## Overview

Miracast is a wireless display technology that works in two different modes. Mago supports both modes automatically. The mode used depends entirely on how the network is configured and how the user device is connected.

### Miracast over WiFi Direct

This is the original Miracast technology. The connection forms a direct peer to peer link between the user device and Mago. It does not use the corporate WiFi network, does not rely on access points and does not require any VLAN or firewall configuration. Miracast over WiFi Direct is especially useful when the user device is connected on a different network or not connected to any WiFi network at all.

### Miracast over Infrastructure

This mode is designed for enterprise environments. Discovery still uses WiFi, but the actual media traffic flows over the existing network infrastructure (WiFi or Ethernet) instead of a direct peer connection. This mode uses the corporate network, DNS resolution, VLAN routing and specific ports that must be opened on the firewall. Miracast over infrastructure is also known as MS MICE.

### How Windows chooses the Miracast mode

Windows prefers Miracast over infrastructure when the sending device and the Mago device are on the same enterprise network and the required ports and multicast traffic are allowed.\
If these conditions are not met, **Windows automatically falls back to Miracast over WiFi Direct**.\
If both modes fail, Miracast will not connect.

In summary:

* When the network supports MS MICE, Miracast over infrastructure will be used.
* If the corporate network blocks the requirements for MS MICE, Miracast over WiFi Direct will be used automatically.
* If WiFi Direct is disabled by policies or drivers, Miracast may not work in any mode.

## Common requirements for all Miracast modes

{% stepper %}
{% step %}

### Hardware and driver support

Miracast requires compatible hardware on both the sending device and the Mago device.\
This includes the following.

**Graphics adapter**

* Windows Display Driver Model WDDM 1.3 or newer

To check WDDM:

1. Press Windows key and R, type `dxdiag` and press Enter.
2. Let the DirectX Diagnostic Tool finish.
3. Select Save All Information.
4. Open the saved text file and search for "WDDM".

**WiFi adapter**

* Supports Miracast
* Supports WiFi Direct
* Uses a driver with NDIS 6.3 or newer

To check Miracast support:

1. Open a Command Prompt window.
2. Type `netsh wlan show driver` and press Enter.
3. Check the Miracast line in the output.
   {% endstep %}

{% step %}

### WLAN AutoConfig service is running

Miracast requires the WLAN AutoConfig service (wlansvc) to be operating.\
If this service is disabled, WiFi Direct and MS MICE cannot start.

To enable the service:

1. Press Windows key and R, type `services.msc` and press Enter.
2. Find WLAN AutoConfig in the list.
3. Right click, select Properties.
4. Select Start and set the startup type to Automatic.
5. Restart the computer.
   {% endstep %}

{% step %}

### Windows Firewall configuration

Windows Firewall must allow the Windows User Mode Driver Framework Host Process, which handles Miracast communication.

Allow the following:

`C:\Windows\System32\WUDFHost.exe`

Inbound and outbound traffic, TCP and UDP on all ports. If this process is blocked by a local or third party firewall, Miracast pairing or streaming may fail.
{% endstep %}

{% step %}

### Group Policy permissions

Local or domain security policies must allow the creation and use of WiFi Direct. If blocked, Miracast will not work in either mode.

Check the following policy:

Computer Configuration > Windows Settings > Security Settings > Wireless Network (IEEE 802.11) Policies

Within Network Permissions:

1. Allow everyone to create all user profiles
2. Uncheck any setting that disables WiFi Direct groups

{% hint style="info" %}
These policies must allow Windows to create a Microsoft WiFi Direct Virtual Adapter and a DIRECT-XXXXXX temporary network.
{% endhint %}
{% endstep %}

{% step %}

### Drivers are up to date

Miracast is sensitive to driver compatibility. Keep the following updated:

* Chipset drivers
* Graphics adapter drivers
* WiFi adapter drivers

Outdated drivers are one of the most common causes of unstable or failing Miracast sessions.
{% endstep %}
{% endstepper %}

## Miracast over Infrastructure (MS MICE) mode specific requirements

Miracast over infrastructure transports the media stream over the existing network, usually enterprise WiFi or Ethernet. Discovery still uses WiFi but the session is routed through the network.

{% stepper %}
{% step %}

### Network reachability and VLAN routing

The user device and Mago must be reachable across the network.

Requirements:

* Devices in the same enterprise network or routed VLAN
* DNS records for Mago resolvable by the client
* Firewall rules allowing bidirectional traffic
  {% endstep %}

{% step %}

### Required firewall and network ports

The following ports must be allowed in both directions between the client device and Mago:

* UDP 5353 for mDNS discovery
* TCP / UDP 7236 for RTSP Control Port
* TCP 7250 for Miracast Sink
* UDP 32768-65536 for Ephemeral ports for Return traffic

These ports enable session negotiation, discovery and continuous streaming.

| Port          | Type      | Direction | Service                            |
| ------------- | --------- | --------- | ---------------------------------- |
| 5353          | UDP       | Both      | mDNS Discovery                     |
| 7236          | TCP / UDP | Both      | RTSP Control Port                  |
| 7250          | TCP       | Both      | Miracast Sink                      |
| 32768-65536   | UDP       | Both      | Ephemeral ports for Return traffic |
| {% endstep %} |           |           |                                    |

{% step %}

### AP isolation disabled

Since Miracast over infrastructure uses the access point and VLANs, the AP must allow client to client communication. AP isolation or client isolation must be disabled on the SSID used by the sender. If enabled, Miracast over the network cannot function.
{% endstep %}

{% step %}

### Multicast and broadcast traffic allowed

Miracast over infrastructure relies on mDNS discovery. Ensure that the network does not block the following:

* UDP 5353
* Multicast forwarding between VLANs if required
* IGMP snooping causing excessive filtering

If multicast discovery is blocked, MS MICE cannot initialize.
{% endstep %}
{% endstepper %}

## Miracast over WiFi Direct mode specific requirements

Miracast over WiFi Direct creates a dedicated peer to peer wireless link between the user device and Mago. It is not routed through the corporate network.

{% stepper %}
{% step %}

### 2.4 GHz wireless availability

Discovery and pairing always use the 2.4 GHz band on channels 1, 6 or 11. Even if the sending device is connected to 5 GHz or not connected to any WiFi network, pairing begins on 2.4 GHz. Ensure that the 2.4 GHz radio is enabled in the environment. If 2.4 GHz is disabled, Miracast over WiFi Direct cannot initialize.
{% endstep %}

{% step %}

### WiFi Direct Virtual Adapter must be created

During pairing, Windows must create the following:

* Microsoft WiFi Direct Virtual Adapter
* A temporary wireless network named DIRECT-XXXXXX

If these do not appear in Network Connections during an attempted Miracast session, Group Policies or drivers are blocking WiFi Direct.
{% endstep %}
{% endstepper %}

## Quick summary

1. **Confirm Miracast support**\
   • Windows 10 or later\
   • Graphics adapter with WDDM 1.3 or newer\
   • WiFi adapter supporting Miracast, WiFi Direct and NDIS 6.3 or newer\
   Check using `netsh wlan show driver`.
2. **Enable required Windows services**\
   • WLAN AutoConfig service must be running\
   • Group Policies must allow WiFi Direct and creation of DIRECT-XXXXXX networks
3. **Allow Miracast through Windows Firewall**\
   • Allow C:\Windows\System32\WUDFHost.exe for inbound and outbound TCP and UDP
4. **Update drivers**\
   • Update chipset, graphics and WiFi drivers to the latest versions
5. **If using Miracast over Infrastructure (MS MICE)**\
   • User device and Mago must be reachable across VLANs\
   • Required ports open\
   • AP isolation must be disabled\
   • Multicast discovery (mDNS) must be allowed
6. **If using Miracast over WiFi Direct**\
   • 2.4 GHz WiFi must be enabled\
   • AP isolation does not affect this mode\
   • WiFi Direct Virtual Adapter and DIRECT-XXXXXX network must appear during pairing

## Troubleshooting flowchart

{% stepper %}
{% step %}

### Check Miracast hardware support

1. Run `netsh wlan show driver`
2. Check WDDM version with dxdiag

{% hint style="danger" %}
If Miracast not supported → **Stop**. **Update drivers or hardware required.**
{% endhint %}

{% hint style="success" %}
If supported → **Continue**
{% endhint %}
{% endstep %}

{% step %}

### Check WLAN AutoConfig service

1. Ensure **wlansvc** is running

{% hint style="warning" %}
If stopped → **Enable and restart PC**
{% endhint %}

{% hint style="success" %}
If running → **Continue**
{% endhint %}
{% endstep %}

{% step %}

### Attempt Miracast connection

Do DIRECT-XXXXXX network and WiFi Direct Virtual Adapter appear?

{% hint style="warning" %}
No → Group Policy or drivers are blocking WiFi Direct. **Fix GPO and update drivers**.
{% endhint %}

{% hint style="success" %}
Yes → WiFi Direct is functioning → **Continue**
{% endhint %}

If DIRECT network appears, but connection fails.

* Check Windows Firewall for WUDFHost.exe
* Update graphics and WiFi drivers
  {% endstep %}

{% step %}

### Determine connection mode

Is the device on same VLAN and required ports open?

**Yes** → Windows will use Miracast over Infrastructure

**No** → Windows will fall back to WiFi Direct
{% endstep %}

{% step %}

### If using Miracast over Infrastructure

1. Check firewall ports (TCP 7236, 7250, UDP 7236, 5353)
2. Check that AP isolation is disabled
3. Confirm mDNS multicast works across VLAN

{% hint style="warning" %}
If blocked → **Fix network settings**
{% endhint %}

{% hint style="success" %}
If working → **Great! Miracast will work in over Infrastructure mode**
{% endhint %}
{% endstep %}

{% step %}

### If using WiFi Direct

1. Ensure 2.4 GHz radio is enabled
2. Check for RF congestion
3. Test connection again

{% hint style="warning" %}
If issues persist → **Update all chipset, WiFi and graphics drivers**
{% endhint %}

{% hint style="success" %}
If working → **Great! Miracast will work in WiFi Direct mode**
{% endhint %}
{% endstep %}
{% endstepper %}

## Miracast over WiFi Direct vs Miracast over Infrastructure

<table><thead><tr><th width="230.1640625">Aspect</th><th>Miracast over Infrastructure (MS MICE)</th><th>Miracast over WiFi Direct</th></tr></thead><tbody><tr><td><strong>Connection type</strong></td><td>Routed through enterprise network</td><td>Peer to peer WiFi Direct link</td></tr><tr><td><strong>Uses access point</strong></td><td>Yes</td><td>No</td></tr><tr><td><strong>VLANs required</strong></td><td>Yes, if endpoints are on different subnets</td><td>No</td></tr><tr><td><strong>DNS required</strong></td><td>Yes</td><td>No</td></tr><tr><td><strong>Firewall rules required</strong></td><td>Yes, ports 7236, 7250, 5353</td><td>No</td></tr><tr><td><strong>AP isolation impact</strong></td><td>Must be disabled</td><td>No impact</td></tr><tr><td><strong>2.4 GHz requirement</strong></td><td>Not required once infrastructure mode is active</td><td>Required for negotiation (channels 1, 6, 11)</td></tr><tr><td><strong>WiFi Direct Virtual Adapter creation</strong></td><td>Still required for negotiation</td><td>Required</td></tr><tr><td><strong>Discovery mechanism</strong></td><td>mDNS (UDP 5353)</td><td>WiFi Direct beaconing</td></tr><tr><td><strong>Stability in enterprise WiFi</strong></td><td>Better for managed enterprise deployments</td><td>Good for isolated or guest scenarios</td></tr><tr><td><strong>Best use cases</strong></td><td>Corporate networks with proper routing and firewall setup</td><td>Guest devices, unmanaged networks, fallback mode</td></tr><tr><td><strong>Mode priority</strong></td><td>Preferred if infrastructure is correctly configured</td><td>Used when MS MICE is not possible</td></tr></tbody></table>


# AirPlay

For screen sharing via Apple iOS / iPadOS / MacOS devices.

{% hint style="warning" %}
This feature is currently available only for **Mago on Windows**.
{% endhint %}

## Overview

AirPlay relies on Apple Bonjour (mDNS) for discovery and uses several TCP and UDP ports for audio, video, control and event channels. The network must allow discovery and communication between the sending device and the Mago device.

## Requirements

The following requirements must be met for AirPlay to function reliably.

{% stepper %}
{% step %}

### Bonjour (mDNS) must be enabled

AirPlay discovery depends on mDNS, which uses multicast traffic on the following:

* UDP 5353 (mDNS)
* Multicast address 224.0.0.251

For AirPlay to work:

* Multicast traffic must be allowed on the WiFi network
* IGMP Snooping must not block or suppress mDNS packets
* IGMP Querier must be active on VLANs when using snooping
* mDNS must not be rate-limited or filtered by the AP

If mDNS is blocked, Apple devices will not see the Mago device in the AirPlay menu.
{% endstep %}

{% step %}

### AirPlay across multiple VLANs requires mDNS forwarding

In single-VLAN environments, no special configuration is typically needed.

In networks with multiple subnets or VLANs, AirPlay will **not** work unless multicast discovery is forwarded between VLANs. Most enterprise networks block multicast between VLANs by default.

To enable AirPlay across VLANs, your network must support one of the following:

* mDNS reflector / mDNS gateway
* Bonjour gateway (Cisco, Aruba, Meraki, UniFi, Extreme, etc.)
* Avahi reflector (Linux-based networks)
* Multicast forwarding between specific VLANs
* AirGroup-style service registration

This configuration is vendor-specific and must be performed on your switches or wireless controllers.

If your network does not forward mDNS between VLANs, AirPlay will only work when client devices and Mago are on the same VLAN.
{% endstep %}

{% step %}

### Required AirPlay ports must be open

<table><thead><tr><th width="102.96875">Port</th><th width="108.40234375">Type</th><th width="119.5234375">Direction</th><th>Service</th></tr></thead><tbody><tr><td>554</td><td>TCP/UDP</td><td>Both</td><td>Real Time Streaming Protocol</td></tr><tr><td>3689</td><td>TCP</td><td>Both</td><td>Digital Audio Access Protocol</td></tr><tr><td>5350</td><td>UDP</td><td>Both</td><td>NAT Port Mapping Announcements</td></tr><tr><td>5351</td><td>UDP</td><td>Both</td><td>NAT Port Mapping Announcements</td></tr><tr><td>5353</td><td>UDP</td><td>Both</td><td>mDNS Discovery</td></tr><tr><td>7000*</td><td>TCP</td><td>Both</td><td>AirPlay Server Port</td></tr><tr><td>7100*</td><td>TCP</td><td>Both</td><td>AirPlay Data Port</td></tr><tr><td>2001*</td><td>UDP</td><td>Both</td><td>AirPlay Timing Port</td></tr><tr><td>29053*</td><td>TCP</td><td>Both</td><td>AirPlay Events</td></tr><tr><td>61875*</td><td>UDP</td><td>Both</td><td>AirPlay Audio Data Port</td></tr></tbody></table>

(\*) Dynamic ports automatically selected by AirServer\
AirServer announces these ports via Bonjour/mDNS.

Firewall rules must not block these ports, or AirPlay will fail after discovery or result in black screen / audio-only mirroring.
{% endstep %}

{% step %}

### Requires Bonjour service types

AirPlay relies on Bonjour (mDNS) to advertise receiver capabilities.\
The following Bonjour service types must be visible to the client device:

* \_airplay.\_tcp
* \_raop.\_tcp
* \_airserver.\_tcp

If your network uses multiple VLANs, your mDNS gateway or Bonjour reflector must forward these service types between VLANs.\
If any of these are filtered or missing, AirPlay devices may not discover the Mago device or may fail during session setup.
{% endstep %}

{% step %}

### Multicast configuration on WiFi access points

Most enterprise WiFi systems include multicast control features that can unintentionally break AirPlay. Ensure the following:

* Multicast is allowed on the SSID used by client devices
* Broadcast/multicast filtering is disabled or relaxed
* Proxy ARP does not interfere with mDNS packets
* DTIM intervals are not excessively high
* Band steering does not block multicast on 2.4 GHz (if used)

Apple recommends enabling multicast on both bands, although 5 GHz is preferred for performance.
{% endstep %}

{% step %}

### AP Isolation must be disabled

AirPlay requires direct communication between the sender device and the Mago device. If AP isolation (client isolation) is enabled, devices cannot see each other, even if mDNS is working. Make sure AP isolation is disabled on the SSID used by client devices.
{% endstep %}

{% step %}

### Device and OS requirements

Sending device must be:

* iPhone or iPad with iOS 11 or later
* macOS 10.11 or later
* Windows devices using iTunes or compatible AirPlay apps

The receiving device (Mago) must:

* Be on the same VLAN as the AirPlay clients unless mDNS forwarding is configured
  {% endstep %}

{% step %}

### Network stability and performance considerations

AirPlay streaming uses a mixture of TCP and UDP channels. For best results:

* Ensure strong signal strength on the WiFi network
* Ensure low latency and minimal packet loss
* Avoid congested 2.4 GHz networks when possible
* Prefer 5 GHz or WiFi 6 for high-quality mirroring
  {% endstep %}
  {% endstepper %}


# Google Cast

For screen sharing via Android, ChromeOS devices, Chrome web browsers.

{% hint style="warning" %}
This feature is currently available only for **Mago on Windows**.
{% endhint %}

## Overview

Google Cast uses a combination of mDNS, SSDP, and TCP/UDP streams to discover and communicate with receiver devices. The following network requirements must be met for reliable mirroring from Android, ChromeOS, and Chrome browser clients.

## Requirements

{% stepper %}
{% step %}

### mDNS and SSDP discovery must be enabled

Google Cast discovery relies on two protocols:

**mDNS**

* UDP 5353
* Multicast address 224.0.0.251
* Bonjour service: \_googlecast.\_tcp

**SSDP**

* UDP 190
* Multicast address 239.255.255.250
* ST/URN tags for Google Cast receivers

Requirements

* Multicast must be allowed on the WiFi network
* IGMP Snooping must not block SSDP or mDNS
* IGMP Querier required if snooping is enabled
* mDNS and SSDP must not be filtered, rate-limited, or converted to unicast in incompatible ways
* AP isolation must be disabled

If mDNS or SSDP is blocked, the sender will not see the Mago device in the Cast menu.
{% endstep %}

{% step %}

### Google Cast across VLANs requires multicast forwarding

In single-VLAN networks Google Cast works without special configuration.

In multi-VLAN networks, Google Cast will not work unless multicast discovery is forwarded between VLANs.

You must enable one of the following (vendor-specific):

* mDNS gateway / Bonjour reflector
* SSDP multicast forwarding between VLANs
* Layer 3 multicast routing between specific VLANs
* Vendor “cast/airgroup multicast proxy” features (Cisco, Aruba, UniFi, Meraki, etc.)

If mDNS and SSDP packets do not cross VLAN boundaries, Google Cast will only work when clients and Mago are on the same VLAN.
{% endstep %}

{% step %}

### Required Google Cast ports must be open

These are the ports used by Google Cast:

<table><thead><tr><th width="134.9921875">Port</th><th width="108.35546875">Type</th><th width="107.71484375">Direction</th><th>Service</th></tr></thead><tbody><tr><td>8008-8019</td><td>TCP</td><td>Both</td><td>GoogleCast Listener Ports</td></tr><tr><td>1900</td><td>UDP</td><td>Both</td><td>SSDP Discovery</td></tr><tr><td>5353</td><td>UDP</td><td>Both</td><td>mDNS Discovery</td></tr><tr><td>32768-61000</td><td>TCP/UDP</td><td>Both</td><td>Ephemeral ports for client / server traffic</td></tr></tbody></table>

Requirements

* Both sender and Mago must be able to communicate over the ports above
* Firewall rules must allow inbound and outbound traffic
* NAT must not rewrite multicast packets (breaks SSDP/mDNS)

If ports 8008–8019 are blocked, Cast may appear but refuse to connect.\
If ephemeral ports are blocked, connection may start but fail mid-stream.
{% endstep %}

{% step %}

### WiFi network configuration for Google Cast

Google Cast requires stable multicast behavior on the access point.

Check that:

* Multicast is enabled on the SSID
* Broadcast/multicast filtering is disabled or set to “unrestricted”
* Proxy ARP does not block or transform mDNS/SSDP packets
* DTIM settings are reasonable (DTIM 1–3 recommended)
* 5 GHz is available for high-bandwidth casting
* Client load on AP is not excessive

Chromecast and Android devices do not retry failed mDNS/SSDP packets aggressively, so multicast reliability is critical.
{% endstep %}

{% step %}

### AP isolation must be disabled

Access point isolation (client isolation) prevents devices on the same SSID from communicating. Because Google Cast requires peer-to-peer communication:

* AP isolation must be disabled on the SSID used by client devices
* Wireless client privacy modes on the controller must be disabled
* Isolation in guest networks must be removed for the SSID used for casting

If isolation is enabled, devices may discover Mago (depending on broadcast bridging), but the connection will always fail.
{% endstep %}

{% step %}

### Device and OS requirements

Google Cast requires compatible senders:

* Android 4.4+
* ChromeOS devices
* Chrome browser with Cast extension or built-in Cast support
* Some Windows/macOS apps support casting via Chrome browser

Receiver (Mago):

* Must be connected via Ethernet or a high-quality WiFi connection
* Must be reachable through firewall and VLAN configuration
  {% endstep %}

{% step %}

### Best practices for network reliability

To ensure smooth casting:

* Prefer Ethernet for the Mago device
* Use 5 GHz WiFi for sending devices
* Avoid DFS channels if Android devices have limited support
* Keep packet loss below 1 percent for stable video
* Minimize interference and channel congestion
* Ensure roaming between APs is not too aggressive
  {% endstep %}

{% step %}

### Bonjour service types required

Google Cast relies on mDNS to advertise available receivers. AirServer broadcasts the following Bonjour service types:

* \_googlecast.\_tcp
* \_display.\_tcp
* \_airserver.\_tcp

These service types must be visible to the client device.\
If your network uses multiple VLANs, your mDNS gateway or Bonjour reflector must allow these service types to be forwarded.

If they are filtered or missing, clients may not discover the Mago device or may fail to connect during session negotiation.
{% endstep %}
{% endstepper %}


# Wired screen sharing (HDMI)

For screen sharing via laptops.

{% hint style="warning" %}
This feature is currently available only for **Mago on Windows**.
{% endhint %}

Mago supports screen sharing through an HDMI cable. An HDMI input port on the room device is required to enable HDMI ingest. For the list of devices with built-in HDMI input and supported capture cards and third-party BYOD or BYOM systems, refer to the chapter titled [(Optional) HDMI capture cards and Third-party BYOD / BYOM systems](/mago/certified-devices/windows-devices/optional-hdmi-capture-cards-and-third-party-byod-byom-systems) and the Mago configuration section under Settings > Presentation.


# Whiteboard

Mago Whiteboard is designed to deliver a natural and responsive writing experience. For the best performance, an interactive display is required so that users can write, draw and interact directly on the screen with a pen or with touch input.

Mago supports all common interaction types provided by certified interactive displays, including pen input, finger touch, hand gestures and punch interactions. These capabilities are available on all devices listed in the “Certified Room Devices” chapter.

For optimal smoothness, we recommend setting the display refresh rate to **60 Hz or higher** when available. A higher refresh rate reduces latency and improves the natural feel of ink strokes during fast writing.

Depending on the display model, the automatic detection mode for pen input and hand or finger touch may need to be configured on the device. Mago fully supports the advanced pen features offered by the interactive displays included in the certified list, such as pressure sensitivity, palm rejection and rear-pen erasing (when available on the hardware). See list here [Broken mention](broken://pages/RBSMgKdWFsCdN0hpolFG).


# Wireless touch controllers

## Apple devices

{% hint style="warning" %}
Apple iPad, minimum required iPadOS version: 13.0
{% endhint %}

**Minimum iPad model required**\
Any model that supports iPadOS 13.0

{% embed url="<https://support.apple.com/guide/ipad/ipad213a25b2/13.0/ipados/13.0>" %}

**Link Mago Controller App for iOS**

{% embed url="<https://apps.apple.com/app/mago-controller/id1630363629>" %}

## Android devices (tablets)

{% hint style="warning" %}
Minimum Android version required: 10.0
{% endhint %}

**Minimum tablet screen resolution**\
1024 x 600 mdpi

**Mago Controller App for Android**

{% embed url="<https://play.google.com/store/apps/details?id=com.remago.valarea.wtc>" %}


# Requirements

The Mago mobile app allows users to connect to Mago Room devices, start meetings, launch personal content, access cloud drives, control the room remotely and interact with the display. The app is available for both iOS and Android.

## Apple devices

The Mago mobile app is compatible with the following Apple operating systems:

* iOS: minimum version 13.0
* macOS with Apple Silicon (M1 or newer): minimum version 13.0 (Ventura)

Download link (Apple App Store):

{% embed url="<https://apps.apple.com/app/mago-workspace/id1408732971>" %}

## Android devices

The Mago mobile app is compatible with Android devices running:

* Android OS: minimum version 8.0

Download link (Google Play Store):<br>

{% embed url="<https://play.google.com/store/apps/details?id=com.remago.workspace>" %}


# Authentication

To use the Mago mobile app, users must authenticate using one of the following methods:

* Third-party OAuth (Microsoft 365, Google, Apple)
* Email and password

For more information, refer to [Third-party providers](/mago/requirements/third-party-providers)


# Proximity connection

## Overview

The Mago mobile app can connect to a Mago display to enable the following features:

* Start a meeting from My Calendar
* Launch personal Mago whiteboards
* Present files from cloud drives (OneDrive, Google Drive)
* Open personal apps and web links
* Remote meeting control (volume, microphone, camera)
* Remote control using trackpad, mouse or keyboard mode

The connection can be established by:

* Scanning the QR code displayed on the Mago Room screen
* Entering the six-digit alphanumeric room code

## Bluetooth requirements

To authenticate user proximity securely, Bluetooth Low Energy (BLE) must be enabled on both the mobile device and the Mago Room device.

* Minimum BLE version required: 4.0
* Bluetooth is used only for proximity verification
* No data is transferred via Bluetooth
* Devices do not need to be paired

All operational data exchanged between the mobile app and the Mago display is transmitted securely through Mago’s end-to-end encrypted HTTPS signaling service.

## Automatic disconnection

When the mobile device moves beyond the allowed proximity range, the app stops receiving packets and automatically disconnects cloud drives, personal calendars and session-bound links from the Mago display.


# Mago app for Android - Data safety notice

Know more about Data Safety on the Mago app for Android

## Data collection and security

### Data types

The Mago app for Android (Google Play Store link: <https://play.google.com/store/apps/details?id=com.remago.workspace>) may collect the following user data types:

* Personal info
  * Name
  * Email address
  * User ID
  * Date of birth
  * Profile picture
  * Address
* Files and docs
  * Photos and videos
  * Audio files
* App Activity
  * App interactions
* App info and performance
  * Crash logs
* Device ID

#### Data purposes

The user data is collected for the following purposes:

* App functionality
  * User authentication
  * User profile name visibility
  * App features such as whiteboard, room connection, calendar event launch, file presentation
* Analytics
  * Monitor app health
  * Diagnose and fix bugs or crashes

## How to manage or delete your user data

### Update or delete your profile information

1. Open the Mago app and sign in to your account.
2. Go to the "Account" section, by tapping the user icon.
3. Update or delete your data such as Nickname, Name, Surname, Profile picture, Address, Date of Birth.
4. When you update or delete any of your user profile data, the old data is deleted immediately.

### Update or delete your whiteboard contents

1. Open the Mago app and sign in to your account.
2. Go to Whiteboards, choose an item from the list.
   * To update: Enter the whiteboard and edit any whiteboard item or object.
   * To delete: Tap the three dots icon and choose "Delete". Tap to confirm.
3. When you update or delete any of your whiteboard data, the old data is deleted immediately.

### Delete your account and associated data completely

### Update or delete your profile information

{% hint style="warning" %}
Once you delete your account and associated data, all data is deleted immediately. No retention period is applied to any of your data.
{% endhint %}

1. Open the Mago app and sign in to your account.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FKNAhYyeJfmyhJrv6PotT%2FScreenshot_2023-12-14-14-42-21-76_cb23e5e7d770c586fbcb33fe48b26116.jpg?alt=media&amp;token=404cd3f2-ea66-4316-a5dc-a26047a015d1" alt="" width="375"><figcaption></figcaption></figure>

2. Go to the "Account" section, by tapping the user icon.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FLnWFOeqH2gDFqVMSWrp3%2FScreenshot_2023-12-14-14-39-04-55_cb23e5e7d770c586fbcb33fe48b26116.jpg?alt=media&amp;token=1374b7bc-3b4c-47a5-ba59-a8285b537975" alt="" width="375"><figcaption></figcaption></figure>

3. Scroll down and tap "Delete account". Tap "OK" to confirm.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FSBxfhi1V9VsppQiMqUyx%2FScreenshot_2023-12-14-14-39-12-12_cb23e5e7d770c586fbcb33fe48b26116.jpg?alt=media&amp;token=06c43eab-09be-4d2a-b5b9-9772b66a4294" alt="" width="375"><figcaption></figcaption></figure>

## More information

Additionally, you can contact us to ask via email at support \[at] mago.io for one of the following:

* Receive a list of the data we collected, associated with your user account
* Edit any of the data associated with your user account
* Delete any of the data associated with your user account
* Completely delete your user and all the data associated with your user account

We will answer your requests within 72 hours and process them within 7 days.


# About Mago Stage

This section introduces Mago Stage and explains the terminology used throughout the documentation.

* **Introduction** explains what Mago Stage is and how it is used.
* **Key terms** defines the product concepts, roles, and features referenced in the guides.


# Introduction

Mago Stage is a presentation and content-control platform for displaying and managing content across one or more screens.

A Mago Stage deployment uses two device roles:

* A **controller** is used to create and manage Stages, add content, connect to receivers, and control presentations.
* A **receiver** displays the content sent from a controller.

Depending on the active license and network configuration, a receiver can run on the same Windows machine as the Mago Stage server, elsewhere on a private network, or at another accessible location.

#### What you can do with Mago Stage

Mago Stage can be used to:

* Create reusable Stages with predefined content and layouts
* Present documents, images, videos, websites, notes, and supported 3D models
* Add content from local storage, Microsoft 365, or Google Drive
* Arrange content across predefined or custom layouts
* Connect to individual receivers or receiver groups
* Control supported content from the controller
* Share a screen using Mago Share
* Use Player or Showroom presentation modes
* Apply branding, signage, and display policies through the Administration Portal
* Manage displays, Remote Agents, licenses, users, tags, and assignments

Available features depend on the controller platform, receiver platform, active license, connected services, and organization configuration.

#### Mago Cloud and on-premises deployments

Mago Stage can connect to:

* **Mago Cloud**, operated and hosted by Mago
* A customer-managed **on-premises Mago Stage environment**

Controllers and receivers must use the same Mago Stage environment. Accounts, Stages, receivers, licenses, and configuration are not transferred automatically between environments.

#### Where to begin

Before installing Mago Stage:

1. Review **Supported platforms**.
2. Confirm the applicable **Controller requirements** or **Receiver requirements**.
3. Review the **Network requirements**.
4. Continue to **Before you begin** in the Mago Stage Client Apps section.

Administrators should also review the **Administration Portal** section before activating receivers, assigning licenses, or configuring organization policies.

{% embed url="<https://www.youtube.com/watch?v=QFSK1aOVAM8>" %}


# Key terms

This page explains the terms used throughout the Mago Stage documentation.

### Activation code

A code shown by an unactivated receiver. An administrator uses this code in the Administration Portal to register the receiver with an organization and assign the required license.

An activation code is not the same as a connection code.

### Connected account

A Microsoft 365 or Google account linked to Mago Stage.

Connected accounts allow supported cloud files, folders, profile information, and calendar features to be used in Mago Stage. Available features depend on the account provider and the organization’s policies.

### Connection code

A code shown by an activated receiver that allows a controller to connect to it.

Enter the connection code on the controller when the receiver is not discovered automatically or when QR-code connection is not being used.

A connection code does not activate or license the receiver.

### Content

Any item added to a Stage for display or presentation.

Content can include:

* Images
* Videos
* PDF documents
* Microsoft Office documents
* Websites
* YouTube videos
* Cloud files and folders
* Cameras
* Screen-sharing sessions
* Other supported media or integrations

### Content drawer

The area of the controller used to find, add, and manage content for the current Stage.

The available sources depend on the platform, connected accounts, organization configuration, and assigned license.

### Controller

The phone, tablet, computer, or browser used to create and manage a Stage, add content, connect displays, and control a presentation.

See **Controller Requirements** for supported platforms and device guidance.

### Display

A screen or display endpoint managed through Mago Stage.

In the Administration Portal, a display record represents an activated receiver and its associated configuration, license assignment, status, and policies.

### Mago Remote Agent

A device running the Mago Remote Agent software.

An authorized administrator or user can access and control the device remotely through the Administration Portal and Remote Controller.

Mago Remote Agents are managed separately from Stage receivers.

### Organization

The Mago Stage environment containing the organization’s users, displays, licenses, policies, tags, assignments, and digital-signage content.

A user may have access to more than one organization.

### Player mode

A playback-focused view used to present the current Stage with fewer editing controls visible.

Use Player mode when the Stage is ready and the presenter wants to focus on displaying and controlling content.

### Present

A quick presentation workflow for sharing a file, photograph, screen, or supported call without first building a complete reusable Stage.

Present sessions are intended for immediate or temporary presentation needs.

### Receiver

The application or device that receives commands and displays content sent from a controller.

A receiver must be activated, licensed, online, and reachable through the configured Mago Stage environment before it can be used.

See **Receiver Requirements** for supported platforms and device guidance.

### Receiver group

A managed collection of receivers that can be selected together.

Receiver groups make it possible to send or control content across several displays. A receiver group can contain up to 9 receivers.

The available number of receivers and groups can also depend on the organization’s license.

### Showroom mode

A simplified presentation view intended for guided demonstrations, showrooms, and similar customer-facing experiences.

Showroom mode reduces the editing interface and emphasizes the content being presented.

### Stage

A saved workspace containing a layout and its content.

A Stage can be reopened and reused. Changes to its layout or content can be saved for future sessions.

### Stage created from a cloud folder

A Stage whose content is based on a selected Microsoft or Google cloud folder.

The files in the connected folder become the Stage’s content. Update the source folder and refresh the Stage when the folder contents change.

Some editing behavior differs from a Stage created manually in the application.

### WebRTC service

The real-time communication service used for supported screen-sharing, audio, and video features.

The WebRTC service may be hosted by Mago or deployed within the customer’s on-premises environment.


# Device requirements

This section describes the platforms and device specifications supported by Mago Stage.

Review these requirements before selecting, purchasing, or configuring devices.

* **Supported platforms** lists the supported operating systems, browsers, and available controller and receiver roles.
* **Controller requirements** provides hardware and permission guidance for controller devices.
* **Receiver requirements** provides hardware and performance guidance for single-display, multi-display, Android, and browser receivers.


# Supported platforms

Mago Stage is available on several operating systems. Available features depend on the device, operating system, and whether the device is acting as a controller or receiver.

#### Native applications

| **Platform** | **Minimum supported version**           | **Controller** | **Receiver** |
| ------------ | --------------------------------------- | -------------- | ------------ |
| **Windows**  | Windows 11, version 24H2                | Yes            | Yes          |
| **Android**  | Android 12                              | Yes            | Yes          |
| **iPhone**   | iOS 16                                  | Yes            | No           |
| **iPad**     | iPadOS 16                               | Yes            | No           |
| **macOS**    | macOS 12 on Apple silicon (M1 or later) | No             | Yes          |

{% hint style="info" %}
Some features require compatible hardware, operating-system permissions, an active license, or additional organization configuration.
{% endhint %}

{% hint style="info" %}
The platform table describes application availability. License editions can apply additional restrictions. The Basic edition is available on Windows only.
{% endhint %}

#### Browser access

Browser-based Mago Stage features require a current, supported browser.

| Browser             | Controller access | Receiver access |
| ------------------- | ----------------- | --------------- |
| **Google Chrome**   | Yes               | Yes             |
| **Microsoft Edge**  | Yes               | Yes             |
| **Mozilla Firefox** | Yes               | Yes             |
| **Apple Safari**    | Yes               | No              |

Use the current or previous major version of a supported browser.

Browser functionality can be affected by:

* Camera, microphone, and screen-sharing permissions
* Pop-up and redirect restrictions
* Third-party cookie restrictions
* Organization security policies
* Firewall and proxy configuration
* Hardware acceleration settings

#### Choosing a platform

Use a native application where possible for the most complete experience.

The appropriate platform depends on the intended role:

* Use Windows or Android for devices that must operate as either a controller or receiver.
* Use an iPhone or iPad as a mobile controller.
* Use a supported Apple silicon Mac as a receiver.
* Use browser access when installation is not practical or when a supported web workflow is required.

For device-specific hardware guidance, see **Controller requirements** and **Receiver requirements**.


# Controller requirements

Use these requirements when selecting a device that will control Mago Stage. Controller devices are used to create and manage Stages, add content, connect displays, and control presentations.

More demanding workflows, including high-resolution content, screen sharing, video conferencing, and several connected displays, may require more powerful hardware.

The specifications below are deployment baselines. They do not guarantee performance for every combination of content and connected displays.

### Windows controllers

| Component    | Minimum baseline                                               | Recommended                                      |
| ------------ | -------------------------------------------------------------- | ------------------------------------------------ |
| Processor    | 12th-generation Intel Core i5 or equivalent                    | Intel Core Ultra 5 or equivalent                 |
| Memory       | 16 GB RAM                                                      | 32 GB RAM                                        |
| Free storage | 64 GB                                                          | 128 GB                                           |
| Graphics     | Hardware-accelerated graphics and video decoding               | Hardware-accelerated graphics and video decoding |
| Display      | 1920 × 1080                                                    | 1920 × 1080 or higher                            |
| Software     | Current graphics, network, and Microsoft Edge WebView2 updates | Current vendor and operating-system updates      |

The controller must be able to reach the required Mago Stage cloud or on-premises services.

### Android controllers

Recommended baseline:

* Android 12 or later
* Quad-core processor or better
* 8 GB RAM
* Sufficient free storage for locally stored and cached content
* Rear camera with autofocus for QR codes, photographs, and document scanning
* 1920 × 1080 display resolution or higher
* Reliable Wi-Fi connection

### iPhone and iPad controllers

Recommended baseline:

* iOS or iPadOS 16 or later
* iPad 10th generation or newer for full-size tablet use
* Sufficient free storage for locally stored and cached content
* Rear camera with autofocus for QR codes, photographs, and document scanning
* Reliable Wi-Fi connection

Smaller phone-sized controllers support selected workflows. A phone controller can connect to a maximum of two displays during a session.

### Browser controllers

A browser controller requires:

* A supported desktop browser
* JavaScript and cookies enabled
* Permission to open required pop-up windows
* Access to the required Mago Stage services
* Screen-sharing permission when sharing the controller’s screen
* Camera and microphone permission when using conferencing features

Screen capture is not supported from mobile browsers or Safari on iPhone and iPad.

### General controller requirements

All controllers require:

* A supported operating system or browser
* Access to the required cloud or on-premises endpoints
* Correct system date, time, and time zone
* Current operating-system, graphics, browser, and network updates
* A stable network connection
* Local file access when uploading content

Depending on the features being used, controllers may also require:

* Camera permission for scanning QR codes
* Camera access for photographs and document scanning
* Microphone permission for conferencing
* Screen-recording permission for screen sharing

### Performance considerations

Controller performance may be affected by:

* The number of connected displays
* The complexity of the Stage layout
* High-resolution images and video
* Large locally stored or cached files
* Interactive websites
* 3D models
* Screen sharing
* Video conferencing

Test the intended device with representative content before a large deployment.


# Receiver requirements

Use these requirements when selecting a device that will display content received from a Mago Stage controller.

Receiver requirements depend on the number of connected displays, their resolutions, and the type of content being shown.

The specifications below are deployment baselines. They do not guarantee performance for every layout or workload. For extreme resolutions and custom requirements, consult your authorized Mago Partner before deployment.

#### Single-display receivers

Use this baseline for a Windows or macOS receiver connected to one display.

| Component      | Minimum baseline                                          | Recommended                                      |
| -------------- | --------------------------------------------------------- | ------------------------------------------------ |
| Processor      | 12th-generation Intel Core i5 or equivalent               | Intel Core Ultra 5 or equivalent                 |
| Memory         | 16 GB RAM                                                 | 32 GB RAM                                        |
| Free storage   | 64 GB                                                     | 128 GB                                           |
| Graphics       | Hardware-accelerated graphics and video decoding          | Hardware-accelerated graphics and video decoding |
| Display output | One output at 1920 × 1080                                 | One output at 1920 × 1080 or higher              |
| Software       | Current graphics, network, and browser or WebView updates | Current vendor and operating-system updates      |

{% hint style="info" %}
The Intel processor baseline applies to Windows receivers. A macOS receiver requires Apple silicon with an M1 processor or later.
{% endhint %}

#### Multi-display receivers

Use this baseline when one Windows receiver controls up to three directly connected displays. Multi-display operation is subject to the active license. Basic supports up to three wired displays from one receiver. Pro, Ultra, and Cloud support one wired display per receiver.

| Component       | Minimum baseline                                                             | Recommended                                                                                      |
| --------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| Processor       | 12th-generation Intel Core i7 or equivalent                                  | Intel Core Ultra 7 or equivalent                                                                 |
| Memory          | 32 GB RAM                                                                    | 32 GB RAM or more                                                                                |
| Free storage    | 64 GB                                                                        | 128 GB                                                                                           |
| Graphics        | Hardware-accelerated graphics with enough supported outputs for all displays | Dedicated or high-performance integrated graphics with enough supported outputs for all displays |
| Display outputs | Up to three outputs at 1920 × 1080                                           | Outputs and resolutions validated for the intended layout                                        |
| Software        | Current graphics, network, and browser or WebView updates                    | Current vendor and operating-system updates                                                      |

Confirm that the graphics hardware supports the required number of simultaneous displays and their intended resolutions. The presence of multiple physical connectors does not always mean they can all operate simultaneously.

{% hint style="info" %}
With Basic, the server and receiver run on the same Windows machine. Select hardware that can support the server workload, receiver workload, connected displays, and intended content simultaneously.
{% endhint %}

#### Android receivers

An Android receiver requires:

* Android 12 or later
* Hardware-accelerated video decoding
* Sufficient memory and storage for the intended content
* A display resolution suitable for the installation
* A reliable network connection
* Permission for Mago Stage to remain active during scheduled use

Test the intended Android device with representative content before deployment. Android device performance can vary significantly between manufacturers and models.

#### Browser receivers

A browser receiver requires:

* A supported desktop browser
* JavaScript and cookies enabled
* Access to the required Mago Stage services
* Permission to use full-screen mode
* A device configured to prevent sleep during scheduled use

Browser receivers are supported in Chrome, Edge, and Firefox.

#### General receiver requirements

All receivers require:

* A supported operating system or browser
* Continuous access to the configured Mago Stage service
* Correct system date, time, and time zone
* Current operating-system, graphics, browser, and network updates
* A stable wired or managed Wi-Fi connection
* A supported display output
* Permission to prevent sleep during scheduled use
* Audio output when playing media or using conferencing features

A wired network connection is recommended for fixed receivers, high-resolution video, conferencing, and multi-display installations.

#### Performance considerations

Receiver performance may be affected by:

* The number and resolution of connected displays
* 4K or high-frame-rate video
* Several videos playing simultaneously
* Complex multi-zone layouts
* Interactive or embedded websites
* 3D models
* Screen sharing
* Video conferencing
* Large locally cached content libraries

Test the intended receiver with representative content and the final display configuration before deployment. A successful installation confirms compatibility but does not validate performance under the expected workload.


# Network Requirements

This section describes the connectivity required for Mago Cloud and on-premises Mago Stage deployments.

Network and security teams should review the applicable pages before installation or deployment.

* **Network overview** explains the general connectivity, network-quality, segmentation, and time-synchronization requirements.
* **Cloud connectivity** lists the Mago-hosted services required by Mago Cloud deployments.
* **Third-party service endpoints** lists optional external services used by Microsoft, Google, Apple, YouTube, email, and embedded web content.
* **On-premises firewall ports** lists the inbound ports required by on-premises services.
* **On-premises DNS and service addresses** explains hostname planning, DNS records, service URLs, and application origins.
* **On-premises certificates and proxies** explains certificate files, trust, renewal, reverse proxies, WebSockets, and TLS inspection.


# Network overview

Mago Stage controllers, receivers, and administration services communicate over standard IP networks. Every device must be able to reach the same configured Mago Stage environment.

Controllers and receivers do not need to be on the same local network or broadcast domain. Their connection is coordinated through the Mago Stage service, subject to the organization’s license and network policies.

### Core network requirements

A Mago Stage deployment requires:

* Reliable IP connectivity
* DNS resolution for all configured service names
* HTTPS access to the Mago Stage API and web services
* Secure WebSocket connections for live control and device status
* Accurate system time on controllers, receivers, and servers
* Access to any external services enabled by the organization

Firewalls and proxies must permit HTTPS connections, WebSocket upgrades, and long-lived WebSocket sessions.

### Controller connectivity

Controllers must be able to reach:

* The configured Mago Stage API
* The device signaling service
* Content and file-storage services used by the organization
* Authentication services used for sign-in
* Conferencing or screen-sharing services when those features are enabled

A controller may connect to receivers on another subnet or site as long as both devices can reach the same Mago Stage environment.

### Receiver connectivity

Receivers require continuous access to:

* The configured Mago Stage API
* The device signaling service
* Content sources used by active Stages
* Conferencing and screen-sharing services when enabled
* Application update services when automatic updates are used

A temporary network interruption may delay commands, content updates, and device-status reporting.

Use wired Ethernet for fixed receivers whenever possible, especially for high-resolution video, conferencing, screen sharing, and multi-display installations.

### Administration connectivity

Administrators must be able to reach:

* The Mago Stage administration portal
* The configured Mago Stage API
* Licensing services
* Application download and update services
* Mago Remote services when remote management is enabled

Additional access may be required for identity providers, cloud storage, email services, and other configured integrations.

### Network segmentation

Receivers can be placed in a managed AV or IoT network segment.

When using network segmentation:

* Allow controllers and receivers to reach the same Mago Stage environment.
* Allow administrators to reach the administration portal and API.
* Permit WebSocket upgrades and long-lived connections.
* Permit only the required communication paths between network segments.
* Use DNS names instead of fixed IP addresses for application services.
* Give on-premises servers a static IP address or DHCP reservation.
* Do not expose application, database, or container-management ports directly to the public internet.

Real-time media services should be excluded from TLS inspection unless the configuration has been tested and confirmed to work.

### Recommended network quality

These values are planning targets rather than application-enforced limits.

| Metric                              | Recommended target                                                                    |
| ----------------------------------- | ------------------------------------------------------------------------------------- |
| Controller-to-service latency       | Below 100 ms; below 50 ms preferred at a local site                                   |
| Packet loss                         | Below 1%                                                                              |
| Jitter for calls and screen sharing | Below 30 ms                                                                           |
| Basic control traffic               | Approximately 2 Mbps available per active device                                      |
| 1080p screen sharing or video       | Approximately 10–15 Mbps per simultaneous stream                                      |
| 4K or multiple simultaneous streams | Validate at the deployment site; plan for at least 25 Mbps per high-resolution stream |

Content downloads, cloud-file synchronization, and application updates can create short bandwidth peaks. Available capacity should account for simultaneous users and displays, not only the bandwidth required by one device.

### Wi-Fi guidance

Wi-Fi can be used for mobile controllers and receivers where cabling is not practical.

For reliable operation:

* Use managed business-grade Wi-Fi.
* Provide strong signal coverage at every device location.
* Avoid congested channels.
* Keep real-time presentation traffic separate from guest traffic where possible.
* Confirm that client-isolation rules do not block required services.
* Test screen sharing and video playback under normal site load.

Use wired Ethernet for permanent receivers and other business-critical installations.

### Time synchronization

Controllers, receivers, and servers must maintain accurate date and time settings.

Incorrect system time can cause:

* Certificate validation failures
* Authentication or SSO failures
* Expired or invalid access tokens
* Incorrect audit timestamps
* Problems establishing secure connections

Use automatic operating-system time synchronization or an organization-managed time service.


# Cloud connectivity

Mago Stage controllers, receivers, and administrator browsers require access to Mago-hosted services when using the Mago Cloud deployment.

Allow DNS resolution and outbound connections to the endpoints required by the organization’s enabled features.

### Connection requirements

Mago Cloud uses:

* HTTPS over TCP 443
* Secure WebSockets over TCP 443
* Real-time media transport for screen sharing and conferencing
* DNS through the organization’s configured DNS service
* Time synchronization through the organization’s configured time service

Firewalls, proxies, and security gateways must permit:

* TLS 1.2 or later
* WebSocket connection upgrades
* Long-lived WebSocket connections
* File uploads and downloads
* HTTP redirects between approved Mago services
* Real-time media traffic when screen sharing or conferencing is enabled

### Mago Cloud endpoints

| Service                    | Endpoint                            | Protocol and port                                                        | Required when                                                 |
| -------------------------- | ----------------------------------- | ------------------------------------------------------------------------ | ------------------------------------------------------------- |
| Mago Stage API             | `eu-api.magostage.com`              | HTTPS and secure WebSocket over TCP 443                                  | Required for Mago Cloud controllers and receivers             |
| Mago Stage web application | `app.magostage.com`                 | HTTPS over TCP 443                                                       | Browser-based Mago Stage access or application links are used |
| Administration Portal      | `admin.magostage.com`               | HTTPS over TCP 443                                                       | Administrators access the Mago Stage Portal                   |
| Stage VC                   | `join.magostage.com`                | HTTPS and secure WebSocket over TCP 443                                  | Conferencing or browser-based session joining is used         |
| WebRTC Services            | `cast.magostage.com`                | Secure WebSocket over TCP 443, with additional real-time media transport | Screen sharing, audio, or video conferencing is used          |
| Present Share              | `share.mago.io`                     | HTTPS and secure WebSocket over TCP 443                                  | Present Share or Mago Room screen sharing is used             |
| Application releases       | `remagogroup.blob.core.windows.net` | HTTPS over TCP 443                                                       | Applications check for or download updates                    |

The API endpoint shown above is the current European production endpoint. If the organization is assigned to another Mago Cloud region, use the regional endpoint supplied by Mago.

### Mago Stage API

The Mago Stage API provides:

* User authentication
* Organization and account information
* Stage and content data
* Controller and receiver registration
* Display activation
* Device status
* Commands between controllers and receivers
* File uploads and downloads
* Digital signage configuration

Live control and device-status communication use a secure WebSocket connection.

The signaling endpoint is:

`wss://eu-api.magostage.com/api/hubs/signal`

Proxies and security gateways must preserve the WebSocket upgrade and must not close active connections prematurely.

### Administration Portal

Administrators access the Mago Stage Portal at:

`https://admin.magostage.com`

The administrator’s browser must also be able to reach the Mago Stage API.

Portal functions include:

* Organization management
* User and role management
* Display activation and management
* License management
* Policy configuration
* Digital signage
* Downloads
* Audit history

### Screen sharing and conferencing

Screen sharing and conferencing can require access to:

* `join.magostage.com`
* `cast.magostage.com`

These services use HTTPS, secure WebSockets, and real-time media transport.

Networks that restrict UDP traffic, apply TLS inspection, or close long-running connections may interrupt:

* Screen sharing
* Audio
* Video
* Participant connections
* Session control

Test screen sharing and conferencing through the production firewall, proxy, and Wi-Fi configuration before deployment.

{% hint style="warning" %}
Cloud real-time media can require outbound UDP traffic in addition to HTTPS and secure WebSockets over TCP 443.

The hosted media-port configuration can change as the Mago Cloud infrastructure is updated. Organizations that restrict outbound UDP or require explicit port-level firewall rules must request the current Mago Cloud media endpoint and port list from Mago Support before deployment.

Do not assume that the on-premises WebRTC port list applies to Mago Cloud.
{% endhint %}

### Application updates

Mago Stage applications retrieve update information and installation packages from:

`remagogroup.blob.core.windows.net`

Allow HTTPS downloads from this endpoint when automatic update checks or Portal-based application downloads are required.

Security tools must not modify downloaded application packages. Package modification can cause signature validation or installation failures.

### File uploads and downloads

Mago Stage transfers cloud content over HTTPS.

Files larger than 3 MB may be divided into smaller upload chunks. The 3 MB value is a chunking threshold, not a maximum supported file size.

Firewalls and proxies must:

* Permit request bodies large enough for each upload chunk
* Permit large file downloads
* Preserve authentication headers
* Avoid modifying binary content
* Allow transfers enough time to complete

Available storage, organization policies, and configured service limits may still restrict the maximum file size.

For proxy configuration, TLS inspection, and certificate requirements, see **On-Premises Certificates and Proxies**.


# Third-party service endpoints

Mago Stage connects to third-party services only when the related feature or integration is enabled.

Organizations using restrictive firewall policies must allow the required endpoints for each enabled integration.

### Endpoint summary

| Integration              | Endpoint                                  | Protocol and port                        | Required when                                                       |
| ------------------------ | ----------------------------------------- | ---------------------------------------- | ------------------------------------------------------------------- |
| Microsoft identity       | `login.microsoftonline.com`               | HTTPS over TCP 443                       | Microsoft sign-in or Microsoft account linking is enabled           |
| Microsoft Graph          | `graph.microsoft.com`                     | HTTPS over TCP 443                       | OneDrive, SharePoint, Microsoft profile, or calendar access is used |
| Google identity          | `accounts.google.com`                     | HTTPS over TCP 443                       | Google sign-in or Google account linking is enabled                 |
| Google OAuth             | `oauth2.googleapis.com`                   | HTTPS over TCP 443                       | Google authentication or account linking is enabled                 |
| Google APIs              | `www.googleapis.com`                      | HTTPS over TCP 443                       | Google Drive, profile, or calendar access is used                   |
| Google client services   | `apis.google.com`                         | HTTPS over TCP 443                       | Google account or Drive integrations are used                       |
| Apple identity           | `appleid.apple.com`                       | HTTPS over TCP 443                       | Sign in with Apple is enabled                                       |
| SendGrid                 | `api.sendgrid.com`                        | HTTPS over TCP 443                       | SendGrid email delivery is configured                               |
| Customer SMTP server     | Organization-configured hostname          | Configured SMTP port                     | SMTP email delivery is configured                                   |
| YouTube                  | `www.youtube.com`                         | HTTPS over TCP 443                       | YouTube search, playback, playlists, or signage is used             |
| YouTube links            | `youtu.be`                                | HTTPS over TCP 443                       | Shortened YouTube links are used                                    |
| Privacy-enhanced YouTube | `www.youtube-nocookie.com`                | HTTPS over TCP 443                       | Privacy-enhanced embedded videos are used                           |
| YouTube thumbnails       | `i.ytimg.com` and `img.youtube.com`       | HTTPS over TCP 443                       | YouTube thumbnails are displayed                                    |
| YouTube media delivery   | YouTube and Google media-delivery domains | HTTPS over TCP 443                       | YouTube video or audio is played                                    |
| Website thumbnails       | `image.thum.io`                           | HTTPS over TCP 443                       | Mago Stage generates previews of website content                    |
| Embedded web content     | Customer-selected website domains         | HTTP or HTTPS as required by the website | Websites are added to a Stage                                       |

These endpoints can redirect to additional domains operated by the provider. Organizations using strict domain allowlists should also follow the provider’s current network documentation.

### Microsoft 365

Microsoft connectivity is required when users:

* Sign in with a Microsoft account
* Link a Microsoft 365 account
* Browse OneDrive
* Browse SharePoint
* Access Microsoft profile information
* Access Microsoft calendar information

Required endpoints include:

* `login.microsoftonline.com`
* `graph.microsoft.com`

Microsoft authentication may use tenant-specific paths under `login.microsoftonline.com`.

The Microsoft Entra administrator may need to grant tenant-wide consent for the permissions requested by Mago Stage. Firewall access alone does not grant users access to Microsoft 365 data.

Organization policies can restrict:

* Third-party application consent
* Access to OneDrive or SharePoint
* Cross-tenant sharing
* External accounts
* Conditional Access
* Device compliance
* File downloads

Test Microsoft sign-in and file access using an account with the same policies as the intended users.

### Google Workspace

Google connectivity is required when users:

* Sign in with a Google account
* Link a Google Workspace account
* Browse Google Drive
* Select Google Drive files
* Select Google Drive folders
* Access Google profile information
* Access Google calendar information

Required endpoints include:

* `accounts.google.com`
* `oauth2.googleapis.com`
* `www.googleapis.com`
* `apis.google.com`

Google authentication requires a valid HTTPS callback domain. A bare IP address or an unencrypted HTTP callback is not suitable for a production deployment.

Google Workspace administrators can restrict:

* Third-party OAuth applications
* Requested OAuth permissions
* Access to files outside the organization
* External sharing
* Shared drives
* File downloading
* Account linking

Test Google sign-in, file selection, folder selection, and content refresh using an account governed by the intended production policies.

### Sign in with Apple

Allow access to:

`appleid.apple.com`

This endpoint is required only when Sign in with Apple is configured and made available to users.

Apple authentication also requires correctly configured application identifiers, redirect addresses, and signing credentials.

### YouTube

YouTube features can require access to:

* `www.youtube.com`
* `youtube.com`
* `youtu.be`
* `www.youtube-nocookie.com`
* `i.ytimg.com`
* `img.youtube.com`
* YouTube and Google-operated media-delivery domains

These endpoints support:

* YouTube URL recognition
* Search
* Video information
* Thumbnails
* Embedded playback
* Playlists
* Digital signage

Allowing only `youtube.com` may not be sufficient for playback. YouTube media can be delivered through regional content-delivery domains that change over time.

YouTube access may also be affected by:

* Geographic restrictions
* Age restrictions
* Authentication requirements
* Copyright restrictions
* Organization content filters
* Video owner embedding settings
* Advertising or tracking restrictions

Test representative YouTube content through the production network before deployment.

### Email delivery

Mago Stage can send invitations, account messages, and notifications through SendGrid or a customer-provided SMTP service.

#### SendGrid

Allow access to:

`api.sendgrid.com`

SendGrid API delivery uses HTTPS over TCP 443.

#### Customer SMTP

The required address, port, and encryption method depend on the organization’s mail server.

Common SMTP ports include:

| Port    | Typical use                                |
| ------- | ------------------------------------------ |
| TCP 25  | Server-to-server SMTP or an internal relay |
| TCP 465 | SMTP over implicit TLS                     |
| TCP 587 | SMTP submission using STARTTLS             |

Use the port and encryption method specified by the organization’s email administrator.

Do not enable unencrypted SMTP across untrusted networks.

### Website content

Mago Stage can display customer-selected websites. Each website can load resources from additional services, including:

* Content-delivery networks
* Video platforms
* Font providers
* Authentication systems
* Analytics services
* Maps
* Embedded applications
* Advertising services

The customer is responsible for approving and allowing the domains required by its selected websites.

A website loading successfully in a normal browser does not confirm that it will work on the receiver network. Test the website from the intended receiver using the production firewall, proxy, and content-filtering policies.

### Website thumbnails

Mago Stage may use the following service to generate website preview images:

`image.thum.io`

Allow outbound HTTPS over TCP 443 to this endpoint when website preview images are required.

Blocking this service may prevent a preview image from appearing without necessarily preventing the website itself from opening.

### Security considerations

Only enable and allow third-party services that the organization intends to use.

Before enabling an integration:

1. Review the permissions requested by Mago Stage.
2. Obtain approval from the organization’s identity or security administrator.
3. Configure the provider’s application registration.
4. Restrict access according to organization policy.
5. Test with a representative user account.
6. Confirm that authentication redirects are not blocked.
7. Confirm that linked content can be opened from the receiver network.
8. Document the approved integration and responsible owner.


# On-premises firewall ports

An on-premises Mago Stage deployment runs several services on the customer’s server. Firewall access depends on which services are enabled and whether a reverse proxy is used.

Only allow access from authorized controller, receiver, administrator, and server networks.

### Core service ports

| Service                | Direction         | Protocol and port | Required by                                                          | Status                                                  |
| ---------------------- | ----------------- | ----------------- | -------------------------------------------------------------------- | ------------------------------------------------------- |
| Mago Stage API         | Inbound to server | TCP 5083          | Controllers, receivers, Administration Portal, and Remote Controller | Required                                                |
| Administration Portal  | Inbound to server | TCP 4000          | Administrator browsers                                               | Required                                                |
| Remote Controller      | Inbound to server | TCP 8080          | Administrators using Mago Remote                                     | Required when Mago Remote is used                       |
| Present web controller | Inbound to server | TCP 5000          | Browser-based controllers                                            | Required when Present is enabled                        |
| Stage VC               | Inbound to server | TCP 3000          | Controllers and receivers using conferencing                         | Required when Stage VC is enabled and accessed directly |

These are the default host ports used by the standard Mago Stage server deployment.

If services are published through a reverse proxy on TCP 443, the original service ports should remain restricted to the server, management network, or reverse proxy.

### Bundled WebRTC ports

The following ports apply when the bundled on-premises WebRTC service is installed.

| Function                    | Direction         | Protocol and port | Purpose                                                                       |
| --------------------------- | ----------------- | ----------------- | ----------------------------------------------------------------------------- |
| WebRTC signaling and health | Inbound to server | TCP 7880          | WebSocket signaling and service health in plain LAN mode                      |
| ICE over TCP                | Inbound to server | TCP 7881          | TCP media fallback                                                            |
| WebRTC media                | Inbound to server | UDP 7882          | Primary real-time audio, video, and screen-sharing media                      |
| WebRTC TLS entry point      | Inbound to server | TCP 443           | Secure WebSocket signaling and TURN over TLS                                  |
| TURN over UDP               | Inbound to server | UDP 3478          | Relayed media when TLS mode is enabled and direct connectivity is unavailable |

For the best real-time performance, allow UDP 7882 between participating devices and the WebRTC server.

TCP fallback can maintain connectivity where UDP is restricted, but it may provide lower performance or reliability for real-time media.

### Port requirements by deployment type

#### Basic deployment

A Basic deployment runs the Mago Stage server and receiver on the same Windows machine.

A controller can run on another supported device, such as an iPad, when it can reach the Basic server over the permitted network.

Basic uses the applicable on-premises service ports documented on this page:

* Allow access to the Mago Stage API from authorized controllers.
* Allow Administration Portal access from authorized administrator devices.
* Allow additional service and WebRTC ports only when the corresponding features are enabled.
* Keep database, Redis, container-management, and other internal service ports restricted to the local server.

When services are published through a reverse proxy, controllers and administrator devices can use TCP 443 instead of directly accessing the underlying service ports.

#### Core deployment

Open the following ports:

| Port | Protocol | Service               |
| ---- | -------- | --------------------- |
| 5083 | TCP      | Mago Stage API        |
| 4000 | TCP      | Administration Portal |

#### Core deployment with Mago Remote

Open the core ports and:

| Port | Protocol | Service           |
| ---- | -------- | ----------------- |
| 8080 | TCP      | Remote Controller |

#### Core deployment with Present

Open the core ports and:

| Port | Protocol | Service                |
| ---- | -------- | ---------------------- |
| 5000 | TCP      | Present web controller |

#### Core deployment with Stage VC

Open the core ports and:

| Port | Protocol | Service                      |
| ---- | -------- | ---------------------------- |
| 3000 | TCP      | Stage VC direct service port |

When Stage VC is published through HTTPS, clients may connect through TCP 443 instead of directly using TCP 3000.

#### Core deployment with bundled WebRTC

Open the core ports and:

| Port | Protocol | Service                                                     |
| ---- | -------- | ----------------------------------------------------------- |
| 7880 | TCP      | WebRTC signaling in plain LAN mode                          |
| 7881 | TCP      | ICE over TCP                                                |
| 7882 | UDP      | WebRTC media                                                |
| 3478 | UDP      | TURN over UDP when TLS mode is enabled                      |
| 443  | TCP      | Secure signaling and TURN over TLS when TLS mode is enabled |

The exact set depends on whether WebRTC uses plain LAN mode or TLS mode.

### Plain LAN mode

In plain LAN mode, clients connect directly to the WebRTC server using:

`ws://<server-address>:7880`

Required ports are:

* TCP 7880 for signaling
* TCP 7881 for ICE over TCP
* UDP 7882 for real-time media

Plain LAN mode should only be used on a trusted private network.

Browser security restrictions may prevent camera or microphone access over an insecure connection. Use TLS mode when browser-based conferencing or screen sharing is required.

### TLS mode

In TLS mode, clients connect using a secure address such as:

`wss://webrtc.magosrv.com`

TLS mode uses:

* TCP 443 for secure signaling and TURN over TLS
* UDP 3478 for TURN over UDP
* TCP 7881 for ICE over TCP
* UDP 7882 for real-time media

The example hostname must be replaced with the DNS name assigned to the deployment.

TLS mode requires a valid certificate matching the WebRTC hostname.

### Source networks

Restrict inbound rules according to the service.

| Service                | Recommended source                                                                  |
| ---------------------- | ----------------------------------------------------------------------------------- |
| Mago Stage API         | Authorized controller, receiver, Portal, Remote Controller, and management networks |
| Administration Portal  | Administrator and management networks                                               |
| Remote Controller      | Administrator and management networks                                               |
| Present web controller | Authorized user and presentation networks                                           |
| Stage VC               | Authorized controller and receiver networks                                         |
| WebRTC                 | Authorized controller, receiver, and conferencing networks                          |

If devices connect from another site, provide access through an approved routed network, site-to-site VPN, remote-access VPN, or secured public entry point.

Do not expose raw container ports directly to the public internet.

### Internal-only services

The standard deployment also contains internal container services that do not require client firewall rules.

These include:

* Database services
* Redis
* YouTube token-provider services
* Container management interfaces
* Internal Docker networking

Do not publish these services to user networks or the public internet.

### Reverse proxy deployments

A reverse proxy can publish Mago Stage services through TCP 443 while keeping the original container ports restricted to the server or management network. The proxy must support WebSockets, uploads, long-lived connections, and the required WebRTC transports. See **On-Premises Certificates and Proxies** for configuration requirements.


# On-premises DNS and service addresses

An on-premises Mago Stage deployment can use direct server addresses or dedicated DNS names.

Dedicated DNS names with HTTPS are recommended for production deployments. They provide clearer service separation, support trusted certificates, and avoid browser restrictions associated with insecure connections.

### Recommended service names

The following table illustrates a deployment using the example domain `magosrv.com`.

| Service                | Example public address                | Default internal target            |
| ---------------------- | ------------------------------------- | ---------------------------------- |
| Mago Stage API         | `https://api.magosrv.com/api`         | `http://<server-address>:5083/api` |
| Administration Portal  | `https://admin.magosrv.com`           | `http://<server-address>:4000`     |
| Remote Controller      | `https://remote.magosrv.com`          | `http://<server-address>:8080`     |
| Present web controller | `https://present.magosrv.com`         | `http://<server-address>:5000`     |
| Stage VC               | `https://vc.magosrv.com`              | `https://<server-address>:3000`    |
| WebRTC                 | `wss://webrtc.magosrv.com`            | `ws://<server-address>:7880`       |
| WebRTC TURN            | `turns://turn-webrtc.magosrv.com:443` | `<server-address>:443`             |

Replace `magosrv.com` and `<server-address>` with the values assigned to the deployment.

Do not use these example addresses in production unless the domain has specifically been assigned to the deployment.

### Required service address configuration

Record the following addresses during installation:

| Configuration value       | Example                               |
| ------------------------- | ------------------------------------- |
| Mago Stage API            | `https://api.magosrv.com/api`         |
| Administration Portal     | `https://admin.magosrv.com`           |
| Remote Controller         | `https://remote.magosrv.com`          |
| Present web controller    | `https://present.magosrv.com`         |
| Stage VC                  | `https://vc.magosrv.com`              |
| WebRTC                    | `wss://webrtc.magosrv.com`            |
| WebRTC TURN               | `turns://turn-webrtc.magosrv.com:443` |
| SSO callback base address | `https://api.magosrv.com`             |

The address entered in the application configuration must match the address that controllers, receivers, and browsers use to reach the service.

Do not configure `localhost` when the service must be reached from another device. On a controller or receiver, `localhost` refers to that device—not the Mago Stage server.

### DNS records

Create an A or AAAA record for each enabled service.

Example:

| DNS record                | Resolves to                                            |
| ------------------------- | ------------------------------------------------------ |
| `api.magosrv.com`         | Mago Stage server or reverse-proxy address             |
| `admin.magosrv.com`       | Mago Stage server or reverse-proxy address             |
| `remote.magosrv.com`      | Mago Stage server or reverse-proxy address             |
| `present.magosrv.com`     | Mago Stage server or reverse-proxy address             |
| `vc.magosrv.com`          | Mago Stage server or reverse-proxy address             |
| `webrtc.magosrv.com`      | WebRTC server, load balancer, or reverse-proxy address |
| `turn-webrtc.magosrv.com` | WebRTC server, load balancer, or TLS gateway address   |

Create records only for services enabled in the deployment.

Explicit DNS records are recommended because they make ownership and troubleshooting clearer.

#### Wildcard DNS

A wildcard DNS record can direct multiple service names to the same server or reverse proxy.

Example:

`*.magosrv.com`

A wildcard record does not:

* Create service routing
* Configure the reverse proxy
* Open firewall ports
* Issue a certificate
* Confirm that every service is installed

Wildcard DNS behavior depends on the organization’s DNS provider and record configuration. Do not assume that a wildcard DNS record provides certificate coverage for the same hostnames.

Use explicit records where the organization requires strict change control or where services resolve to different addresses.

### Internal-only deployments

For services available only on the customer’s private network:

* Use the organization’s internal DNS service.
* Resolve each service name to the server’s private address.
* Restrict firewall access to authorized internal networks.
* Use a certificate trusted by every controller, receiver, and administrator device.
* Do not publish the service names through public DNS unless required.

Internal-only deployments can use an organization-owned internal subdomain, such as:

* `api.stage.example.com`
* `admin.stage.example.com`
* `webrtc.stage.example.com`

Avoid unqualified hostnames such as `stage-server`. Fully qualified domain names provide more predictable certificate and DNS behavior.

### Public or multi-site deployments

A deployment accessed from other sites or external networks requires:

* Public or appropriately routed DNS
* A secured public entry point or VPN
* Valid TLS certificates
* Restricted firewall rules
* Protection against unauthorized access
* A routing design that supports WebSockets and real-time media

Do not expose raw API, container, database, Redis, or management ports directly to the public internet.

Use a reverse proxy, load balancer, VPN, or other approved security gateway.

### Split DNS

Split DNS allows the same hostname to resolve differently depending on the requesting network.

For example:

* Internal clients resolve `api.magosrv.com` to the server’s private address.
* Authorized external clients resolve `api.magosrv.com` to a secured public address.

Split DNS can avoid unnecessary routing through the public gateway and can simplify certificate configuration because clients continue using the same hostname.

Confirm that:

* Internal and external records use the intended addresses.
* Both routes present a certificate valid for the hostname.
* WebSocket connections work through both routes.
* Firewall policies permit the required traffic.
* Remote sites do not receive an unreachable private address.

### Application origins

Browser security policies distinguish between origins using the scheme, hostname, and port.

For example, these are different origins:

* `https://admin.magosrv.com`
* `http://admin.magosrv.com`
* `https://admin.magosrv.com:4000`
* `https://remote.magosrv.com`

Configure allowed origins using the exact addresses presented to users.

The Remote Controller must trust the exact Administration Portal origin used by the browser. A mismatch in the scheme, hostname, or port can prevent the Portal from opening or transferring control to the Remote Controller.

### SSO callback addresses

Single sign-on providers redirect users to a registered callback address after authentication.

The callback address must:

* Use the correct public API hostname
* Use HTTPS in production
* Match the address registered with the identity provider
* Be reachable by the user’s browser
* Present a trusted certificate

Google authentication requires a real HTTPS callback domain. A bare IP address or unencrypted HTTP callback is not suitable for production.

Update the identity-provider registration whenever the service hostname changes.

### Address changes

Changing a service hostname can affect:

* Application configuration
* DNS
* Certificates
* Firewall rules
* Reverse-proxy routes
* Allowed origins
* SSO callback addresses
* Bookmarks and deployment records

Plan hostname changes as a controlled deployment change.

Update all dependent settings before retiring the previous address.


# On-premises certificates and proxies

On-premises certificates and proxies  Production on-premises deployments should use HTTPS and secure WebSockets for all browser-accessible services.

Trusted certificates are especially important for authentication, screen sharing, camera access, microphone access, Stage VC, and WebRTC.

### Certificate requirements

Certificates used by Mago Stage must:

* Be valid for the service hostname
* Be within their validity period
* Include the required intermediate certificate chain
* Be trusted by controllers, receivers, servers, and administrator devices
* Use a supported key type and strength
* Be available in PEM format where certificate files are loaded directly
* Have a private key matching the certificate
* Be renewed before expiration

The certificate’s Subject Alternative Name must contain every hostname presented to clients.

Modern clients require the service hostname in the certificate’s Subject Alternative Name. The Common Name is ignored for hostname validation.

### Certificate coverage

Using the example `magosrv.com` service names, certificates must cover the corresponding hostnames.

| Service                | Example hostname          | Certificate requirement                                |
| ---------------------- | ------------------------- | ------------------------------------------------------ |
| Mago Stage API         | `api.magosrv.com`         | Certificate must include `api.magosrv.com`             |
| Administration Portal  | `admin.magosrv.com`       | Certificate must include `admin.magosrv.com`           |
| Remote Controller      | `remote.magosrv.com`      | Certificate must include `remote.magosrv.com`          |
| Present web controller | `present.magosrv.com`     | Certificate must include `present.magosrv.com`         |
| Stage VC               | `vc.magosrv.com`          | Certificate must include `vc.magosrv.com`              |
| WebRTC signaling       | `webrtc.magosrv.com`      | Certificate must include the WebRTC signaling hostname |
| WebRTC TURN            | `turn-webrtc.magosrv.com` | Certificate must include the TURN hostname             |

Replace the example hostnames with the names assigned to the deployment.

### Wildcard certificates

A wildcard certificate such as:

`*.magosrv.com`

can cover first-level hostnames including:

* `api.magosrv.com`
* `admin.magosrv.com`
* `remote.magosrv.com`
* `present.magosrv.com`
* `vc.magosrv.com`
* `webrtc.magosrv.com`
* `turn-webrtc.magosrv.com`

The wildcard does not cover:

* The root name `magosrv.com`
* A deeper name such as `api.eu.magosrv.com`
* A service using a different domain

Confirm that the certificate includes every required hostname before deployment.

### Stage VC certificate files

Stage VC loads its certificate from the `certs` folder in the main Mago Stage installation directory.

| File      | Purpose                                         |
| --------- | ----------------------------------------------- |
| `tls.crt` | Stage VC certificate and certificate chain      |
| `tls.key` | Matching private key                            |
| `ca.crt`  | Optional additional certificate-authority chain |

The certificate must match the hostname used to access Stage VC, such as:

`vc.magosrv.com`

Without `tls.crt` and `tls.key`, Stage VC can fall back to plain HTTP. Browsers generally block camera and microphone access over insecure HTTP except on localhost.

Use HTTPS for production Stage VC deployments.

### WebRTC certificate files

The bundled WebRTC TLS service uses a separate certificate folder and different filenames.

Place the files in the WebRTC `certs` folder:

| File       | Purpose                                                             |
| ---------- | ------------------------------------------------------------------- |
| `cert.pem` | Certificate chain containing the leaf and intermediate certificates |
| `key.pem`  | Matching unencrypted private key in PEM format                      |

The certificate must cover both the WebRTC signaling hostname and the TURN hostname.

For example:

* `webrtc.magosrv.com`
* `turn-webrtc.magosrv.com`

A wildcard certificate can cover both names when they use the same parent domain.

The bundled WebRTC TLS configuration does not automatically request certificates from a public certificate authority. The customer or installer must provide the certificate files.

If the required WebRTC certificate files are missing, the installer can fall back to plain LAN mode using `ws://<server-address>:7880`.

Plain LAN mode is not recommended for browser-based production deployments.

### Public and private certificate authorities

A public certificate authority is recommended when services are accessed by unmanaged devices, external users, or devices outside the customer’s domain.

A private certificate authority can be used for internal-only deployments if every connecting device trusts the issuing authority.

When using a private certificate authority:

* Install the root and required intermediate certificates on every controller.
* Install them on every receiver.
* Install them on administrator devices.
* Install them on the server and reverse proxy where required.
* Confirm trust in both applications and browsers.
* Include mobile devices in the certificate deployment plan.

Manually accepting a browser certificate warning is not a valid production configuration. Native applications and WebSocket clients may reject the connection without offering an override.

### Private-key protection

Private keys must be treated as secrets.

* Restrict access to authorized administrators and service accounts.
* Do not include private keys in support packages.
* Do not include private keys in screenshots.
* Do not commit private keys to source control.
* Do not send private keys through unapproved email or messaging systems.
* Back up keys only through an approved secrets-management or backup process.

The WebRTC `key.pem` file must be unencrypted for the service to load it automatically. Protect access to the file and its containing directory accordingly.

### Certificate renewal

Record the following for every certificate:

* Covered services
* Issuing authority
* Issue date
* Expiration date
* Renewal owner
* Renewal process
* Required service restart
* Validation procedure

Before replacing a certificate:

1. Confirm that the new certificate covers every required hostname.
2. Confirm that the private key matches the certificate.
3. Confirm that the complete intermediate chain is included.
4. Back up the active certificate according to the organization’s security policy.
5. Replace the certificate files or update the reverse proxy.
6. Restart or reload the affected service.
7. Test the service from a controller, receiver, and administrator device.
8. Confirm the new expiration date.
9. Update the organization’s deployment records with the new certificate details and expiration date.

Do not wait until the expiration date to test a replacement certificate.

### Reverse-proxy requirements

A reverse proxy used with Mago Stage must:

* Terminate TLS using a valid certificate
* Route each hostname to the correct internal service
* Preserve the original hostname
* Forward client protocol information
* Preserve authorization headers
* Support WebSocket upgrades
* Allow long-lived WebSocket connections
* Support file uploads and downloads
* Use suitable request-size limits
* Use suitable connection and request timeouts

A basic web-page test is not sufficient. A proxy may successfully load the Portal while still blocking WebSockets, uploads, or real-time communication.

### WebSocket proxy behavior

The Mago Stage API uses WebSockets for device signaling and live status.

The proxy must preserve:

* The HTTP upgrade request
* The `Upgrade` header
* The `Connection` header
* Authentication information
* Long-running connections

Avoid short idle timeouts. Closing idle WebSockets too aggressively can make receivers appear offline or delay commands.

The signaling path is:

`/api/hubs/signal`

### WebRTC proxy considerations

WebRTC uses more than ordinary HTTPS traffic.

It can require:

* Secure WebSocket signaling
* ICE over TCP
* WebRTC media over UDP
* TURN over UDP
* TURN over TLS

A standard HTTP reverse proxy does not automatically proxy WebRTC UDP media.

The bundled WebRTC TLS gateway uses the requested TLS hostname to route signaling and TURN traffic. The signaling and TURN hostnames must:

* Resolve to the correct server
* Be included in the certificate
* Be permitted through the firewall
* Route to the correct WebRTC services

Confirm that TCP 443 is not already assigned to an incompatible service on the same server address.

### Forwarded client information

When Mago Stage is placed behind a reverse proxy, the application may need forwarded headers to determine:

* The original HTTPS scheme
* The public hostname
* The client address
* The correct SSO callback address

Only trust forwarded headers from known proxies or networks.

Do not configure the application to trust forwarded headers from every source unless the security implications have been reviewed.

### TLS inspection

TLS inspection can interfere with:

* Certificate validation
* WebSocket connections
* WebRTC signaling
* Real-time media
* SSO redirects
* Cloud-storage authentication
* Application downloads

Where inspection is required, test every enabled workflow through the production inspection service.

Create approved inspection exceptions for affected authentication, WebSocket, media, or application-download endpoints when required.


# Mago Stage Client Apps

Use the Mago Stage applications to configure a device as a controller or receiver.

A **controller** is used to create and manage Stages, add content, connect to receivers, and control presentations.

A **receiver** displays content sent from a controller.

#### Get started

1. Review **Before you begin**.
2. Install the appropriate Mago Stage application.
3. Select the correct Mago Stage environment.
4. Sign in when required.
5. Activate the device when it will operate as a receiver.
6. Connect the controller to the intended receiver.

#### In this section

Use these guides to:

* Install Mago Stage
* Select a Cloud or on-premises environment
* Sign in and manage connected accounts
* Activate a receiver
* Connect a controller to a receiver
* Create and manage Stages
* Add and control content
* Start a presentation
* Share a screen
* Review supported formats, cloud behavior, and license limits

For platform versions and device support, see **Supported platforms**.

For hardware guidance, see **Controller requirements** and **Receiver requirements**.


# Before you begin

Before installing or configuring Mago Stage, confirm which device role, service environment, account, and permissions you will use.

#### Choose the device role

Determine whether the device will act as a controller or receiver.

* A **controller** is used to create and manage Stages, add content, connect displays, and control presentations.
* A **receiver** displays content sent from a controller.

Some platforms support both roles. See **Supported platforms** for platform availability.

#### Check the device

Confirm that the device meets the applicable requirements:

* Supported operating system or browser
* Sufficient processor, memory, and storage
* Suitable display resolution
* Current operating-system and graphics updates
* Reliable network connection
* Required camera, microphone, or screen-sharing capabilities

See **Controller requirements** or **Receiver requirements** for details.

Mago Stage mobile controllers are optimized for tablets. Phone-sized controllers support selected workflows but provide a more limited working area.

#### Identify the service environment

Mago Stage can connect to:

* Mago Cloud
* A self-hosted or on-premises environment

Use the service environment specified by your administrator.

For an on-premises environment, obtain the exact server address before setup. Include `https://` where applicable.

Accounts, receivers, Stages, and configuration belong to the selected environment. Changing environments signs the user out and may make content from the previous environment unavailable until the device reconnects to it.

#### Prepare the user account

Depending on the organization’s configuration, users may sign in with:

* An organization-created email address and password
* Microsoft single sign-on
* Google single sign-on
* Apple single sign-on
* Another identity provider configured by the organization

Obtain the required account or invitation from the organization administrator.

The available sign-in methods depend on the selected Mago Stage environment and the organization’s authentication policies.

#### Prepare the receiver

Before a controller can use a receiver, the receiver must normally be:

* Installed on a supported device
* Connected to the correct Mago Stage environment
* Activated in the Administration Portal
* Assigned an available display license
* Online and reachable
* Connected to the intended display and audio equipment

An organization administrator may be required to complete receiver activation.

#### Prepare the controller

Before connecting to a receiver, confirm that the controller:

* Uses the same Mago Stage environment as the receiver
* Has a working network connection
* Can sign in when authentication is required
* Can reach the receiver through the Mago Stage service
* Has permission to use the intended features

The controller and receiver do not need to be on the same local network when permitted by the active license, routing configuration, and organization policies.

Basic requires the Mago Stage server and receiver to run on the same Windows machine. Pro supports receivers available on the private network. Ultra and Cloud can support local or remote receivers, subject to the applicable server and network configuration.

Both devices must be able to reach the same Mago Stage environment.

#### Prepare cloud accounts

A connected Microsoft 365 or Google account is required only when using supported cloud files, folders, profiles, or calendar features.

Before connecting an account, confirm that:

* The provider is enabled by the organization.
* The account is permitted to use third-party applications.
* Required administrator consent has been granted.
* The user has access to the intended files or folders.
* Organization sharing policies permit the intended workflow.

Cloud accounts can be connected after signing in to Mago Stage.

#### Prepare application permissions

Mago Stage requests permissions only when the related feature is used.

| Permission                            | Required for                                                   |
| ------------------------------------- | -------------------------------------------------------------- |
| Local network                         | Finding and communicating with displays on supported platforms |
| Camera                                | QR-code scanning, photographs, document scanning, and video    |
| Microphone                            | Audio and conferencing                                         |
| Photos or media library               | Selecting photographs and videos                               |
| Files or storage                      | Selecting and saving local content                             |
| Screen recording or screen capture    | Sharing the controller’s screen                                |
| Notifications                         | Supported status, update, or session notifications             |
| Prevent sleep or background operation | Continuous receiver operation and supported sharing workflows  |

Permission names vary by operating system.

If a permission is denied, the related feature may remain unavailable until access is enabled in the device settings.

#### Check the network

Confirm that:

* Required Mago Stage services are reachable.
* DNS resolves the required service addresses.
* HTTPS and secure WebSocket connections are permitted.
* The connection is stable enough for the intended content.
* Screen sharing and conferencing traffic are permitted when those features are used.
* A fixed receiver uses wired Ethernet where practical.

See **Network requirements** for detailed connectivity guidance.

#### Information to collect

Before beginning setup, collect the applicable information:

| Information                         | Needed for                                    |
| ----------------------------------- | --------------------------------------------- |
| Mago Stage environment              | All installations                             |
| Corporate server address            | On-premises deployments                       |
| User email address                  | Account sign-in                               |
| Temporary or existing password      | Password-based sign-in                        |
| Identity provider                   | Single sign-on                                |
| Receiver activation code            | Registering a new receiver                    |
| Available display license           | Receiver activation                           |
| Receiver connection code or QR code | Connecting a controller                       |
| Microsoft or Google account         | Cloud content and connected features          |
| Required application permissions    | Camera, microphone, files, and screen sharing |

After these requirements are ready, continue with the installation and setup instructions for the intended controller or receiver.


# Install Mago Stage

Install the Mago Stage application that matches the device’s platform and intended role.

Only install packages obtained from the Mago Stage Administration Portal, an approved app store, or the organization’s managed software-distribution system.

### Choose the correct application

| Platform        | Controller | Receiver | Distribution                                         |
| --------------- | ---------- | -------- | ---------------------------------------------------- |
| Windows         | Yes        | Yes      | Administration Portal or managed software deployment |
| Android         | Yes        | Yes      | Administration Portal or managed software deployment |
| iPhone and iPad | Yes        | No       | Apple App Store or managed Apple deployment          |
| macOS           | No         | Yes      | Administration Portal or managed software deployment |
| Web browser     | Yes        | Yes      | No local installation required                       |

Controller and receiver packages are not interchangeable. Confirm the intended device role before downloading an installer.

### Download from the Administration Portal

When software downloads are available through the organization’s Administration Portal:

1. Sign in to the Administration Portal.
2. Select **Downloads**.
3. Find **Mago Stage**.
4. Select the required platform.
5. Select the **Controller** or **Receiver** package.
6. Review the published version.
7. Select **Download**.
8. Review the changelog when available.
9. Follow the platform-specific installation instructions below.

The packages shown on the Downloads page depend on the selected environment and the releases published by the organization.

### Install on Windows

1. Download the appropriate Windows controller or receiver package.
2. Close any running instance of Mago Stage.
3. Open the downloaded installer.
4. Approve the operating-system security prompt when requested.
5. Follow the installation instructions.
6. Open Mago Stage after installation.
7. Confirm that the expected Controller or Receiver experience opens.

Administrator approval may be required depending on the organization’s Windows policies.

If Windows blocks the installer, confirm that:

* The installer came from the approved Mago Stage download location.
* The package has not been modified.
* The device permits installation of organization-approved applications.
* Endpoint security has not quarantined the package.

Do not bypass an organization security warning without approval from the IT administrator.

### Install on Android

Android controller and receiver packages are distributed separately.

1. Download the required Android package from the approved source.
2. Select the Controller or Receiver package for the device’s intended role.
3. Open the downloaded package.
4. Approve the installation when prompted.
5. Open Mago Stage after installation.
6. Grant permissions required for the intended features.

When the package is installed directly rather than through a managed application store, Android may request permission to install applications from that source.

Only enable this permission for an organization-approved download source. Disable it again after installation when required by the organization’s security policy.

For managed deployments, the organization can distribute the application through its mobile-device-management or enterprise-mobility platform.

### Install on iPhone or iPad

Mago Stage on iPhone and iPad supports the controller role.

1. Open [Mago Stage on the Apple App Store](https://apps.apple.com/us/app/mago-stage/id6742988201).
2. Select **Get** or the download button.
3. Complete Apple authentication when prompted.
4. Open Mago Stage.
5. Grant the permissions required for the intended features.

An organization can also distribute the application through its managed Apple deployment system.

Mago Stage is optimized for iPad. The iPhone application supports selected workflows with a more compact interface.

### Install on macOS

Mago Stage on macOS supports the receiver role.

1. Download the macOS receiver package from the approved source.
2. Open the downloaded disk image.
3. Move Mago Stage to the **Applications** folder when prompted.
4. Open Mago Stage from **Applications**.
5. Approve the operating-system security prompt when requested.
6. Grant the permissions required for receiver operation.

If macOS prevents the application from opening, confirm that:

* The package was obtained from the approved download location.
* The download completed successfully.
* The device permits organization-approved applications.
* The installed release is signed and notarized.
* Endpoint security has not quarantined the application.

Do not disable macOS security controls to install an unverified package.

### Use Mago Stage in a browser

A browser-based Mago Stage experience does not require local installation.

1. Open a supported browser.
2. Go to the address supplied by Mago or the organization administrator.
3. Allow pop-up windows when required.
4. Sign in when prompted.
5. Grant screen-sharing, camera, or microphone permission when using the related feature.

Browser capabilities depend on the operating system and browser.

Screen capture is not supported from mobile browsers or Safari on iPhone and iPad. Use the native Mago Stage application for supported mobile sharing workflows.

### Managed deployment

Organizations can deploy Mago Stage through supported software-management tools.

Before a managed rollout:

* Select the correct controller or receiver package.
* Confirm the target operating system.
* Confirm the application version.
* Test installation on a representative device.
* Test upgrades from the currently deployed version.
* Configure required application permissions.
* Confirm firewall and proxy access.
* Define how devices will receive future updates.
* Avoid installing controller and receiver packages on the wrong device group.

### Confirm the installation

After installation:

1. Open Mago Stage.
2. Confirm that the application starts without an error.
3. Confirm that the intended Controller or Receiver role appears.
4. Confirm that the application version matches the approved release.
5. Confirm that the device can reach the required Mago Stage services.
6. Continue with selecting the correct service environment.

Do not activate a receiver or sign in until the application is connected to the correct Mago Cloud or on-premises environment.


# Select the Mago Stage environment

Mago Stage can connect to Mago Cloud or to a customer-managed corporate server.  Controllers and receivers must use the same environment before they can connect and work together.

### Mago Cloud

Mago Cloud is the default environment for standard Mago-hosted deployments.

No server configuration is normally required when using Mago Cloud. Open the application and continue to sign-in or receiver activation.

Mago Cloud requires access to the endpoints listed under **Cloud connectivity**.

### Corporate server

Select a corporate server when the organization hosts its own Mago Stage environment.

Obtain the exact server address from the organization administrator before continuing.

The address may resemble:

`https://api.magosrv.com`

or:

`https://api.magosrv.com/api`

Use the address supplied by the administrator. Do not guess the hostname, protocol, port, or path.

### Set a corporate server

You can select a corporate server from the sign-in screen or receiver activation screen.

1. Open Mago Stage.
2. Go to the sign-in or receiver activation screen.
3. Open the **Settings** control.
4. Select **Set corporate server**.
5. Enter the address supplied by the administrator in **Corporate Server URL**.
6. Include `https://` when required.
7. Select **Save**.
8. Wait while Mago Stage retrieves the server configuration.
9. Sign in or activate the receiver in the selected environment.

On the receiver activation screen, the Settings control appears near the lower-right corner.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F0wcjnJHcIS5x8mlM1xVh%2Fselect-environment-menu.png?alt=media&amp;token=0112664e-aacb-4b5b-bf82-eee895814d59" alt=""><figcaption></figcaption></figure>

### Confirm the environment

Before signing in or activating a receiver, confirm that:

* The address was copied correctly.
* The protocol is correct.
* The hostname resolves through DNS.
* The device trusts the server certificate.
* The server is reachable from the device’s network.
* The controller and receiver use the same environment.
* The organization account and licenses exist in that environment.

If the corporate server cannot be reached, Mago Stage may be unable to retrieve its configuration.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2Fr1yMHISLnS1Aukc26zRO%2Fcorporate-server-address.png?alt=media&amp;token=b8d7407f-bf22-4ce7-9d7b-a2871e8a573e" alt=""><figcaption></figcaption></figure>

### Return to Mago Cloud

To remove the corporate-server setting and return to Mago Cloud:

1. Open the sign-in or receiver activation screen.
2. Open **Settings**.
3. Select **Use cloud server**.
4. Complete device authentication when requested.
5. Wait while the corporate-server configuration is cleared.
6. Sign in or activate the receiver using Mago Cloud.

Depending on the device, authentication may use:

* Device password
* PIN
* Fingerprint
* Face recognition
* Another supported device-authentication method

Device authentication protects the server setting from unauthorized changes.

### What happens when the environment changes

Changing the Mago Stage environment:

* Signs the current user out
* Clears the active server configuration
* Disconnects the device from the previous environment
* Requires the user to sign in again
* Requires receivers to be activated in the new environment
* Changes which organizations, users, receivers, Stages, policies, and licenses are available

Changing environments does not transfer data between Mago Cloud and a corporate server.

A Stage, user account, receiver activation, or license created in one environment is not automatically available in another environment.

### Controllers and receivers

A controller and receiver can connect only when both use the same Mago Stage environment.

If a receiver is missing from the controller:

1. Confirm the environment selected on the controller.
2. Confirm the environment selected on the receiver.
3. Confirm that the receiver is activated in that environment.
4. Confirm that both devices can reach the environment.
5. Confirm that the receiver is online.
6. Confirm that the organization permits access to the receiver.

### Troubleshooting

#### The corporate server does not load

Confirm that:

* The server address is correct.
* The address includes the required protocol.
* DNS resolves the server hostname.
* The device is connected to the required network or VPN.
* The server certificate is trusted.
* Required firewall and proxy rules are in place.
* The Mago Stage server is running.

#### Sign-in fails after changing servers

User accounts belong to a specific Mago Stage environment.

Confirm that:

* The account exists on the selected server.
* The correct sign-in method is being used.
* The organization has enabled the expected identity provider.
* The user has received an invitation or account from that environment.

#### A receiver requires activation again

Receiver activation belongs to the selected environment.

When a receiver changes from Mago Cloud to a corporate server, or from one corporate server to another, it must be activated in the new environment and may require an available display license.

#### The expected organization or Stage is missing

Organizations and Stages are not transferred between environments.

Return to the environment where the organization or Stage was created, or contact the organization administrator.


# Sign in to Mago Stage

Sign in using the method provided by your organization.

Available methods can include:

* Email address and password
* Microsoft single sign-on
* Google single sign-on
* Apple single sign-on
* Another identity provider configured by the organization
* Guest access for supported screen-sharing workflows

The options shown on the sign-in screen depend on the selected Mago Stage environment and organization configuration.

### Before signing in

Confirm that:

* The correct Mago Cloud or corporate-server environment is selected.
* The device can reach the required Mago Stage services.
* Your account exists in the selected environment.
* You are using the sign-in method specified by your administrator.
* The device date and time are correct.

Accounts are specific to an environment. An account created in Mago Cloud does not automatically exist on a corporate server.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FZjKLmjofsemYq5cxr9lf%2Fsign-in.png?alt=media&amp;token=d43ed341-479a-40b2-9477-22b257f42bb7" alt=""><figcaption></figcaption></figure>

### Sign in with an email address and password

Use this method when the organization has created a Mago Stage account for you.

1. Open Mago Stage.
2. Go to **Sign in**.
3. Enter your email address.
4. Enter the temporary or existing password supplied by the organization.
5. Select **Remember me** only when using your own trusted device.
6. Select **Sign In**.
7. Wait for Mago Stage to load your account.

Email addresses are not case-sensitive, but passwords are case-sensitive.

### Set a new password

Mago Stage may require you to set a new password during your first sign-in.

1. Sign in using the temporary password supplied by the organization.
2. When **Set new password** appears, enter a new password.
3. Enter the same password in **Confirm new password**.
4. Select **Update Password**.
5. Wait for Mago Stage to complete sign-in.

The password must contain at least eight characters.

If the password-change session expires, return to the sign-in screen and sign in again using the temporary or current password.

Follow any additional password requirements provided by the organization.

### Sign in with single sign-on

Use single sign-on when the organization has enabled an identity provider such as Microsoft, Google, or Apple.

1. Open Mago Stage.
2. Go to **Sign in**.
3. Select **Sign in with** followed by the provider name.
4. Complete the organization’s sign-in process in the browser window.
5. Complete multi-factor authentication when requested.
6. Approve the requested access when applicable.
7. Return to Mago Stage.
8. Wait for sign-in to complete automatically.

Only identity providers enabled for the selected Mago Stage environment appear on the sign-in screen.

The identity-provider account must be permitted to access the organization. Successfully signing in to Microsoft, Google, or Apple does not automatically grant access to Mago Stage.

### Continue as a guest

Select **Continue as Guest** when you need to use a supported guest screen-sharing workflow without signing in to a Mago Stage account.

Guest access is limited. It does not provide the complete controller experience and does not provide access to:

* Saved Stages
* Organization content
* Connected cloud accounts
* Administration features
* User-specific settings

Follow the on-screen instructions to start or join the supported sharing workflow.

### Remember me

Select **Remember me** only on a device that is:

* Assigned to you
* Protected by a password, PIN, or biometric authentication
* Managed according to the organization’s security policy
* Not shared with guests or unauthorized users

Do not select **Remember me** on public, shared, demonstration, or temporary devices.

Sign out when you finish using a shared device.

### Multiple organizations

A user may have access to more than one organization.

After signing in, select the organization containing the Stages, displays, licenses, and users you need to access.

If the expected organization is missing:

* Confirm that you used the correct account.
* Confirm that you selected the correct Mago Stage environment.
* Ask an organization administrator to verify your invitation and access.
* Sign out and sign in again after access has been updated.

### Terms of Service

The sign-in screen provides access to the Mago Terms of Service.

By continuing, users confirm that they have read and agree to the applicable terms.

### Troubleshooting

#### Authentication failed

Confirm that:

* The email address is correct.
* The password is correct.
* Caps Lock is not enabled unexpectedly.
* The account belongs to the selected environment.
* The account is active.
* The device has network access.
* The server date and time are correct.

If the problem continues, contact the organization administrator.

#### A single sign-on option is missing

The provider may not be enabled for the selected environment.

Confirm that:

* The correct Mago Stage environment is selected.
* The organization has configured the identity provider.
* The application can reach the identity provider.
* You are using a supported application or browser.

#### The browser does not open

Confirm that:

* The device has a default browser.
* Pop-up windows and external application links are allowed.
* Endpoint security is not blocking the browser.
* The identity-provider endpoints are allowed through the firewall or proxy.

#### Access is denied by the identity provider

The identity provider may be enforcing organization security policies.

Possible causes include:

* The user is not assigned to the application.
* Administrator consent has not been granted.
* Multi-factor authentication was not completed.
* Conditional Access blocked the device or location.
* The account belongs to another tenant.
* The organization does not permit third-party applications.

Contact the organization’s identity administrator.

#### A password must be changed again

The password-change session may have expired or the new password may not meet the required policy.

Return to **Sign in**, authenticate again, and repeat the password-change process.

#### The expected content is missing

Confirm that:

* The correct environment is selected.
* The correct account was used.
* The correct organization is selected.
* The account has permission to access the required content.

Content and access are not shared automatically between Mago Cloud and corporate-server environments.


# Connect a Microsoft 365 or Google account

Connect a Microsoft 365 or Google account to access supported cloud files, folders, profile information, and calendar features in Mago Stage.

The available providers and features depend on the selected Mago Stage environment and the organization’s configuration.

### Sign-in account and connected account

Signing in to Mago Stage and connecting a cloud account are separate actions.

Your Mago Stage sign-in determines:

* Your Mago Stage identity
* The organizations you can access
* Your roles and permissions
* The Stages and displays available to you

A connected Microsoft 365 or Google account provides access to supported external content and services.

Signing in with Microsoft or Google does not necessarily connect that account for cloud content. Complete the connected-account process when you want to access OneDrive, SharePoint, Google Drive, or supported calendar features.

### Before connecting an account

Confirm that:

* You are signed in to Mago Stage.
* The correct Mago Stage environment is selected.
* The organization has enabled the provider.
* Your Microsoft 365 or Google account permits third-party applications.
* Required administrator consent has been granted.
* The account can access the intended files and folders.
* Authentication pop-ups and redirects are permitted.

Organization security policies can prevent account linking even when the username and password are correct.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FsEZQi9APry7RhNAbfnYp%2Fconnected-accounts.png?alt=media&amp;token=d0c646b7-e38f-4442-b567-d1289cbc88ef" alt=""><figcaption></figcaption></figure>

### Connect a Microsoft 365 account

1. Open Mago Stage.
2. Open your user profile.
3. Find **Connected accounts**.
4. Find **Microsoft 365**.
5. Select **Connect**.
6. Sign in to the Microsoft account you want to use.
7. Complete multi-factor authentication when requested.
8. Review the requested permissions.
9. Approve access when permitted by your organization.
10. Return to Mago Stage.
11. Confirm that Microsoft 365 appears as connected.

After connection, supported Microsoft content can include:

* OneDrive files
* SharePoint files
* Microsoft profile information
* Supported Microsoft calendar features

The available content depends on Microsoft tenant policies and the user’s existing permissions.

### Connect a Google account

1. Open Mago Stage.
2. Open your user profile.
3. Find **Connected accounts**.
4. Find **Google**.
5. Select **Connect**.
6. Sign in to the Google account you want to use.
7. Complete additional authentication when requested.
8. Review the requested permissions.
9. Approve access when permitted by your organization.
10. Return to Mago Stage.
11. Confirm that Google appears as connected.

After connection, supported Google content can include:

* Google Drive files
* Google Drive folders
* Google profile information
* Supported Google Calendar features

The available content depends on Google Workspace policies and the user’s existing permissions.

### Permissions

Mago Stage requests permissions needed for the enabled integration.

Depending on the provider and features, permissions can include:

* Viewing basic profile information
* Viewing cloud files and folders
* Downloading selected content
* Viewing supported calendar information
* Maintaining access while the user is not actively signing in

Connecting an account does not grant Mago Stage access to content that the user cannot already access.

Do not approve permissions that conflict with the organization’s security policy. Contact the organization administrator when approval is unclear.

### Select the correct account

Use the account containing the files, folders, or calendars you need.

If several Microsoft or Google accounts are already signed in within the browser, carefully select the correct account during the connection process.

Before approving access, confirm:

* The displayed email address
* The organization or tenant
* The requested permissions
* Whether the account is personal or organization-managed

### Reconnect an account

A connected account may require reconnection when:

* The access token expires
* The user changes their password
* An administrator revokes consent
* Organization security policies change
* The provider requires authentication again
* The account is disabled or restored
* The connection has not been used for an extended period

To reconnect:

1. Open your user profile.
2. Find **Connected accounts**.
3. Find the affected provider.
4. Select **Reconnect**.
5. Complete authentication and consent.
6. Return to Mago Stage.
7. Confirm that the account appears as connected.
8. Test access to the required cloud content.

Reconnect uses the account selected during the new authentication process. Confirm that you reconnect the intended account.

### Disconnect an account

Disconnect an account when you no longer want Mago Stage to access it.

1. Open your user profile.
2. Find **Connected accounts**.
3. Find the connected provider.
4. Select **Disconnect**.
5. Confirm the action when requested.

Disconnecting an account prevents Mago Stage from retrieving new information from that account.

Content already uploaded or copied into Mago Stage may remain available according to the organization’s content, retention, and storage policies.

Disconnecting a cloud account does not delete the original files from Microsoft 365 or Google Drive.

### Organization and tenant restrictions

Cloud access can be restricted by:

* Microsoft Entra application-consent policies
* Microsoft Conditional Access
* Google Workspace OAuth controls
* Device-compliance requirements
* User or group assignments
* File-sharing restrictions
* Cross-tenant access policies
* External-user restrictions
* Shared-drive permissions
* Data-loss-prevention policies

A file may appear in the provider’s normal website but remain unavailable through Mago Stage because of an organization policy or unsupported content type.

### Troubleshooting

#### The provider is not shown

Confirm that:

* The correct Mago Stage environment is selected.
* The organization has enabled the provider.
* You are signed in to the correct organization.
* The provider configuration is complete.

Contact the Mago Stage administrator if the provider remains unavailable.

#### The browser does not open

Confirm that:

* A default browser is configured.
* Pop-up windows are allowed.
* External application links are permitted.
* Endpoint security is not blocking the browser.
* The provider’s authentication endpoints are allowed.

#### Administrator approval is required

The organization may require an identity administrator to approve the application or requested permissions.

Do not attempt to bypass the approval process. Send the displayed request or error information to the organization’s Microsoft Entra or Google Workspace administrator.

#### The wrong account was connected

1. Disconnect the account in Mago Stage.
2. Sign out of the incorrect account in the browser when necessary.
3. Start the connection process again.
4. Select the intended account.
5. Confirm the email address before approving access.

#### Files or folders are missing

Confirm that:

* The connected account can access the content.
* The content is shared with the correct account.
* The file is not restricted by organization policy.
* The correct tenant or Google Workspace organization was selected.
* The content type is supported.
* The account connection has not expired.

#### Access has expired

Select **Reconnect**, complete authentication again, and retest the content.

If reconnection continues to fail, an administrator may need to renew consent or review the provider configuration.


# Activate a receiver

A receiver must be activated before controllers can connect to it.

Activation registers the receiver with an organization and creates its display record in the Administration Portal. This is normally completed once when the receiver is first installed or moved to a different Mago Stage environment.

### Who can activate a receiver

Activation requires a user with permission to manage displays in the Administration Portal.

If you do not have this permission, leave the activation code visible and give it to the appropriate administrator.

### Before activation

Confirm that:

* Mago Stage is installed as a receiver.
* The receiver is connected to the correct Mago Stage environment.
* The receiver has a working network connection.
* The administrator can access the Administration Portal.
* The correct organization is selected in the Portal.
* An appropriate display license is available when required.

See **Select the Mago Stage environment** if the receiver is connected to the wrong server.

### Get the activation code

1. Open Mago Stage on the receiver.
2. Wait while the receiver connects to the selected environment.
3. Leave the activation screen open.
4. Note the six-character activation code shown on the display.

The activation code can contain uppercase letters and numbers.

Use the code currently shown by the receiver. If the receiver generates a new code, the previous code may no longer be accepted.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FR1DWeW2fs9Iob63SPNWQ%2Fimage.png?alt=media&amp;token=8e936897-106b-470f-bec9-8d63540c2758" alt=""><figcaption></figcaption></figure>

### Activate the receiver in the Administration Portal

1. Sign in to the Mago Stage Administration Portal.
2. Select the correct organization.
3. Select **Displays**.
4. Select **Activate**.
5. Under **Enter activation code**, enter the six-character code shown by the receiver.&#x20;

   <figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2Fuq3DUGGOgAl1UljpZmGf%2Fimage.png?alt=media&amp;token=32050ee7-70fb-479c-98ed-feea0b7c6bb1" alt=""><figcaption></figcaption></figure>
6. Select **Continue**.
7. Assign an available display license when the Portal requests one.&#x20;

   <figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FYt3riizRTzegdHklsNzg%2Fimage.png?alt=media&amp;token=c9c9961a-a5c3-4299-8b0d-83b4a54e9d72" alt=""><figcaption></figcaption></figure>
8. Select **Activate Display**.
9. Enter a name that identifies the display’s location or purpose.&#x20;

   <figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2Fa0waUlKHqfErMHMOcD5E%2Fimage.png?alt=media&amp;token=473fc42b-2e89-4e57-8350-fa4415f2b726" alt=""><figcaption></figcaption></figure>
10. Select **Continue**.

Example display names include:

* Boardroom Display
* Reception Screen
* Training Room
* Showroom Left Display

You can select **Skip** when the existing or automatically assigned name is suitable.

When **Display activated** appears, select **Finish**.

### Confirm activation

After activation:

* The new display appears under **Displays** in the Administration Portal.
* The receiver checks its activation status automatically.
* The receiver leaves the activation screen.
* The receiver displays its controller connection screen.
* Controllers can connect using the displayed QR code or connection code.

Leave the receiver online while it checks for approval.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FTjWh6hsc5mfr7Pyx4gnu%2Fimage.png?alt=media&amp;token=d7eb1aad-feb8-4a1f-ad07-add09d14895a" alt=""><figcaption></figcaption></figure>

### If no display license is available

If the Portal reports that no display seats are available, the organization does not have a suitable active license with available capacity.

An administrator must review the organization’s licenses and assignments before activation can continue.

Do not assume that deleting a display automatically releases its license assignment. Review the license and assignment status in the Administration Portal.

After capacity becomes available:

1. Return to **Displays**.
2. Select **Activate**.
3. Enter the receiver’s current activation code.
4. Repeat the activation process.

### Move a receiver to another environment

Receiver activation belongs to a specific Mago Stage environment.

If the receiver is moved from Mago Cloud to an on-premises environment, or between corporate servers:

1. Select the new environment on the receiver.
2. Wait for the receiver to display a new activation code.
3. Activate the receiver in the new environment’s Administration Portal.
4. Assign a license when required.

Activation records and licenses are not transferred automatically between environments.

### Troubleshooting

#### The activation code is rejected

Confirm that:

* All six characters were entered correctly.
* The receiver is still displaying the same code.
* The receiver and Portal use the same Mago Stage environment.
* The correct organization is selected.

If the receiver displays a new code, use the new code.

#### Activate is unavailable

Confirm that:

* Your account has permission to manage displays.
* The correct organization is selected.
* The server license is active for an on-premises deployment.
* The Portal is not restricted by an unresolved licensing warning.

#### No display seats are available

Ask an administrator to review:

* Active display licenses
* License expiration
* Available capacity
* Existing display assignments
* Deleted-receiver assignments that may still count toward license totals

Return to activation after suitable capacity is available.

#### The display is already assigned

The receiver may already be associated with another organization or license assignment.

An administrator must review and resolve the existing assignment before the receiver can be activated elsewhere.

#### The receiver remains on the activation screen

Confirm that:

* The receiver remains online.
* The receiver and Portal use the same environment.
* The activation completed successfully in the Portal.
* The receiver can reach the Mago Stage API.
* The system date and time are correct.

Wait briefly for the automatic activation check. If the receiver does not continue, restart the application and confirm its environment again.

#### The receiver shows a server error

Confirm that the correct environment is selected. If the receiver uses a corporate server, ask the administrator to verify that the server is running and reachable.


# Connect a controller to a receiver

Connect a controller to a receiver before sending or presenting content.

An activated receiver can display:

* A QR code
* A six-character connection code
* Its availability in the controller’s display list
* Its membership in an available receiver group

The options shown on the controller depend on the organization, license, device, and selected Mago Stage environment.

### Before connecting

Confirm that:

* The receiver has been activated.
* The controller and receiver use the same Mago Stage environment.
* Both devices are online.
* The receiver is showing its connection screen.
* The controller has permission to access the receiver.
* The organization’s license allows another connection.

See **Activate a receiver** if the receiver is still showing an activation code.

### Connect using a QR code

1. Open Mago Stage on the controller.
2. Open the display connection control.
3. Select **Scan QR code**.
4. Allow camera access when requested.
5. Point the controller’s camera at the QR code shown on the receiver.
6. Keep the complete QR code visible within the scanner.
7. Wait for the connection to complete.

After connection, the receiver’s name appears in the controller’s connected-display controls.

If camera access was previously denied, enable it in the device’s operating-system settings before trying again.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2Ft7LWFe0Wgp58iBtWbBEu%2Fimage.png?alt=media&amp;token=38b30205-74dc-4be4-a521-7155d4785850" alt=""><figcaption></figcaption></figure>

### Connect using a connection code

1. Open Mago Stage on the controller.
2. Open the display connection control.
3. Select **Enter code**.
4. Enter the six-character code shown on the receiver.
5. Confirm the code.
6. Wait for the connection to complete.

Spaces and hyphens in the entered code are ignored.

Use the code currently shown on the receiver. If the receiver displays a new code, the previous code may no longer work.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FckpT80RNeoZKwvypfTyc%2Fimage.png?alt=media&amp;token=a3458423-31f6-4565-ae67-1e2759b92b72" alt=""><figcaption></figcaption></figure>

### Connect from the display list

When permitted by the organization, the connection dialog lists receivers available to the signed-in user.

1. Open the display connection control.
2. Find the receiver under **Displays**.
3. Select the receiver.
4. Wait for the connection to complete.

If the receiver is not listed, use its QR code or connection code, or ask an administrator to confirm your access.

On iPhone and iPad, Mago Stage may require Local Network permission to find displays on the current network.

### Connect to a receiver group

Receiver groups allow several receivers to be selected together.

1. Open the display connection control.
2. Open **Groups**.
3. Select the required group.
4. Wait while Mago Stage connects to the available receivers.

A group may be unavailable when:

* It has no active receivers.
* Its receivers are offline.
* The user does not have access to the group.
* The organization’s license does not permit the requested connection.
* The group belongs to another Mago Stage environment.

Group size and receiver limits are covered under **Product limits**.

### Connect an additional receiver

To connect another receiver while a Stage is open:

1. Select the connected-display control in the Stage header.
2. Select **Connect a display**.
3. Select an available receiver or group, scan a QR code, or enter a connection code.
4. Wait for the additional connection to complete.
5. Repeat when the organization’s license and device allow more connections.

Phone-sized controllers can connect to a maximum of two displays during a session. Other limits can depend on the organization’s license and configuration.

### Disconnect receivers

To disconnect one or more receivers:

1. Open the connected-display control.
2. Select the receiver you want to disconnect, or choose the applicable disconnect action.
3. Select **Disconnect displays** or **Disconnect all** when required.
4. Confirm that the disconnected receiver returns to its connection screen.

Disconnecting a receiver does not:

* Deactivate it
* Remove it from the organization
* Delete its display record
* Remove its license assignment

It only ends the active controller connection.

### Troubleshooting

#### The connection code is rejected

Confirm that:

* All six characters were entered correctly.
* The receiver is still showing the same code.
* The controller and receiver use the same environment.
* The receiver has been activated.
* The receiver is online.

If the receiver shows a new code, use the new code.

#### The QR code does not scan

Confirm that:

* Camera permission is enabled.
* The complete QR code is visible.
* The camera lens is clean.
* The receiver screen is bright enough.
* Glare is not obscuring the code.
* The controller is held steadily.

Use **Enter code** if scanning remains unsuccessful.

#### The receiver is not listed

Confirm that:

* The receiver is online.
* The receiver is activated.
* The correct organization is selected.
* The controller has access to the receiver.
* Both devices use the same environment.
* Local Network permission is enabled on iPhone or iPad.

You can still connect using the QR code or connection code when permitted.

#### No displays in the group are online

The group exists, but none of its receivers are currently available.

Check the receivers’ power, application status, network connections, and selected environments.

#### The controller remains on Connecting

Confirm that:

* Both devices can reach the Mago Stage service.
* HTTPS and secure WebSocket connections are allowed.
* The receiver remains on its connection screen.
* The device date and time are correct.
* The organization’s connection limit has not been reached.

Cancel the attempt and try again after checking connectivity.

#### The connection limit has been reached

Disconnect an unused receiver and try again.

If the limit does not match the expected organization capacity, ask an administrator to review the applicable license and receiver assignments.

#### The receiver disconnects repeatedly

Check:

* Network stability
* Wi-Fi signal quality
* Proxy WebSocket timeouts
* Device sleep settings
* Application updates
* Server availability

Use wired Ethernet for fixed receivers where practical.


# User Guide

This guide explains how to create a stage, connect to a display, add content, configure layouts, present information, and manage presentation modes.

#### Get started

Follow these guides in order when setting up a presentation:

1. **Connect a controller to a receiver**
2. **Create and manage Stages**
3. **Add content to a Stage**
4. **Arrange content on a Stage**
5. **Start a presentation mode**

#### Present and control content

Use the applicable guide when you need to:

* Control content during a session
* Change the Stage layout
* Share a screen
* Use Player or Showroom mode
* Disconnect from a receiver

#### Content and service limits

Refer to the supporting pages for:

* Supported file formats and limits
* Cloud Drive refresh behavior
* Cloud tenant and sharing restrictions
* License limits for displays and receiver groups

The available features depend on the controller platform, receiver platform, active license, connected accounts, and organization configuration.


# Create and open a Stage

### Create a Stage

1. Open **Mago Stage**.
2. On the **Stages** screen, select **Create a Stage**.
3. Enter a name for the Stage. The name must contain at least three characters.
4. Optionally, configure either of the following:
   * Select **Create from Drive** to create the Stage from a connected Microsoft 365 or Google account.
   * Select **Tap to select image** to add a cover image.
5. Select **Create**.

The new Stage is added to the **Stages** screen.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FzFeAVYWoCgVrvDzIdi2l%2Fimage.png?alt=media&amp;token=0ac56d2e-84db-4745-beaf-fe75cefd021a" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
A Stage created from a cloud folder cannot be edited directly in Mago Stage. Update the source folder and refresh the Stage to synchronize supported files. Subfolders are not included.

For more information, see **Use cloud folders.**
{% endhint %}

### Find and open a Stage

Existing Stages appear on the **Stages** screen, with recently updated Stages shown first.

To open a Stage:

1. Locate the Stage you want to use.
2. Select its Stage card.

Use the search field to find a Stage by name when it does not appear in the visible list.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FDAlcn344kIPlwomYKZdJ%2Fimage.png?alt=media&amp;token=ff637817-043c-4607-8ec3-7cdabcfabf8f" alt=""><figcaption></figcaption></figure>

### Change a Stage

Press and hold the Stage card, then select **Settings**.

From **Stage settings**, you can:

* Rename the Stage.
* Change available Stage settings.
* Remove the Stage.

The available options may depend on how the Stage was created.

### Remove a Stage

1. Press and hold the Stage card.
2. Select **Settings**.
3. Under **Danger Zone**, select **Remove**.
4. Confirm that you want to remove the Stage.

{% hint style="info" %}
Removing a Stage is permanent. It may also remove access to content stored only within that Stage. Confirm that any required content is stored elsewhere before removing it.
{% endhint %}


# Add content to a Stage

You can add files, images, notes, websites, videos, cloud content, and live sources to a Stage.

### Open the content menu

1. Open the required Stage.
2. Select the **+** button.
3. Select the type of content you want to add.

The available choices depend on the controller platform, connected accounts, licenses, server configuration, and device capabilities.

| Content option          | Use it for                                                                |
| ----------------------- | ------------------------------------------------------------------------- |
| **Camera**              | Capture a new photo using the controller camera.                          |
| **Photo library**       | Add one or more images stored on the controller.                          |
| **Files**               | Add a supported document, image, video, or 3D model from the controller.  |
| **Scan document**       | Capture a paper document using the device camera.                         |
| **Note**                | Add a simple note to the Stage.                                           |
| **Web page**            | Display a website using its address.                                      |
| **YouTube**             | Add a YouTube video using its URL.                                        |
| **Mago Share**          | Add a live screen-sharing source.                                         |
| **Mago Remote**         | Display and interact with a configured Mago Remote Agent.                 |
| **SharePoint/OneDrive** | Select files or supported folders from a connected Microsoft 365 account. |
| **Google Drive**        | Select files or supported folders from a connected Google account.        |

{% hint style="info" %}
Camera and document scanning require a compatible camera. Mago Remote requires an available and licensed Mago Remote Agent.
{% endhint %}

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F22Gkj7lMxeSH4p31Q8Cd%2Fimage.png?alt=media&amp;token=876a292f-c055-46f1-952e-e00f22d8ab79" alt=""><figcaption></figcaption></figure>

For the complete list of supported formats, see **Supported file formats and limits**.

### Put content on the Stage

After adding or selecting content, it appears in the content drawer at the bottom of the Stage.

To place it on the active layout:

1. Select the content item in the drawer.
2. Select **Add to Stage**.

Where drag-and-drop is supported, you can drag the item directly from the drawer into an available grid cell.

Repeat these steps for each item you want to display. Content can remain in the drawer for later use without appearing in the active layout.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FLCrBJyGkF9gOq6RH8kPK%2Fimage.png?alt=media&amp;token=d40a32bb-c969-40f8-8477-f90503b0d7b4" alt=""><figcaption></figcaption></figure>

### Add files from cloud storage

Before adding cloud files, connect the appropriate Microsoft 365 or Google account from your profile.

1. Open the Stage.
2. Select the **+** button.
3. Select **SharePoint/OneDrive** or **Google Drive**.
4. Browse to the required location.
5. Select the files or supported folder you want to add.
6. Confirm your selection.
7. Add the resulting content items to the Stage layout.

If prompted, complete the account connection or reconnection process in the browser.

For folder synchronization and refresh behavior, see **Use cloud folders**.

### Arrange the Stage layout

Use the layout selector in the upper-right corner to choose how many cells appear on the Stage.

Available layouts can include:

* **1 element**
* **2 elements**
* **4 elements**
* **6 elements**
* **Custom**

Drag content between cells to rearrange the layout. Select **Custom** when you need a custom arrangement and the option is available.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FLztnbswMdyEMLsjoA7RX%2Fimage.png?alt=media&amp;token=cf426d85-f797-4485-bd14-4100b41cdbd8" alt=""><figcaption></figcaption></figure>

### Manage a content item

Select or press and hold a content item to open its available options.

Depending on the content type, you can:

* Add the item to the Stage.
* Set or change its thumbnail.
* Remove it from the Stage.
* Delete it from the content drawer.

{% hint style="danger" %}
Deleting an item from the content drawer may remove it from the Stage completely. Confirm that the content is no longer required before deleting it.
{% endhint %}


# Control content during a session

When you select content on the Stage, Mago Stage displays controls that are appropriate for that content type. The available controls can vary by platform, receiver, and content source.

### Select content to control

1. Open the Stage.
2. Select the content item you want to control.
3. Use the controls that appear over or near the selected item.

Only the selected item receives commands from its content controls.

### Available controls

| Content type         | Available actions                                                                           |
| -------------------- | ------------------------------------------------------------------------------------------- |
| **Images**           | Move between images in a collection and adjust the view where available.                    |
| **PDF documents**    | Move between pages and change the page view.                                                |
| **Videos**           | Play, pause, seek, and use the available playback controls.                                 |
| **YouTube videos**   | Play, pause, seek, and use the available YouTube playback controls.                         |
| **Web pages**        | Navigate backward or forward, refresh the page, interact with the page, or stop loading it. |
| **3D models**        | Rotate or adjust the model and, on supported devices, open an augmented-reality view.       |
| **Magic annotation** | Draw, highlight, erase, and use the available annotation tools.                             |
| **Mago Remote**      | Select a remote screen and use the available remote-input controls.                         |

### Control a web page

When a web page is selected, its floating controls can include:

* Expand or fit the page.
* Navigate backward.
* Navigate forward.
* Refresh the page.
* Enter or exit interaction mode.
* Stop loading the page.

Some websites prevent their content from being embedded or restrict interaction when displayed inside another application. If a website does not load correctly, open it directly in a supported browser to confirm that it is available.

### Control the volume

Use the volume control in the Stage header when it is available.

Volume control depends on the connected receiver, its operating system, and the content currently being displayed. If no audio is heard, also check the receiver’s system volume and mute setting.

### Move between content items

Select a different item in the Stage layout to display its controls. The controls change automatically to match the newly selected content.

To change the layout or move content between cells, see **Add content to a Stage**.


# Start a presentation mode

When your Stage is ready, start a presentation mode to display and control its content.  If you are presenting on another display, connect the controller to the required receiver before starting.

### Choose a presentation mode

Mago Stage provides two presentation modes:

| Mode              | Use it for                                                                                                   |
| ----------------- | ------------------------------------------------------------------------------------------------------------ |
| **Player mode**   | Normal presentations where you want access to the available content and playback controls.                   |
| **Showroom mode** | A cleaner, simplified presentation experience for showrooms, demonstrations, events, or unattended displays. |

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F8Tf70KR68GcteUoljAxt%2Fimage.png?alt=media&amp;token=22bf7c9a-94a3-49f2-b7d9-67a049130bcb" alt=""><figcaption></figcaption></figure>

### Start presenting

1. Open the required Stage.
2. Confirm that the correct content and layout are displayed.
3. Select the **Play** button in the Stage header.
4. Select **Start Player mode** or **Start Showroom mode**.
5. Present or interact with the Stage content.

For information about the controls available for each content type, see **Control content during a session**.

#### Exit presentation mode

Select the red **Stop** button in the upper-left corner of the presentation interface.

On supported native devices, Mago Stage may ask you to authenticate using the device password, PIN, fingerprint, or facial recognition before returning to the Stage editing view.

The web controller returns to the Stage editing view without requesting device authentication.

Exit presentation mode before changing the Stage layout or adding or removing content.

{% hint style="info" %}
The controls available during a presentation can vary depending on the selected mode, controller platform, receiver, and content type.
{% endhint %}


# Share your screen

Use Screen Share to present a screen or application window without first adding it to a saved Stage.

### Before you begin

Confirm that:

* The receiver is powered on, activated, and online.
* The controller can connect to the receiver.
* Screen-recording or screen-capture permission is enabled.
* Confidential applications and notifications are closed or hidden.

For connection instructions, see **Connect a controller to a receiver**.

### Start a new screen share

1. On the main Mago Stage screen, find **Share your screen**.
2. Select **Screen Share**.
3. Select **Start Sharing**.
4. Connect to a receiver if one is not already connected.
5. On desktop systems, select the screen or application window you want to share.
6. Approve the operating-system or browser permission request if it appears.
7. Wait for the selected screen to appear on the receiver.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FJjY4BAh2WLxqR2Sjpeer%2Fimage.png?alt=media&amp;token=02d6e02a-f9e3-4000-bfcf-ca85105750ac" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Only share a screen or window that is safe for the audience to see. Close confidential applications and disable visible notifications before starting.
{% endhint %}

### Join an existing share

1. Select **Screen Share**.
2. Select **Join existing share**.
3. Follow the on-screen connection instructions.

### Join a Mago Room

1. Select **Screen Share**.
2. Select **Join Mago Room**.
3. Follow the room connection instructions shown on screen.

The available options depend on your organization’s Mago Stage configuration and enabled services.

### Share audio

Audio-sharing support depends on the controller’s operating system, browser, and selected source.

If audio is required:

* Select a source that supports audio sharing.
* Enable the audio-sharing option when prompted.
* Confirm that the receiver is not muted.
* Check the receiver’s system volume.

### Stop sharing

1. Select the stop-sharing control in Mago Stage or in the operating system’s sharing indicator.
2. Confirm that sharing has stopped.
3. Disconnect from the receiver when the session is finished.

Confirm that the receiver has returned to its expected connection or idle screen before leaving the room.


# Supported file formats and size limits

Mago Stage supports common images, documents, videos, and 3D models. Availability can vary by controller platform, receiver platform, connected cloud provider, and server configuration.

### Supported file formats

| Content type               | Supported formats                                                 |
| -------------------------- | ----------------------------------------------------------------- |
| **Images**                 | JPG, JPEG, PNG, WebP, BMP, HEIC, and HEIF                         |
| **Documents**              | PDF                                                               |
| **Microsoft Office files** | PPTX, DOCX, XLSX, and CSV                                         |
| **Videos**                 | MP4, MOV, and MKV                                                 |
| **3D models**              | GLTF and GLB                                                      |
| **Additional cloud files** | DOC, PPT, XLS, and RTF, where supported by the connected provider |

File extensions are not case-sensitive.

{% hint style="info" %}\
A supported file extension does not guarantee that every file will play correctly. Video playback also depends on the codecs supported by the receiver’s operating system.\
{% endhint %}

### File conversion

Some files are converted before they are displayed:

* PPTX, DOCX, XLSX, and CSV files are converted to PDF.
* HEIC and HEIF images are converted to JPEG.
* Google Docs, Sheets, Slides, and Drawings selected from Google Drive are exported as PDF.

The displayed result may differ slightly from the original application, particularly when a document uses unavailable fonts, animations, macros, or other application-specific features.

### Files added to a saved Stage

Mago Stage does not define a fixed per-file upload limit for content added to a saved Stage.

Uploads can still be limited by:

* The user’s available Mago Stage storage quota.
* Available server storage.
* Network speed and connection stability.
* Firewall or proxy restrictions.
* Web-server or reverse-proxy configuration.
* Limits applied by a connected cloud provider.

Cloud deployments can apply a per-user storage quota. On-premises deployments are unlimited by default unless the administrator configures a limit or the server runs out of available storage.

### Files shared through Present

The quick **Present file** workflow supports files up to approximately **30 MB**.

For larger files, add the content to a saved Stage or use an appropriate cloud-storage source.

### Cloud files

Cloud files remain subject to the permissions and limits of the connected Microsoft 365 or Google account.

For information about how cloud files are stored, refreshed, and synchronized, see **Cloud Drive refresh behavior**.


# Cloud Drive refresh behavior

Mago Stage can use files stored in Google Drive, OneDrive, and SharePoint. Cloud files remain in the connected cloud service and are retrieved when required.

Cloud files are stored in Mago Stage as references. They are not copied into normal Stage storage and do not count against the user’s Mago Stage storage quota.

#### Cloud references and stored copies

Content selected directly from Google Drive, OneDrive, or SharePoint remains linked to its source and is stored in Mago Stage as a reference.

Content that a user uploads separately or explicitly copies into Mago Stage is stored independently. Changes to the original cloud file do not automatically update a separately uploaded or copied item.

Google-native documents are exported to PDF when Mago Stage requests them for display. The generated PDF can be cached temporarily to improve performance, but it is not permanently copied into normal Mago Stage storage.

If the connected account is disconnected or loses access to the source, linked cloud content may stop loading or refreshing. Separately uploaded or copied content remains available according to the organization’s storage and retention policies.

### Individual cloud files

Files selected individually continue to reference the original cloud files.

When the content is loaded again, Mago Stage retrieves the latest accessible version. You do not normally need to remove and re-add the item after updating the original file.

If the original file is deleted or the connected account loses access, the Stage item may no longer load.

### Synced cloud folders

A folder selected from Google Drive, OneDrive, or SharePoint creates a synchronized content group.

The group includes supported files stored directly inside the selected folder. Nested subfolders are not synchronized recursively.

When the folder is refreshed, Mago Stage checks for:

* Newly added files.
* Removed files.
* Renamed files.
* Files that are no longer supported or accessible.

{% hint style="info" %}
A synchronized folder group is managed from its source folder. Add, rename, or remove files in the cloud folder, then refresh the group in Mago Stage.
{% endhint %}

### Stages created from Drive

A Stage created using **Create from Drive** remains linked to the selected cloud folder.

These Stages cannot be edited directly in Mago Stage. Update the source folder and refresh the Stage instead.

Mago Stage checks the linked folder when the Stage opens. Use the manual refresh option when you need to check for changes immediately.

### Refresh cloud content

To refresh synchronized content:

1. Open the Stage.
2. Open the content drawer.
3. Locate the synchronized folder group.
4. Select its refresh action.
5. Wait for Mago Stage to check the connected cloud folder.

If no changes are found, Mago Stage reports that the folder is up to date.

| Change in the cloud folder    | Result after refresh                                              |
| ----------------------------- | ----------------------------------------------------------------- |
| A supported file is added     | The file is added to the synchronized content.                    |
| A file is removed             | The corresponding cloud item is removed.                          |
| A file is renamed             | The displayed name is updated.                                    |
| A file’s contents are updated | The latest accessible version is retrieved when the item reloads. |
| An unsupported file is added  | The file is ignored.                                              |
| A nested subfolder is added   | Its contents are not synchronized recursively.                    |

### If refresh fails

If Mago Stage cannot refresh the folder:

1. Confirm that the controller is online.
2. Open your profile and check the connected account.
3. Select **Reconnect** if access has expired.
4. Confirm that the linked account can still open the folder and its files.
5. Return to the Stage and try refreshing again.

For account permissions, external sharing, and tenant restrictions, see **Cloud tenant and sharing restrictions**.


# Cloud tenant and sharing restrictions

Access to Google Drive, OneDrive, and SharePoint content follows the permissions of the account connected to Mago Stage.

A file or folder is available only when that connected account is permitted to access it.

### Supported cloud locations

Depending on the connected account and organization policies, Mago Stage can access:

| Provider          | Available locations                                           |
| ----------------- | ------------------------------------------------------------- |
| **Google Drive**  | My Drive, Shared with me, and accessible shared drives        |
| **Microsoft 365** | OneDrive, accessible SharePoint sites, and document libraries |

The locations shown in Mago Stage may be more limited than those visible in the provider’s own application.

### Account used for cloud content

Cloud content is accessed using the account connected by the user who added the content to the Stage.

The receiver does not require its own Google or Microsoft 365 account. It displays the content using the cloud reference associated with the Stage.

{% hint style="warning" %}\
Only add cloud content that the intended audience is permitted to view. Displaying content through Mago Stage does not replace your organization’s information-sharing and privacy policies.\
{% endhint %}

### Microsoft 365 restrictions

Microsoft 365 administrators can restrict access to OneDrive and SharePoint through tenant policies and application-consent settings.

The following restrictions may apply:

* Administrator approval may be required before users can connect their accounts.
* SharePoint access may require additional permissions.
* Some SharePoint sites or document libraries may be hidden.
* OneDrive may remain available even when SharePoint access is restricted.
* Conditional Access policies may require additional authentication.
* External or guest content may be blocked by tenant policy.

If SharePoint locations are missing, contact the organization’s Microsoft 365 administrator.

### Google Drive restrictions

Google Workspace administrators can restrict application access and sharing.

The following restrictions may apply:

* Administrator approval may be required before users can connect their accounts.
* Shared drives appear only when the connected account is a permitted member.
* Files under **Shared with me** remain subject to the owner’s sharing settings.
* External files may be blocked by the organization’s Google Workspace policies.
* Access can be removed by the file owner or administrator at any time.

### Cross-organization sharing

Content shared between different organizations works only when:

* The file owner allows external sharing.
* The connected account has permission to open the file.
* Both organizations permit cross-tenant or external access.
* The Mago Stage cloud application has the required permissions.
* Any required administrator consent has been granted.

A file that opens for one user may not be available to another user connected with a different account.

### Changes that can interrupt access

Existing Stage content can become unavailable when:

* The connected account is disconnected.
* Account authorization or consent expires.
* The original file or folder is deleted.
* The file is moved to a restricted location.
* Sharing permissions are removed.
* The user leaves the organization.
* An administrator changes an access or application policy.

When access expires, open your Mago Stage profile and reconnect the affected account.

For synchronization and refresh instructions, see **Cloud Drive refresh behavior**.


# License limits for displays and receiver groups

The number and location of receivers that a controller can use depend on the active Mago Stage license.

A **physical receiver** is a device running Mago Stage in receiver mode. A receiver can also drive additional displays connected directly to that device when permitted by the active license.

#### Receiver and display limits

| License edition | Physical receivers per controller | Wired displays per receiver |
| --------------- | --------------------------------- | --------------------------- |
| **Basic**       | 1                                 | Up to 3                     |
| **Pro**         | Up to 9                           | 1                           |
| **Ultra**       | Up to 9                           | 1                           |
| **Cloud**       | Up to 9                           | 1                           |

The physical-receiver limit includes the primary receiver.

For example:

* **Basic** supports one physical receiver driving up to three wired displays.
* **Pro**, **Ultra**, and **Cloud** support one primary receiver and up to eight additional physical receivers.
* Each physical receiver used with Pro, Ultra, or Cloud supports one wired display.

{% hint style="info" %}
Actual availability also depends on the receiver hardware, operating system, graphics outputs, and display configuration.
{% endhint %}

#### Receiver location

| License edition | Supported receiver location                                            |
| --------------- | ---------------------------------------------------------------------- |
| **Basic**       | Mago Stage server and receiver running on the same Windows machine     |
| **Pro**         | Receivers available on the private network                             |
| **Ultra**       | Local or remote receivers, subject to server and network configuration |
| **Cloud**       | Local or remote receivers, subject to network configuration            |

Firewall rules, routing, and server configuration can still prevent a permitted receiver from connecting.

#### Receiver groups

A receiver group can contain up to **9 receivers** for mirrored presentations.

There is no separate configured limit on the number of receiver groups an organization can create.

When connecting to a receiver group:

* Offline receivers may be skipped.
* Unavailable receivers may be skipped.
* Receivers already connected to another controller may be skipped.
* The connection remains subject to the active license and network configuration.

Creating and managing receiver groups requires permission to manage receivers.

{% hint style="info" %}
The Basic edition is available on Windows only. It is not supported on macOS.
{% endhint %}

#### Cloud display seats

In a Cloud deployment, every activated physical receiver requires an available display seat.

Adding a receiver to a group does not provide a display seat and does not replace the receiver’s individual Cloud license assignment.

If no display seat is available, an administrator must claim or renew a suitable license or release an unused seat before activating another receiver.

For activation instructions, see **Activate a receiver**.


# Admin Portal


# Administration Portal overview

The Mago Stage Administration Portal is used to configure and manage a Mago Stage environment.

The pages and actions you can access depend on your assigned administrative roles.

### What you can manage

Depending on your permissions, you can use the portal to:

* Activate and manage receiver displays.
* Activate and manage Mago Remote Agents.
* Claim and monitor display and Agent licenses.
* Organize resources using tags and groups.
* Apply display settings and policies.
* Configure supported sign-in providers and server services.
* Create digital-signage playlists.
* Invite users and assign administrative roles.
* Review user sessions and audit history.
* Download Mago Stage applications.
* Activate and maintain an on-premises server license.

### Portal navigation

The navigation menu can include the following areas:

| Area                                      | Purpose                                                                   |
| ----------------------------------------- | ------------------------------------------------------------------------- |
| **Displays**                              | Activate, view, edit, update, control, and remove receiver displays.      |
| **Agents**                                | Activate, share, update, remotely control, and remove Mago Remote Agents. |
| **Tags**                                  | Create reusable labels for displays and Agents.                           |
| **Digital Signage**                       | Create playlists and manage signage content.                              |
| **Assignment → Tag-based Assignment**     | Create tag-based resource groups and assign policies.                     |
| **Assignment → Display-based Assignment** | Create groups from selected displays and assign policies.                 |
| **Policies**                              | Create application policies and configure permitted services.             |
| **Licenses**                              | Claim and review Cloud Display and Remote Agent licenses.                 |
| **Downloads**                             | Download available controller, receiver, and Agent installers.            |
| **Profile**                               | Manage your profile and access organization-administration pages.         |

Only areas permitted by your administrative roles appear in the navigation.

### Selected organization

The portal manages resources belonging to the organization selected at the top of the navigation sidebar.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F0XpHqVJY23TlqWMlieQ1%2Fimage.png?alt=media&amp;token=b56bafd2-59d6-4316-8e2b-1149c61bc104" alt=""><figcaption></figcaption></figure>

Before making a change:

1. Open the organization selector.
2. Select the required organization.
3. Confirm that the correct organization name appears in the sidebar.
4. Wait for the current page to reload its organization-specific information.

The following resources are organization-specific:

* Licenses
* Displays
* Agents
* Groups and assignments
* Tags
* Users
* Policies
* Digital-signage content

{% hint style="warning" %}
Always confirm the selected organization before activating, assigning, changing, or deleting a resource.
{% endhint %}

### Access requirements

You need:

* The portal address for the correct Mago Stage environment.
* A valid user account or approved single sign-on provider.
* Access to the required organization.
* An administrative role with the necessary permissions.

On an on-premises installation without an active server license, authorized users may be directed to the server-license page before other Mago Stage services can be managed.


# Roles and permissions

The Administration Portal is permission-driven. Users see only the pages and actions allowed by their assigned administrative roles.

A user can have more than one administrative role. When multiple roles are assigned, their permissions are combined.

### Available roles

| Role                   | Typical access                                                                           |
| ---------------------- | ---------------------------------------------------------------------------------------- |
| **Owner**              | Unrestricted access to all portal functions.                                             |
| **Admin**              | Manages the organization, users, displays, Agents, signage, policies, and audit history. |
| **User Admin**         | Manages users within the organization.                                                   |
| **Organization Admin** | Manages organization details and structure.                                              |
| **Receiver Admin**     | Manages receivers, displays, and their related configuration.                            |
| **Agent Admin**        | Manages Mago Remote Agents.                                                              |
| **Signage Admin**      | Manages digital-signage playlists and content.                                           |
| **Policy Admin**       | Creates and manages policies.                                                            |
| **Support Admin**      | Accesses support functions and reviews audit history.                                    |
| **Read-only Admin**    | Views the Administration Portal and audit history without making changes.                |
| **Standard user**      | Uses Mago Stage without Administration Portal access.                                    |

The exact pages available can also depend on the deployment type and enabled services.

### Owner role

The **Owner** role has full access to the organization and its administrative configuration.

The Owner role cannot be changed or removed through normal user editing. This protects the organization from accidentally losing its primary administrative account.

{% hint style="warning" %}
Keep the Owner account secure and ensure that its recovery information remains current.
{% endhint %}

### Assign the minimum required access

Assign only the roles required for the user’s responsibilities.

For example:

* A help-desk user who manages receiver displays may need **Receiver Admin**.
* A content manager responsible for signage may need **Signage Admin**.
* A user who manages accounts may need **User Admin**.
* A user who needs both display and Agent access can have **Receiver Admin** and **Agent Admin**.

Avoid assigning **Admin** or **Owner** when a more limited role provides sufficient access.

### Missing pages or actions

If a page or action does not appear:

1. Confirm that the correct organization is selected.
2. Check the user’s assigned administrative roles.
3. Confirm that the required service is enabled for the deployment.
4. Ask the Owner or a User Admin to review the account.
5. For on-premises deployments, confirm that the server license is active.

If a user can sign in but has no permitted administration areas, the portal displays a no-access page.

For instructions on inviting users and assigning roles, see **Manage organization users**.


# Sign in to the Administration Portal

The Administration Portal supports organization-created accounts and configured single sign-on providers.

Use the portal address supplied by your organization. Cloud and on-premises environments can use different portal addresses and user directories.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FQqZMjmQCogm6EQY0J3lK%2Fimage.png?alt=media&amp;token=6469cc22-e3b4-456a-8f56-8f337639f35b" alt=""><figcaption></figcaption></figure>

### Sign in with an organization-created account

1. Open the Administration Portal.
2. Enter your email address.
3. Select **Continue**.
4. Enter your password.
5. Select **Continue**.

If you are signing in with an initial or temporary password, the portal may ask you to create a new password before continuing.

After authentication, the portal opens the first area permitted by your assigned role.

### Sign in with single sign-on

1. Open the Administration Portal.
2. Select the required provider, such as **Sign in with Microsoft** or **Sign in with Google**.
3. Complete your organization’s sign-in process.
4. Complete multi-factor authentication when requested.
5. Return to the portal if the browser does not return automatically.

Only providers configured for the selected Mago Stage environment appear on the sign-in page.

### If you cannot sign in

Confirm that:

* You are using the portal address for the correct Mago Stage environment.
* Your email address is entered correctly.
* Your account is active.
* The selected single sign-on provider is approved by your organization.
* Your browser permits the authentication page to open.
* Any required multi-factor authentication is completed.

If authentication succeeds but no administration pages are available, your account may not have an administrative role. Contact the organization Owner or a User Admin.

{% hint style="info" %}
On an unlicensed on-premises server, authorized administrators may be directed to the server-license page after signing in.
{% endhint %}


# Displays


# View and find displays

The Displays area lists the receivers registered to the selected organization.

You need display-management permission, such as the **Receiver Admin** role, to manage displays.

### Open the Displays area

1. Confirm that the correct organization is selected.
2. In the navigation menu, select **Displays**.

The page shows the displays belonging to the selected organization.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2Fq3i8WBh5yPTbHwmIp4qI%2Fimage.png?alt=media&amp;token=1ce3e570-353b-408f-9f40-d3164559aca9" alt=""><figcaption></figcaption></figure>

### Change the view

Use the view selector to switch between:

* **Grid** view
* **List** view

Changing the view does not affect the display configuration.

### Find a display

Use the search field to find a display by name.

Select **Filters** to narrow the list using the available display properties. Available filters can depend on the deployment and display information reported to the portal.

### Display information

The display list can show:

* Display name
* Device or platform type
* Assigned tags
* Online or offline status
* Installed application version or update state

Select a display row or card to open its details.

### Display status

A display’s status is based on its current connection to Mago Stage.

| Status      | Meaning                                                            |
| ----------- | ------------------------------------------------------------------ |
| **Online**  | The receiver is currently connected to the Mago Stage environment. |
| **Offline** | The receiver remains registered but is not currently connected.    |

An offline display can still appear in the portal and retain its configuration. Live commands and updates cannot be completed until it reconnects.

{% hint style="info" %}
A display appearing offline does not necessarily mean that it has been deleted or deactivated. Confirm that the receiver is powered on, connected to the network, and configured for the correct Mago Stage server.
{% endhint %}

### Activate another display

Select **Activate** to begin adding a receiver to the organization.

For the complete activation workflow, see **Activate a receiver**.


# View and edit display information

Open a display to review its reported device information and change its administrative details.

### Open a display

1. In the Administration Portal, select **Displays**.
2. Find the required display.
3. Select its row or card.
4. Select **Device info**.

The display details page contains separate areas for device information, software management, and policies.

### Review device information

The **Device info** page can show:

* Display name
* Current online or offline status
* Device identifier and activation information
* Operating system and platform details
* Installed software version
* Last-seen date and time
* Screen resolution or hardware information
* Assigned tags

The information available depends on the receiver platform and the details reported by the device.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F1ot2p9fx9hdyULNyiaDG%2Fimage.png?alt=media&amp;token=485a73ed-4b91-4af7-80ae-1c2c287d67c0" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Device information is reported by the receiver. Some fields may be unavailable while the receiver is offline or when the platform does not provide the information.
{% endhint %}

### Edit a display

1. Open the display.
2. Select **Edit**.
3. Change the required fields.
4. Select **Save Changes**.

Available fields can include:

| Field           | Purpose                                                                           |
| --------------- | --------------------------------------------------------------------------------- |
| **Name**        | Identifies the display in the portal and controller display lists.                |
| **Orientation** | Sets the intended display orientation.                                            |
| **Tags**        | Adds reusable labels used for organization, filtering, and tag-based assignments. |

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FyACngxQCVa3njdJgdg5j%2Fimage.png?alt=media&amp;token=b21dc2f4-0f38-40f8-a63f-e554c4ce528a" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The **Orientation** field sets the display-specific orientation used when no applicable policy supplies an orientation setting.&#x20;

When an effective Appearance policy supplies an orientation setting, the policy setting takes precedence. A policy assigned directly to the display overrides the corresponding setting inherited from a display-based or tag-based assignment.
{% endhint %}

### Display naming

Use a name that clearly identifies the display’s physical location or purpose.

Examples include:

* Boardroom Display
* Reception Screen
* Training Room 2
* Showroom North Wall

Avoid relying only on generic names or computer hostnames.

### Changing tags

Adding or removing a tag can change the display’s membership in a tag-based assignment.

This may cause policies associated with that assignment to be applied or removed. Review the relevant assignments before changing tags on a production display.

For more information, see **Manage tags** and **Tag-based assignments**.


# Manage display software and commands

Use the **Software** page to review the receiver application, send available updates, and issue remote commands.

The display must be online to receive commands and updates.

### Open the Software page

1. In the Administration Portal, select **Displays**.
2. Open the required display.
3. Select **Software**.

### Review software status

The page can show:

* Installed application version
* Application status
* Display usage status
* Available update
* Update history
* Command history

| Status            | Meaning                                                            |
| ----------------- | ------------------------------------------------------------------ |
| **App status**    | Indicates whether the Mago Stage application is currently running. |
| **Usage status**  | Indicates whether the display is idle or currently in use.         |
| **Update status** | Shows whether a managed update is available.                       |

Some status information may be unavailable when the display is offline or does not support the corresponding management feature.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2F8C1lhOw1fHXDazBOVkj4%2Fimage.png?alt=media&amp;token=c90cfffa-1d0c-44dc-a7da-72183396c447" alt=""><figcaption></figcaption></figure>

### Update the display

When a newer managed release is available:

1. Open the display’s **Software** page.
2. Review the installed and available versions.
3. Select **Push Update**.
4. Confirm the action if prompted.
5. Monitor **Update History**.
6. Confirm the installed version after the display reconnects.

{% hint style="warning" %}
Test application updates on a limited number of displays before deploying them more widely.
{% endhint %}

If the portal reports that update status is unavailable, confirm that the display platform supports managed updates and that the update service is configured correctly.

### Send application commands

The **Commands** area can include:

| Command            | Result                                                      |
| ------------------ | ----------------------------------------------------------- |
| **Start App**      | Starts the Mago Stage application on the display.           |
| **Stop App**       | Stops the Mago Stage application.                           |
| **Restart App**    | Stops and restarts the application.                         |
| **Remote Control** | Starts an authorized remote-control session when supported. |

Select the required command and confirm it when prompted.

### Verify command completion

A successful portal notification confirms that the command was sent. It does not always confirm that the action completed successfully on the receiver.

After sending a command:

1. Allow time for the receiver to process it.
2. Refresh the display status.
3. Review **Command History**.
4. Confirm the result on the physical display when possible.

If the command does not take effect, confirm that the receiver remains online and can communicate with the Mago Stage environment.

### Remote control

Use **Remote Control** only when:

* The display is online.
* Remote control is enabled for the deployment.
* Your account has the required permission.
* The session is authorized by your organization.

Remote sessions and administrative actions may be recorded in the audit history.


# Assign policies to a display

Use the Policy page to apply configuration directly to an individual display.

## Assign policies to a display

Use the **Policy** page to apply configuration directly to an individual display.

Policies can control supported display behavior, appearance, orientation, branding, signage, and other application settings.

### Open the Policy page

1. In the Administration Portal, select **Displays**.
2. Open the required display.
3. Select **Policy**.

The page shows policies assigned directly to that display.

Policies applied through display-based or tag-based assignments are managed from their corresponding assignment pages.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FTL0H13MyFbQxEwxdPg5L%2Fimage.png?alt=media&amp;token=10420700-70b6-45c4-86e6-b466915ccea7" alt=""><figcaption></figcaption></figure>

### Add a policy

1. Open the display’s **Policy** page.
2. Select **New**.
3. Choose whether to:
   * Create a new policy.
   * Select an existing reusable policy.
4. Select the required policy type.
5. Enter or select the policy name.
6. Configure the available settings when creating a policy.
7. Select **Add** or **Save**, as shown.

The available policy types and settings depend on the deployment and receiver platform.

{% hint style="info" %}
A policy assigned directly to a display can act as a display-specific override. Use group assignments when the same configuration must apply consistently to several displays.
{% endhint %}

### Review assigned policies

Select a policy from the list to review its settings.

Depending on your permissions, you can:

* Edit its available settings.
* Rename the policy.
* Remove it from the display.
* Delete the policy permanently.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FTXzS9oOK0ja71DzTjMQT%2Fimage.png?alt=media&amp;token=abf6a572-0c36-44e5-9d22-e4af852ffe6f" alt=""><figcaption></figcaption></figure>

### Remove or delete a policy

**Remove** and **Delete** have different results:

| Action     | Result                                                                              |
| ---------- | ----------------------------------------------------------------------------------- |
| **Remove** | Unassigns the policy from this display without deleting the reusable policy.        |
| **Delete** | Permanently deletes the policy and can affect every display or assignment using it. |

{% hint style="warning" %}
Use **Remove** when you only want to stop applying the policy to this display. Use **Delete** only when the policy is no longer required anywhere.
{% endhint %}

### Apply policy changes

After saving a policy change:

1. Confirm that the policy remains assigned to the intended display.
2. Allow time for the receiver to retrieve the new configuration.
3. Verify the result on the physical display.

An offline receiver retains its assignment but cannot apply new settings until it reconnects.

For instructions on creating and configuring reusable policies, see **Manage policies**.




---

[Next Page](https://kb.mago.io/llms-full.txt/1)

