Windows
It is recommended that agents use the default screen resolution on their device.
| DNS / URL | Port | Reason for Whitelisting |
|---|---|---|
api-us3.pusher.com | 443 | Trigger start/stop recording events |
wss://ws-us3.pusher.com | 443 | Trigger start/stop recording events |
http-intake.logs.datadoghq.com | 443 | Send app activity logs to Datadog |
prod-api.thelevel.ai | 443 | Level API authorization |
screen-case.thelevel.ai | 443 | Start/stop recording controls |
screen.thelevel.ai | 1935 | Stream recording to Level servers |
https://screen-app.thelevel.ai | 443 | Network health checks |
https://sr-releases.thelevel.ai | 443 | Auto-update downloads |
https://screen-app-v3.thelevel.ai | 443 | App UI |
https://launchdarkly.thelevel.ai | 443 | Feature flag configuration |
https://stream.launchdarkly.com | 443 | Feature flag streaming updates |
https://sdk.launchdarkly.com | 443 | Feature flag SDK access |
https://events.launchdarkly.com | 443 | Feature flag event reporting |
https://api.mixpanel.com | 443 | Analytics events |
https://api-eu.mixpanel.com | 443 | Analytics events |
https://api-in.mixpanel.com | 443 | Analytics events |
storage.googleapis.com | 443 | Update binary download storage |
fonts.googleapis.com | 443 | App UI fonts (Google Fonts) |
fonts.gstatic.com | 443 | App UI fonts (Google Fonts static assets) |
time.windows.com | UDP 123 | NTP time sync |
time.google.com | UDP 123 | NTP time sync |
time.cloudflare.com | UDP 123 | NTP time sync |
time.nist.gov | UDP 123 | NTP time sync |
NTP note: The NTP entries above require outbound UDP on port 123. All four are public time servers.
time.windows.comis typically already permitted in Windows environments because Windows uses it for system clock sync. Verify with your firewall team that outbound UDP 123 is not blocked.
[!NOTE] Are you evaluating the Level Screen Recorder for your organization? Read our dedicated Security Architecture & FAQ to understand how we secure updates, encrypt data, and accommodate EDR/Antivirus policies.
Complete every check with your security and endpoint team before Step 1. Resolve any No or Unsure answers, then generate a report for LevelAI.
Use the computer’s default screen resolution.
| Screens | Upload |
|---|---|
| 1 | 5 Mbps |
| 2 | 8 Mbps |
| 3 | 12 Mbps |
| 4 | 16 Mbps |
Allow outbound traffic from both the signed-in user's session and Windows services running as NT AUTHORITY\SYSTEM. Use DNS names rather than fixed IP addresses because LevelAI service endpoints and signed download URLs can change IP addresses.
| Destination | Port | Purpose |
|---|---|---|
screen-prod.thelevel.ai | TCP 443 | Main backend API for Level Screen Recorder and Watchdog |
screen.thelevel.ai | TCP 443 | Secure recording stream (RTMPS) |
screen-app-v3.thelevel.ai | TCP 443 | Level Screen Recorder user interface |
storage.googleapis.com | TCP 443 | Signed Watchdog and Screen Recorder MSI packages (Watchdog allowlists this host only) |
time.windows.com | UDP 123 | Time synchronization |
time.google.com | UDP 123 | Time synchronization fallback |
time.cloudflare.com | UDP 123 | Time synchronization fallback |
time.nist.gov | UDP 123 | Time synchronization fallback |
Add these destinations only if Agent Assist is enabled for your organization (you see both Screen Recording and Agent Assist in the app; see Step 3: Launch the App). If you use Screen Recording without Agent Assist, skip this table.
| Destination | Port | Purpose |
|---|---|---|
aa-auth.thelevel.ai | TCP 443 | Agent Assist authentication and session cookies |
agent-assist.web.app | TCP 443 | Agent Assist UI module (federated widget and assets) |
launchdarkly.thelevel.ai | TCP 443 | Agent Assist feature-flag configuration |
api-js.mixpanel.com | TCP 443 | Agent Assist analytics events |
events.launchdarkly.com | TCP 443 | Agent Assist feature-flag analytics events |
Important: Permit HTTPS redirects to the destinations listed above and do not require interactive proxy authentication. The Watchdog runs in Session 0 as
SYSTEM, so a proxy rule that works only after a user signs in will block enrollment and updates.
If your organization decrypts HTTPS traffic, place the corporate root CA in Local Computer → Trusted Root Certification Authorities. The Watchdog and Level Screen Recorder read trusted roots from the Windows certificate store. If inspection still blocks the connection, bypass inspection for LevelAI hostnames, storage.googleapis.com, and (when Agent Assist is enabled) the Agent Assist destinations above.
The NTP entries require outbound UDP 123. time.windows.com is normally already available on managed Windows devices. If UDP 123 is blocked, Level Screen Recorder uses HTTPS time through screen-prod.thelevel.ai; accurate Windows system time is still required for authentication and recording timestamps.
Install the Level AI Watchdog on every agent PC (shared desks included). IT deploys with Intune, SCCM, GPO, or elevated PowerShell as LocalSystem (Intune: Install behavior = System). The Watchdog installs Screen Recorder and handles updates. Agents do not run the installer.
Do not double-click the MSI. The wizard does not apply your organization name or enrollment token, so the device will not enroll with LevelAI.
TENANT= and TOKEN= from this page (Intune does not create TOKEN=).storage.googleapis.com, not from this builder.When you publish a new Watchdog build or change deployment settings, download the MSI again, click Generate, and update the install command in your tool.
The part before .thelevel.ai. The silent command uses this value as TENANT=. Confirm with your LevelAI contact if you are unsure.
Save the MSI and note its path on this PC if you will run the command locally (for example C:\Users\YourName\Downloads\LevelAIWatchdog-2.0.1.msi).
The generated command includes the MSI file name (must match what you upload), TENANT=, and TOKEN=. Run it as System or administrator. Do not change or drop TENANT= / TOKEN=.
Common failure: Uploading or assigning only the MSI. Always deploy the complete command from the builder.
/i, not a path from your admin PC).Example shape (your builder supplies the real token and file name):
msiexec.exe /i "LevelAIWatchdog-2.0.1.msi" /qn /norestart TENANT="your-org" TOKEN="…"
On a single PC, you may replace the MSI file name in the command with the full path where you saved the download, then run the command from an elevated PowerShell window. For SCCM or GPO, use the same TENANT= and TOKEN= values and point /i at the MSI in the deployment package.
Confirm the Watchdog is running:
Get-Service -Name LevelScreenRecorderWatchdog
The Watchdog then installs Screen Recorder and handles later updates on its own. It appears in Apps & Features and creates no shortcuts. Do not install the Level Screen Recorder app MSI yourself.
No admin rights required. The app installs silently in the background. It does not open the moment installation finishes.
To start it the first time, the agent restarts the computer and signs back in. The app then opens by itself. If they need it before a restart, they can open Level Screen Recorder once from the Start menu. After that first start, it opens on its own each time they sign in to Windows.
On first launch they enter their organization name (the part before .thelevel.ai), sign in with their account or SSO, and land on a simple status page showing whether recording is on or off.
Complete the matching items in the IT Admin Pre-Deployment Checklist first. The sections below are the configuration reference.
Ask the client's endpoint-security team to approve both the Watchdog (SYSTEM) and Level Screen Recorder (signed-in user) before deployment. A partial allowlist can leave the service installed but unable to enroll, download, install, or launch Level Screen Recorder.
Two contexts, not two people:
| Context | Who this is | Rights |
|---|---|---|
| Installer and Watchdog service | An administrator installs the MSI (Intune, SCCM, GPO, or PowerShell as Administrator). The Watchdog service then runs as LocalSystem, a built-in Windows account, not an IT login. | Admin is required only to install. The service then runs in the background with machine-level rights. |
| Signed-in user | The person using the PC. | Standard-user rights. No admin. Must not start, stop, or configure the Watchdog service. |
The installer and the Watchdog service must be allowed to:
LevelScreenRecorderWatchdog.msiexec.exe for Watchdog and Level Screen Recorder install, update, repair, and uninstall.HKLM\SOFTWARE\Level AI\Watchdog and the Watchdog and Level Screen Recorder folders under C:\Program Files\ and C:\ProgramData\.The signed-in user must be allowed to:
C:\Program Files\Level Screen Recorder\.%APPDATA%\Level Screen Recorder\, C:\ProgramData\Level Screen Recorder\, and %TEMP%.LevelScreenRecorder_Scheduler_<user-SID> scheduled task.Level Screen Recorder is managed by a separate Windows service, Level AI Watchdog. If a GPO, MDM baseline, EDR product, or service-control policy restricts third-party services, create an explicit exception with the following properties:
| Property | Value |
|---|---|
| Service display name | Level Screen Recorder Watchdog |
| Service name | LevelScreenRecorderWatchdog |
| Executable path | C:\Program Files\Level AI Watchdog\LevelScreenRecorderWatchdogSvc.exe |
| Account | NT AUTHORITY\SYSTEM (LocalSystem) |
| Startup type | Automatic |
| Recovery | Restart after service failure |
| Self-heal task | WdSvcAutoHeal, runs every minute as SYSTEM |
Required Administrator / IT Allowances:
SYSTEM context, to create and start LevelScreenRecorderWatchdog.LocalSystem. Do not apply a GPO or MDM policy that changes its startup type to Disabled or Manual.C:\Program Files\Level AI Watchdog\ to run as SYSTEM.WdSvcAutoHeal scheduled task to run as SYSTEM with highest privileges. This task restores the service after an unexpected graceful stop.C:\ProgramData\Level AI Watchdog\ and to run silent Windows Installer operations for Level Screen Recorder updates.Important: Do not grant end users permission to start, stop, configure, or log on as the service. The service is installed and controlled by Windows under
LocalSystem; Level Screen Recorder itself runs in the signed-in user's session with standard-user privileges.
To ensure smooth operation, you must configure your EDR/Antivirus solution.
Option A: Trusted Publisher Rule (Highly Recommended) Where policy permits, create a trusted-publisher rule for production files signed by Ujwal Inc (Level AI's code-signing publisher). This is the most secure and robust method.
Option B: Folder Whitelisting (Fallback) If publisher rules are not an option, you must explicitly exclude or allow the following installation and data folders:
C:\Program Files\Level AI Watchdog\
C:\ProgramData\Level AI Watchdog\
C:\Program Files\Level Screen Recorder\
C:\ProgramData\Level Screen Recorder\
And per user:
%APPDATA%\Level Screen Recorder\
Also permit MSI files staged under C:\ProgramData\Level AI Watchdog\Updates\. The Watchdog downloads and installs updates silently as SYSTEM; no UAC prompt is expected.
Minimum EDR Requirements At minimum, EDR must not:
LevelScreenRecorderProcessRunner.exe.msiexec.exe.WdSvcAutoHeal task.Option A: Publisher Rule (Recommended) Create publisher rules for Publisher: Ujwal Inc covering both product names, Level AI Watchdog and Level Screen Recorder, without restricting the rule to one current file version.
Option B: Path Rules (Fallback) If publisher rules are not available, use controlled path rules for:
%ProgramFiles%\Level AI Watchdog\*
%ProgramFiles%\Level Screen Recorder\*
Required Watchdog (SYSTEM) Operations:
Allow these operations:
%SystemRoot%\System32\msiexec.exe from the Watchdog service for silent lifecycle actions.%SystemRoot%\System32\schtasks.exe, %SystemRoot%\System32\taskkill.exe, and %SystemRoot%\System32\reg.exe for Watchdog maintenance and diagnostics.Level Screen Recorder normally uses its signed native process runner. If AppLocker, WDAC, EDR, or child-process rules block by parent process, allow these only when launched by Level Screen Recorder:
| Process | Purpose | Runs as |
|---|---|---|
LevelScreenRecorderProcessRunner.exe |
User identity, monitor detection, certificate and security diagnostics, scheduled-task operations | Signed-in user |
schtasks.exe |
Create/query/update the user's auto-launch task | Signed-in user |
reg.exe |
Read the user's Windows proxy settings | Signed-in user |
taskkill.exe |
Recover duplicate or unresponsive Level Screen Recorder processes | Signed-in user |
Blocking all fallback utilities does not grant a security boundary if the native helper remains allowed, but it reduces diagnostics and recovery. Prefer publisher and parent-child rules over broad path exclusions.
Apply all entries in Firewall Whitelisting, including for SYSTEM. For TLS inspection requirements, see HTTPS inspection.
Installation does not open the app. Restart the computer and sign in, and Level Screen Recorder opens on its own. Or open it once from the Start menu. After that first start, it opens on its own each time the agent signs in to Windows.
Note: Screenshots may look slightly different in your build.
Enter your organization name, the part before .thelevel.ai (ask your admin if you are unsure). Example for LevelAI: level.

Sign in with your account or SSO.

You should see a status page showing whether recording is on or off.
Screen Recording only (Agent Assist not enabled):
Screen Recording and Agent Assist (both enabled for your organization):
Optional. Apply this step when LevelAI has enabled live call audio for Agent Assist. Audio is captured by Level Screen Recorder. The CCaaS integration supplies the call session events that start and stop capture.
Complete Steps 1–3 and the When Agent Assist is enabled firewall table first. For the trigger-based model, CCaaS integration, testing cycle, headset and Windows communications-device configuration, microphone policy, network, and troubleshooting, see Agent Assist and call audio — rollout and capture setup.
The Level Screen Recorder v5 desktop application provides a modern, flexible interface designed to stay out of the way while remaining easily accessible. These layout controls apply whether your organization uses standard Screen Recording or has the Agent Assist integration enabled.
When you open the application, the widget natively launches on the desktop.
The widget aligned to the left sidebar (showing Agent Assist content when active).
The widget is designed to always stay on top of other windows. Regardless of the applications or screens the agent navigates to, status and assistive guidance remains immediately accessible.
Agents can fully customize the widget's positioning to best suit their screen layout and workflow without obstructing their primary tasks.
Drag the launcher to detach the widget, or snap it to the edge of the display.
The widget can be snapped cleanly to either edge of the agent's display:
The widget snapped securely to the right sidebar.
For ultimate flexibility, agents can detach the widget. In floating mode, the interface collapses to a compact view and can be dragged anywhere on the screen. Once released, it will smartly snap to the nearest screen corner.
Compact Picture-in-Picture layout snapped to the bottom right corner.
When agents do not need the widget, such as during offline periods, they can hide the interface completely by clicking the Close icon or double-clicking the Level AI taskbar icon.
[!NOTE] This deployment model is for non-persistent Windows VDI, pooled desktops, and Citrix environments that are rebuilt from a golden image. It deploys the Level Screen Recorder application only. It does not install or use the Level AI Watchdog.
Are you evaluating the Level Screen Recorder for your organization? Read our dedicated Security Architecture & FAQ to understand how we encrypt data and accommodate EDR/Antivirus policies in VDI environments.
Complete every check with your security and endpoint team before you provision the golden image. Resolve any No or Unsure answers, then generate a report for LevelAI.
Use the computer’s default screen resolution.
%APPDATA%\Level Screen Recorder\ is preserved across logons. In non-persistent pools without profile roaming, users will need to authenticate again after receiving a fresh desktop.| Screens | Upload |
|---|---|
| 1 | 5 Mbps |
| 2 | 8 Mbps |
| 3 | 12 Mbps |
| 4 | 16 Mbps |
Allow outbound traffic from the signed-in user's session. No SYSTEM service needs outbound access for the recorder in this VDI model. Use DNS names rather than fixed IP addresses because Level services and signed download URLs can change IP addresses.
| Destination | Port | Purpose |
|---|---|---|
screen-prod.thelevel.ai | TCP 443 | Recorder authentication, configuration, and session APIs |
screen.thelevel.ai | TCP 443 | Secure recording stream (RTMPS) |
screen-app-v3.thelevel.ai | TCP 443 | Level Screen Recorder user interface |
time.windows.com | UDP 123 | Time synchronization |
time.google.com | UDP 123 | Time synchronization fallback |
time.cloudflare.com | UDP 123 | Time synchronization fallback |
time.nist.gov | UDP 123 | Time synchronization fallback |
Add these destinations only if Agent Assist is enabled for your tenant (you see both Screen Recording and Agent Assist in the app; see Step 3: Launch the App). If you use Screen Recording without Agent Assist, skip this table.
| Destination | Port | Purpose |
|---|---|---|
aa-auth.thelevel.ai | TCP 443 | Agent Assist authentication and session cookies |
agent-assist.web.app | TCP 443 | Agent Assist UI module (federated widget and assets) |
launchdarkly.thelevel.ai | TCP 443 | Agent Assist feature-flag configuration |
api-js.mixpanel.com | TCP 443 | Agent Assist analytics events |
events.launchdarkly.com | TCP 443 | Agent Assist feature-flag analytics events |
Important: Permit HTTPS redirects to the destinations listed above and configure the VDI user's proxy and trusted-root settings.
If your organization decrypts HTTPS traffic, place the corporate root CA in Local Computer → Trusted Root Certification Authorities. The Level Screen Recorder reads trusted roots from the Windows certificate store. If inspection still blocks the connection, bypass inspection for the Level destinations above.
The NTP entries require outbound UDP 123. time.windows.com is normally already available on managed Windows devices. If UDP 123 is blocked, Level Screen Recorder uses HTTPS time through screen-prod.thelevel.ai; accurate Windows system time is still required for authentication and recording timestamps.
This model does not use the Level AI Watchdog. Install Level Screen Recorder into the golden image as an administrator. IT owns updates by republishing the image.
Enter your organization name, select Generate, and download the Screen Recorder MSI. Deploy the silent install command from the builder during image build (elevated prompt or automation). Include TENANT= on the command (written to HKLM at install). Recorder MSI does not use TOKEN= (Watchdog only).
Important: Install the Screen Recorder during golden image creation, not on each non-persistent session at login. Use the full silent install command from the builder, including
TENANT=(notmsiexec /ialone). When you bump the recorder version in the image, download the new MSI and regenerate the command before you rebuild the image.
Complete the matching items in the IT Admin Pre-Deployment Checklist first. The sections below are the configuration reference.
Ask the client's endpoint-security team to approve the Level Screen Recorder (signed-in user) before deployment. A partial allowlist can leave the application unable to launch or capture the screen.
Review the endpoint-security checklist below to ensure proper operation.
Two contexts, not two people:
| Context | Who this is | Rights |
|---|---|---|
| Installer | An administrator installs the MSI (in the golden image). | Admin is required only to install the MSI into the image. |
| Signed-in user | The person using the VDI session. | Standard-user rights. No admin. |
The installer must be allowed to:
msiexec.exe for Level Screen Recorder install, update, repair, and uninstall within the golden image.C:\Program Files\ and C:\ProgramData\.The signed-in user must be allowed to:
C:\Program Files\Level Screen Recorder\.%APPDATA%\Level Screen Recorder\, C:\ProgramData\Level Screen Recorder\, and %TEMP%.LevelScreenRecorder_Scheduler_<user-SID> scheduled task.To ensure smooth operation, you must configure your EDR/Antivirus solution.
Option A: Trusted Publisher Rule (Highly Recommended) Where policy permits, create a trusted-publisher rule for production files signed by Ujwal Inc (Level AI's code-signing publisher). This is the most secure and robust method.
Option B: Folder Whitelisting (Fallback) If publisher rules are not an option, you must explicitly exclude or allow the following installation and data folders:
C:\Program Files\Level Screen Recorder\
C:\ProgramData\Level Screen Recorder\
And per user:
%APPDATA%\Level Screen Recorder\
Minimum EDR Requirements At minimum, EDR must not:
LevelScreenRecorderProcessRunner.exe.Option A: Publisher Rule (Recommended) Create publisher rules for Publisher: Ujwal Inc covering Level Screen Recorder, without restricting the rule to one current file version.
Option B: Path Rules (Fallback) If publisher rules are not available, use controlled path rules for:
%ProgramFiles%\Level Screen Recorder\*
Level Screen Recorder normally uses its signed native process runner. If AppLocker, WDAC, EDR, or child-process rules block by parent process, allow these only when launched by Level Screen Recorder:
| Process | Purpose | Runs as |
|---|---|---|
LevelScreenRecorderProcessRunner.exe |
User identity, monitor detection, certificate and security diagnostics, scheduled-task operations | Signed-in user |
schtasks.exe |
Create/query/update the user's auto-launch task | Signed-in user |
reg.exe |
Read the user's Windows proxy settings | Signed-in user |
taskkill.exe |
Recover duplicate or unresponsive Level Screen Recorder processes | Signed-in user |
Blocking all fallback utilities does not grant a security boundary if the native helper remains allowed, but it reduces diagnostics and recovery. Prefer publisher and parent-child rules over broad path exclusions.
Apply all entries in Firewall Whitelisting. For TLS inspection requirements, see HTTPS inspection.
Installing the recorder does not open it. It opens on its own the next time the agent signs in, including after a restart. If it does not appear, the agent can open Level Screen Recorder once from the Start menu. After that first start, it opens on its own each time they sign in.
If the desktop blocks programs from starting at sign-in, set a sign-in action that starts the recorder on the agent's own desktop. Do not start it as a system service or in a disconnected background session.
Note: Screenshots may look slightly different in your build.
Enter your organization name, the part before .thelevel.ai (ask your admin if you are unsure). Example for Level AI: level.

Sign in with your account or SSO.

You should see a status page showing whether recording is on or off.
Screen Recording only (Agent Assist not enabled):
Screen Recording and Agent Assist (both enabled for your tenant):
The Level Screen Recorder v5 desktop application provides a modern, flexible interface designed to stay out of the way while remaining easily accessible. These layout controls apply whether your tenant uses standard Screen Recording or has the Agent Assist integration enabled.
When you open the application, the widget natively launches on the desktop.
The widget aligned to the left sidebar (showing Agent Assist content when active).
The widget is designed to always stay on top of other windows. Regardless of the applications or screens the agent navigates to, status and assistive guidance remains immediately accessible.
Agents can fully customize the widget's positioning to best suit their screen layout and workflow without obstructing their primary tasks.
Drag the launcher to detach the widget, or snap it to the edge of the display.
The widget can be snapped cleanly to either edge of the agent's display:
The widget snapped securely to the right sidebar.
For ultimate flexibility, agents can detach the widget. In floating mode, the interface collapses to a compact view and can be dragged anywhere on the screen. Once released, it will smartly snap to the nearest screen corner.
Compact Picture-in-Picture layout snapped to the bottom right corner.
When agents do not need the widget, such as during offline periods, they can hide the interface completely by clicking the Close icon or double-clicking the Level AI taskbar icon.
The recorder does not self-update on Windows when it is deployed without the Watchdog. IT must manage its lifecycle:
Do not rely on a user session to download, install, repair, or roll back the recorder. This keeps the installed version deterministic across freshly created desktops.
Validate on the same Citrix/VDI configuration, security policy, proxy path, and user-profile policy that production users will receive:
This app-only architecture is suitable for VDI when those validation checks pass. It intentionally trades autonomous Watchdog lifecycle management for IT-controlled golden-image releases.

Note: Screenshots may differ slightly from the actual UI of the app.
level.


It is recommended that agents use the default screen resolution on their device. The app captures at native resolution and composites all displays into a single 720p-tall frame; the width grows proportionally with the number of monitors. Quality profiles (HIGH / MEDIUM / LOW) adjust only the encoding bitrate (HIGH 5,500 / MEDIUM 4,500 / LOW 3,500 kbps per monitor). The composite height stays at 720p.
| DNS / URL | Port | Reason for Whitelisting |
|---|---|---|
prod-api.thelevel.ai | 443 | Level API authorization and login |
screen-prod.thelevel.ai | 443 | Platform API (recording session, token refresh, audit logs) |
storage.googleapis.com | 443 | Chunk uploads to Google Cloud Storage |
http-intake.logs.datadoghq.com | 443 | Send app activity logs to Datadog |
*.ingest.us.sentry.io | 443 | Error and performance monitoring (Sentry) |
sr-releases.thelevel.ai | 443 | IWA update manifest and signed bundle downloads |
www.cloudflare.com | 443 | Time synchronization, primary (HTTPS trace endpoint) |
timeapi.io | 443 | Time synchronization, fallback (if Cloudflare endpoint is unreachable) |
| Your Okta / SSO IdP domain | 443 | SSO authentication (if Okta SSO is configured for your organization) |
To roll out the app to a specific group of users before enabling it org-wide, use Google Admin Console's Org Unit (OU) hierarchy:
Only users in the child OU will receive the app. Once validated, you can move additional users into the OU or apply the same policies at a higher level for full rollout.
Note: If you are doing a limited rollout, perform these steps on the child Org Unit you created in the Limited Availability Release section above, not the parent OU.
Go to admin.google.com → Devices → Chrome → Apps & extensions.
Select the Users & browsers tab.
Select the target Org Unit.
Click + → Add Isolated Web App.
Fill in:
| Field | Value |
|---|---|
| Web bundle ID | Provided by Level AI |
| Update manifest URL | Provided by Level AI |
Click Save.
Go to Devices → Chrome → Web capabilities.
Select the same Org Unit.
Click Add origin.
Fill in:
| Field | Value |
|---|---|
| Origin | Provided by Level AI |
| Screen recording | Allowed |
Click Save.
Go to Devices → Chrome → Apps & extensions → Users & browsers.
Select the same Org Unit.
Click the IWA entry for this app (the list shows the update manifest URL and bundle id; selecting it opens the details panel on the right).
In the right-side panel, set Installation policy and Launch on login as below, then click Save.
| Setting | Value |
|---|---|
| Installation policy | Force install + pin to ChromeOS taskbar |
| Launch on login | Force launch and prevent closing |
The panel also shows Web bundle ID and Update manifest URL; they must match the values above. You may see This app is unverified and may not work properly. That is expected for self-hosted IWAs on managed devices.
Under Launch on login, the console may warn that preventing IWAs from being closed might affect device speed and performance; that is normal for this setting.
On a test Chromebook:
Policy sync can take 5–30 minutes. Signing out and back in speeds it up.
Note: Screenshots may differ slightly from the actual UI of the app.
level.

