Skip to main content

Bliro IT Onboarding

Fabian Erk avatar
Written by Fabian Erk
Updated yesterday

Bliro Desktop App: Technical Onboarding Guide

Welcome to the Bliro Desktop App Technical Onboarding Guide. This guide is designed to assist the technical team in successfully installing and configuring the Bliro desktop application within your corporate infrastructure.

Overview

To successfully install and configure the Bliro Desktop App, please follow the steps outlined below. Some steps are optional depending on your company’s infrastructure.

Install the Bliro Desktop App

To install the Bliro Desktop App, select the appropriate installer based on your operating system and chip architecture. Click the link to download the installer.

Operating System

File Extension

Chip Architecture

Link

Windows

.msi

all

Windows

.exe

all

MacOS

.dmg

Intel

MacOS

.dmg

Apple Silicon

Install .msi in system context [Windows]

If you centrally manage the distribution of Bliro Desktop app to your users, you might want to install the app on the device’s system context rather than user context. To do so, you can install the Bliro-Setup.msi installer via the following command:

msiexec /i "Bliro-Desktop-Setup-1.2.0.msi" /q /norestart

Allowlist Bliro domains at firewall level

To ensure the Bliro Desktop App functions properly, it must communicate with Bliro servers over the internet. If your organization restricts internet access by default, please allowlist the following domains for all users/devices who will run Bliro Desktop App:

Allowlist Bliro URLs at SSL interception level

Bliro servers, particularly authentication servers, verify SSL encryption integrity. If SSL interception is detected, requests from the client may be blocked. If your organization uses SSL interception, please allowlist the following domains:

In case of the following error message on “Start Meeting” in Desktop App, often the root cause is related to missing allow listing of wss connection with ws.bliro.io server. Please check whether a bypass for Bliro application exists.

[AudioWorker] onerror: WebSocket error occurred: Error: unable to get local issuer certificate Error: unable to get local issuer certificate at TLSSocket.onConnectSecure (node:_tls_wrap:1679:34) at TLSSocket.emit (node:events:518:28) at TLSSocket._finishInit (node:_tls_wrap:1078:8) at ssl.onhandshakedone(node:_tls_wrap:864:12)

Reverse Proxy

For organizations using reverse proxies, Bliro can be configured to work with both authenticated and non-authenticated proxies. Bliro works out of the box with the following proxy configurations:

  • Manually set fixed_servers configurations (client side)

  • Dynamic wpad file based configurations (server side)

  • Dynamic pac_script based configurations (server side)

Grant Calendar Access

Bliro works best when integrated with users' calendars. This allows Bliro to remind users to log meetings as they start, prefill meeting details from calendar events, and provide better meeting summaries with enhanced AI-driven context.

Bliro supports integration with both Google Calendar and Microsoft Outlook.

Microsoft Outlook Integration

To enable Bliro to access Microsoft Outlook calendars, users must be able to grant Bliro the following permissions:

Google Calendar Integration

To enable Bliro to access Google Calendar, users must be able to grant Bliro the following permissions:

IT Security Material

You are interested in Bliro’s approach to Security and Privacy? You can find all relevant material in our security portal.

Contact and Help

We are happy to assist you with making Bliro ready for your organization. Please contact our technical lead via [email protected].

Did this answer your question?