How to Configure Custom Meeting Domains in Launcher

This guide shows you how to add support for a meeting platform Launcher doesn't recognize by default — such as an on-premise Skype for Business server, Jitsi, or Whereby — using the custom_meeting_domains setting in config.json.

By default, Launcher only detects "Join Meeting" links for known platforms (Teams, Zoom, Webex, Google Meet, BlueJeans, Lifesize). If a calendar event contains a link from a platform outside that list, no "Join Meeting" button appears. This setting lets you add arbitrary domains without waiting for a new app release.

Prerequisites

• Launcher 2.9.0 or later.
• File access to the device's config.json (local access, USB, or your usual remote file management method).
• Not yet available in Central Manager. This currently must be set directly in config.json on the device — there is no Central Manager portal field for it yet.

Steps

1. Open config.json on the device. Locate the Launcher configuration file on the device. (C:\Users\ronan.logue\AppData\Local\Packages\DisplayNote.Launcher_dd93t4t878ybj\LocalState)

2. Add the custom_meeting_domains array. Add (or edit) the field as a flat list of domain strings — no http://, https://, or paths:

   {
       "channel": "released",
       "custom_meeting_domains": [
         "meet.codico.com",
         "meet.customerdomain.com"
       ]
     }

3. Save the file.
4. Restart the Launcher app. Changes to the domain list only take effect after an app restart — no reinstall is required.

Verify It Worked

Open (or wait for) a calendar event whose body or location contains a link matching one of the configured domains exactly. A "Meeting" join button should appear. Clicking it opens the link in the device's default system browser.

Common Issues

• Subdomains don't match. Listing meet.codico.com will not match sub.meet.codico.com — only exact host matches are detected.
• Link opens in a browser, not a native app. This is a browser-based join, the same as Google Meet/BlueJeans/Lifesize today. If the on-prem solution (e.g. Skype for Business) requires its native client to actually join, this setting alone may not be sufficient.
• No change after editing? Confirm the app was restarted after saving config.json.
• Existing platform detection is unaffected — Teams, Zoom, Webex, etc. continue working exactly as before.

Note on Central Manager: if a device's settings are managed via Central Manager, a CM-pushed value for this setting takes priority over config.json, and a CM push that omits the field won't clear a previously set list. However, there is currently no field in the Central Manager admin portal for managing this — until that ships, this is a manual config.json edit only.

Related Articles

• Adding web shortcuts
• Adding application shortcuts