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
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 for the list of certified Neat devices.
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 for instructions. The wireless touch controller tablet requires an active Wi-Fi internet connection.
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 requirements. Proxy connections are not supported.
Prepare wireless screen sharing
Mago Link allows any user to share their screen by visiting 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.
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.
Without this consent, devices will not be able to display room calendars or join meetings as authenticated participants.
Select your provider below and follow the setup steps.
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.
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.
Add the Mago application to your tenant
Open 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.
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 and sign in with a Microsoft 365 Administrator account.
Go to Microsoft Entra ID > Enterprise Applications (or search directly for "Enterprise Applications").
Under the Application list, search for "Mago" (Application ID
17781659-6867-4c77-9ba3-40670305181c).
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.
See Microsoft 365 for Advanced consent options and the full list of Required features and scopes.
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.
Mago is a Google OAuth verified application.
Authorize the Mago application
Open 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.
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).
If your domain restricts third-party application access, these prompts will be blocked with a 400 admin_policy_enforced error.
Check third-party app access policy
To check if your domain restricts third-party application access:
Open the Google Admin console
Go to Security > Access and data control > API controls
Click on Settings
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.
Pre-authorize the Mago application
If your domain restricts third-party application access:
Open the Google Admin console
Go to Security > Access and data control > API controls > Manage App Access
Click on "Configure new app"
Search for the following Mago app client IDs and add them as trusted app (one by one).
Mago app for display / web
436832489008-nl03st57foo9su4qg5mddnadhl7ql5oe.apps.googleusercontent.com
Mago mobile app for Android
436832489008-5ie2c8hme7jucfh4vn4hul7sdkm8mhuk.apps.googleusercontent.com
Mago mobile app for iOS
436832489008-l3lejr6nqvgmevau7u999gm6c17jdci2.apps.googleusercontent.com
Set your desired Scope and click Continue
Set the app as Trusted, then click Continue
Review and click Finish
Make sure to repeat the steps to configure all 3 Mago app client IDs.
This ensures that users and room resources are not blocked when Mago requests additional scopes (such as calendar access) during device activation or configuration.
See Google Workspace for the full list of Required features and scopes.
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
Google Workspace — create a service account for conference room calendars and configure resource delegation — see the full guide here: 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.
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 for the full procedure.
User Join (BYOM Authenticated Calls)
Regardless of the room configuration, User Join (BYOM Authenticated Calls) is always available.
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.
Guest Join (ID and Passcode)
Since March 2026, Zoom no longer allows unauthenticated participants to join meetings from room systems.
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 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 table.
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 table.
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 table.
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/
Sign in or Sign up to Mago Admin Center
If you do not already have an account, register at 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.
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 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.
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.
Last updated
Was this helpful?