Mediabriz Conversation Intelligence Enterprise Deployment Guide

Quick Start (Recommended)

For most enterprise deployments:

1. Force-install the extension via Google Workspace or Microsoft Intune.
2. Set the managed policy values for your organization and region:

   {
     "organizationName": "your-org",
     "region": "your-region"
   }

   Nothing else is needed for Genesys Cloud access. The Genesys Cloud domains are install-time permissions, so Chrome and Edge grant them when the extension is installed and on every update, with no prompt (see Host Permissions).
3. Only if your organization blocks extensions on sites by default (runtime_blocked_hosts), add the four hosts of your region to runtime_allowed_hosts as an exception. Replace <region> with your own region domain from Valid Region Values:

   "runtime_allowed_hosts": [
     "*://apps.<region>",
     "*://login.<region>",
     "*://api.<region>",
     "*://api-downloads.<region>"
   ]

   Example only: for Europe (Frankfurt), <region> is mypurecloud.de, so the entries are *://apps.mypurecloud.de, *://login.mypurecloud.de, *://api.mypurecloud.de and *://api-downloads.mypurecloud.de. Use your own region, not Frankfurt.

   runtime_allowed_hosts does not grant anything by itself.

4. Only if agents use Mediabriz on your own domain (for example a CRM or portal that shows Genesys Cloud), add the custom domain keys to the policy. Each user then allows the domain once (see Custom Domain Deployment).

The extension will be installed automatically and will be ready to use on Genesys Cloud without any user configuration.

For detailed configuration and platform-specific instructions, see the sections below.

Choose your platform

ChromeGoogle WorkspaceEdgeMicrosoft Intune

Sections below the platform guides (Policy Reference, Host Permissions, Custom Domain Deployment, Troubleshooting, Examples) apply to both platforms.

Overview

This guide covers how to deploy the Mediabriz Conversation Intelligence browser extension across your organization using Google Workspace (Chrome) or Microsoft Intune (Edge). It includes extension installation, managed policy configuration, host permissions, and troubleshooting.

What Is Being Deployed

Mediabriz Conversation Intelligence is a browser extension deployed to end-user browsers (Chrome or Edge) and managed centrally by IT administrators.

Installation

The extension is installed via browser management policies (Google Workspace or Microsoft Intune). It runs within the browser context and is not designed to install or execute system-level components. No desktop agents or additional client software are required.

Configuration

After installation, the extension is configured using enterprise managed policies. Configuration includes the organization name, Genesys Cloud region, and optional settings such as feature toggles and custom domains.

The extension can be configured to operate on supported domains, including Genesys Cloud and organization-defined custom domains.

Users must authenticate via Genesys Cloud to use Mediabriz functionality.

Prerequisites

• Active Mediabriz Conversation Intelligence subscription - ensure your organization has an active Mediabriz Conversation Intelligence subscription provisioned. Contact us if you have not completed onboarding.
• Genesys Cloud region - the region domain where your organization is hosted (e.g., mypurecloud.com for US East). See the Valid Region Values table below.
• Admin console access - Google Workspace Admin Console (Chrome) or Microsoft Intune admin center (Edge).
• Extension ID - Edge: bpdjeihgofhpojeghkomckhgahioiomo. Chrome: dojbgeididmgnlieckgekbfdncaamhbm. See Get the Extension below.
• Network access - ensure Mediabriz and Genesys Cloud domains are reachable through corporate firewalls and proxies (HTTPS, port 443). See Network Requirements for the full list of required domains.

Get the Extension

The Mediabriz extension is available on the Chrome Web Store (for Chrome) and the Edge Add-ons store (for Edge). For enterprise deployments, install it via browser policy rather than manually - see the platform-specific sections below.

For individual (non-managed) installs, users can install the extension directly from the store.

Note: Chrome and Edge have different extension IDs for the same extension. Use the correct ID for your target browser throughout the deployment configuration.

Google Workspace Deployment

Applies to: Chrome on Windows, macOS, Linux, and ChromeOS

Platform: The same Admin Console configuration applies to Chrome on Windows, macOS, Linux, and ChromeOS.

1. Open Google Admin Console at admin.google.com.

2. Navigate to Chrome Management - Devices > Chrome > Apps & Extensions > Users & browsers.

3. Select Organizational Unit - choose the OU where you want to deploy.

4. Add the Extension - click +, select Add from Chrome Web Store, and enter the Mediabriz extension ID: dojbgeididmgnlieckgekbfdncaamhbm.

5. Set Installation Policy to Force install.

6. Configure Managed Policy - scroll to Policy for extensions and paste the JSON configuration. Example only: replace acme-corp with your Genesys Cloud organization short name and mypurecloud.com with your own region domain (see Valid Region Values):

   {
     "organizationName": "acme-corp",
     "region": "mypurecloud.com"
   }

   See Managed Policy Reference for all available fields.

7. Save. The extension deploys on the next Chrome sync (typically within minutes).

Alternative: JSON-Based Policy

For organizations managing Chrome policies via MDM or file-based configuration, use the ExtensionSettings policy:

{
  "dojbgeididmgnlieckgekbfdncaamhbm": {
    "installation_mode": "force_installed",
    "update_url": "https://clients2.google.com/service/update2/crx"
  }
}

Add runtime_allowed_hosts only if the same policy blocks extensions on sites by default (runtime_blocked_hosts); see Host Permissions.

Managed storage is configured separately via the 3rdparty.extensions.dojbgeididmgnlieckgekbfdncaamhbm.policy key. See Chrome Enterprise policy documentation.

Microsoft Intune (Edge) Deployment

Applies to: Edge on Windows and macOS

Tip: For most deployments, only Step 2 (force-install) and Step 3 (managed storage configuration) are required.

Important: Edge managed storage (chrome.storage.managed) is configured through OS-level policies (Windows Registry or macOS plist), not through the ExtensionSettings JSON. This requires two separate profiles: one for force-install, and one for managed policy values.

1. Sign in to Intune at intune.microsoft.com.

2. Create Force-Install Profile

   • Go to Devices > Manage devices > Configuration > Create > New policy.
   • Select platform (Windows 10 and later or macOS), profile type: Settings catalog.
   • Search for Configure extension management settings under Microsoft Edge > Extensions.
   • Add the ExtensionSettings JSON below to force-install the extension. Add runtime_allowed_hosts only if you block extensions on sites by default (runtime_blocked_hosts); see Host Permissions.

   {
     "bpdjeihgofhpojeghkomckhgahioiomo": {
       "installation_mode": "force_installed",
       "update_url": "https://edge.microsoft.com/extensionwebstorebase/v1/crx"
     }
   }

3. Create Managed Storage Profile

   Edge reads managed extension configuration from OS-level policies. The mechanism differs by platform.

   Reminder: All registry, PowerShell, and plist examples in the Windows and macOS sub-sections below show mypurecloud.com (US East) as the region value. Replace it with your organization’s actual region domain from the Valid Region Values table.

   Windows - Registry

   Write managed storage values to:

   HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\bpdjeihgofhpojeghkomckhgahioiomo\policy

   Registry Value Name	Type	Data
   organizationName	REG_SZ	acme-corp
   region	REG_SZ	mypurecloud.com

   Deploy via Intune using a Custom profile with OMA-URI entries, a PowerShell remediation script, or the Settings catalog. See Microsoft's documentation.

   Example PowerShell script:

   $regPath = "HKLM:\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\bpdjeihgofhpojeghkomckhgahioiomo\policy"
   New-Item -Path $regPath -Force | Out-Null
   Set-ItemProperty -Path $regPath -Name "organizationName" -Value "acme-corp" -Type String
   Set-ItemProperty -Path $regPath -Name "region" -Value "mypurecloud.com" -Type String

   Setting array values (e.g., customDomains) in registry:

   Array-type fields require numbered subkeys under the field name. For example, to set customDomains with two entries:

   HKLM:\...\policy\customDomains\1  REG_SZ  "*.salesforce.com"
   HKLM:\...\policy\customDomains\2  REG_SZ  "crm.acme-corp.com"

   macOS - Property List (plist)

   Edge on macOS reads managed extension policies from per-extension plist files, not from the main com.microsoft.Edge plist. The plist file must be named com.microsoft.Edge.extensions.bpdjeihgofhpojeghkomckhgahioiomo.plist, with policy values placed directly in the root <dict> (no 3rdparty/extensions/policy nesting).

   Note: This differs from Chrome on macOS, which uses a nested structure under com.google.Chrome. Edge Beta and Dev channels use com.microsoft.Edge.Beta.extensions.bpdjeihgofhpojeghkomckhgahioiomo and com.microsoft.Edge.Dev.extensions.bpdjeihgofhpojeghkomckhgahioiomo respectively.

   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
     "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
     <key>organizationName</key>
     <string>acme-corp</string>
     <key>region</key>
     <string>mypurecloud.com</string>
   </dict>
   </plist>

   Setting array values (e.g., customDomains) in plist:

   Array-type fields use the <array> element:

   <key>customDomains</key>
   <array>
     <string>*.salesforce.com</string>
     <string>crm.acme-corp.com</string>
   </array>

   In Intune: Devices > Manage devices > Configuration > Create > New policy > macOS > Templates > Custom, set preference domain to com.microsoft.Edge.extensions.bpdjeihgofhpojeghkomckhgahioiomo. See Microsoft's Edge on macOS documentation and the TechCommunity discussion on Edge extension managed storage.

   Known limitation: Some administrators have reported that Edge on macOS does not always reliably deliver managed storage values to extensions. If managed configuration does not appear after deployment, verify the plist file name matches the extension ID exactly and check edge://policy for policy delivery status.

4. Assign to Device Groups - add target device or user groups to all profiles, then Save.

5. Deploy - profiles apply on the next Intune sync. Users will see the extension installed with the organization pre-configured.

Managed Policy Reference

Applies to: Chrome and Edge

Mediabriz reads enterprise configuration from chrome.storage.managed. The full JSON policy is shown below, followed by field-level documentation.

Full JSON Policy

The snippet below shows every supported field with example values. organizationName and region are required and must be replaced with your organization’s actual short name and Genesys Cloud region domain. mypurecloud.com (US East) is shown only as an example; see Valid Region Values for the complete list. All other fields are optional and shown with their defaults.

{
  "organizationName": "acme-corp",
  "region": "mypurecloud.com",
  "customDomainEnabled": false,
  "customDomainMode": "addition",
  "customDomains": [],
  "searchEnabled": true,
  "searchByIdEnabled": true,
  "searchByDetailsEnabled": true,
  "exportPdfEnabled": true,
  "mediaDownloadEnabled": true,
  "countryCodeOverrideEnabled": false,
  "countryCodeOverride": "us",
  "timeFormatOverrideEnabled": false,
  "timeFormatOverride": "24h",
  "appLanguage": "en"
}

Field Reference

Organization Settings

Valid Region Values

Examples convention used throughout this guide: The JSON, registry, PowerShell, and plist snippets in the deployment, host-permissions, and configuration sections below use mypurecloud.com (US East, N. Virginia) as the example Genesys Cloud region. This is for illustration only. Mediabriz supports all 18 Genesys Cloud regions listed in the table above. When applying any example to your deployment, replace mypurecloud.com (and the four apps./login./api./api-downloads.mypurecloud.com subdomains derived from it) with your organization’s actual region domain. Examples that intentionally show a different region (such as mypurecloud.de for the Full Configuration walk-through) are explicitly labeled as such.

FedRAMP / GovCloud: use2.us-gov-pure.cloud (US East 2 - Ohio) is supported end-to-end: content scripts inject on apps.use2.us-gov-pure.cloud, login-redirect detection recognizes login.use2.us-gov-pure.cloud, and the Mediabriz API allowlists accept *.us-gov-pure.cloud media URLs.

European Sovereign (Brandenburg): edee1.eusc-pure.cloud is a data-sovereignty region, supported end-to-end: content scripts inject on apps.edee1.eusc-pure.cloud, login-redirect detection recognizes login.edee1.eusc-pure.cloud, and the Mediabriz API allowlists accept *.eusc-pure.cloud media URLs. Note the hyphen before pure: eusc-pure.cloud is a distinct TLD from *.pure.cloud.

Custom Domain Settings

Steps for a custom domain deployment are in Custom Domain Deployment.

Note on customDomains format (managed values are stored verbatim): Values pushed via enterprise policy (ExtensionSettings JSON, Windows Registry, macOS plist) are stored byte-for-byte verbatim, with no auto-rewriting. To cover an apex AND its subdomains in a single entry, write the wildcard form explicitly (e.g., *.acme.com, not acme.com). An apex-only entry like acme.com requests the host permission for https://acme.com/* only, and Chrome does not extend that grant to subdomains, so the extension would silently fail to load on app.acme.com, crm.acme.com, etc. The end-user settings UI in the extension auto-rewrites apex inputs (e.g., a user typing acme.com) to *.acme.com for convenience, but managed-policy values never receive this transform, so admins keep full control over the string they push.

Feature Toggles

Regional Preferences

Choosing a country code: Set countryCodeOverride to the lowercase two-letter ISO 3166-1 alpha-2 code for the country whose phone-number formatting you want agents to see. Common values: us (United States), gb (United Kingdom), de (Germany), il (Israel), au (Australia), fr (France). For any other country, look up the code in the Wikipedia list linked above.

Host Permissions

Applies to: Chrome and Edge

Mediabriz requires browser host permissions to operate on specific domains. These permissions determine where the extension is active and able to interact with page content.

Genesys Cloud addresses used per region

For each region, Mediabriz uses these 4 addresses. There is nothing to grant: the browser grants them when the extension is installed. The list is for network allowlists: firewalls, proxies, SSL inspection, web filters, and the runtime_allowed_hosts exception. Replace <region> with the domain from the Valid Region Values table:

• *://apps.<region> - Genesys Cloud UI (toolbar injection)
• *://login.<region> - OAuth authentication
• *://api.<region> - API calls
• *://api-downloads.<region> - Media file downloads

All four are needed for full functionality.

Manifest design

host_permissions lists the Mediabriz API and media domains and the nine Genesys Cloud domain patterns (https://*.mypurecloud.com/*, https://*.mypurecloud.de/*, https://*.pure.cloud/*, and the others). The browser grants these when the extension is installed and on every update. Only https://*/*, used for custom domains, is optional.

How Permissions Are Granted

• Force-installed by policy (Google Workspace, Intune): the Genesys Cloud domains are granted at install and on every update, with no prompt. A policy-installed extension is never paused for new permissions. New staff, new PCs and new browser profiles need nothing.
• Installed from the store: the install dialog lists the Genesys Cloud domains with the Mediabriz domains, and nothing more is asked at setup.
• Policy cannot grant an optional permission. Chrome and Edge grant an optional permission only after a user clicks Allow. runtime_allowed_hosts is only an exception list for sites blocked by runtime_blocked_hosts; it grants nothing.

When to use runtime_allowed_hosts

Only if your organization blocks extensions on sites by default (runtime_blocked_hosts in the ExtensionSettings policy, for example *://*). That browser policy overrides the extension's own permissions, so the browser withholds the Genesys Cloud addresses even though they were granted at install. List the four addresses of your region (see Genesys Cloud addresses used per region) and any custom domains as exceptions:

{
  "dojbgeididmgnlieckgekbfdncaamhbm": {
    "runtime_blocked_hosts": ["*://*"],
    "runtime_allowed_hosts": [
      "*://apps.<region>",
      "*://login.<region>",
      "*://api.<region>",
      "*://api-downloads.<region>"
    ]
  }
}

Example only: replace <region> with your own region domain from Valid Region Values. For Europe (Frankfurt), mypurecloud.de, the four entries are *://apps.mypurecloud.de, *://login.mypurecloud.de, *://api.mypurecloud.de and *://api-downloads.mypurecloud.de.

This example shows the Chrome Web Store extension ID. For Edge, use bpdjeihgofhpojeghkomckhgahioiomo. Existing runtime_allowed_hosts entries without a block list do no harm and can stay.

Custom domains

Custom domains use the optional https://*/* permission, so each user allows them once per browser profile: on the extension's settings page, a yellow notice lists the domains without access and offers Grant access, which opens the browser's prompt. This works whether or not the domain list is managed by policy: when it is managed, the domain fields are locked and Grant access is how each user allows the managed domains. See Custom Domain Deployment for the full steps.

What Site access should look like

On the extension's Details page, Site access lists the Mediabriz domains and the Genesys Cloud domains from install. Custom domains appear after the user grants them.

Custom Domain Deployment

Applies to: Chrome and Edge

Use a custom domain when agents work in your own web application (for example a CRM or an internal portal that shows Genesys Cloud) and Mediabriz should run there. Genesys Cloud access needs nothing more. Each custom domain needs the following:

1. Managed policy. Add the three custom domain keys to the same policy as organizationName and region. Example only: replace the organization, region and domains with your own:

   {
     "organizationName": "acme-corp",
     "region": "mypurecloud.com",
     "customDomainEnabled": true,
     "customDomainMode": "addition",
     "customDomains": [
       "*.salesforce.com",
       "crm.acme-corp.com"
     ]
   }

   customDomainEnabled must be true, or the list is ignored. "addition" runs Mediabriz on Genesys Cloud and the custom domains; "alternative" runs it on the custom domains only. For Edge, set the same keys in the registry or plist (see Windows - Registry and macOS - plist for the array syntax).

2. Domain format. Write the host name the agent sees in the address bar, with no https://, path or port. *.acme-corp.com covers acme-corp.com and every subdomain; crm.acme-corp.com covers that host only. HTTPS pages only, up to 10 domains. Do not list Genesys Cloud domains: they are already covered.

3. Each user allows the domains once. No policy can grant the optional custom domain permission. On the extension's settings page, each user clicks Grant access in the yellow notice and allows the browser's prompt, once per browser profile. The same applies when you add a domain to the policy later.

4. Only if you use runtime_blocked_hosts. Add each custom domain to runtime_allowed_hosts, next to the four region hosts (see When to use runtime_allowed_hosts). Grant access cannot open a site that policy blocks. Example only:

   "runtime_allowed_hosts": [
     "*://apps.<region>",
     "*://login.<region>",
     "*://api.<region>",
     "*://api-downloads.<region>",
     "*://*.salesforce.com",
     "*://crm.acme-corp.com"
   ]

On a custom domain, if Mediabriz cannot sign in silently, it opens a Genesys Cloud sign-in window, and the user signs in there.

What Users Will See

Applies to: Chrome and Edge

• Fields set by the admin appear as read-only with a "Managed by your organization" label.
• Fields not set by the admin remain editable by the user.
• If organizationName and region are both managed, users do not need to configure anything - the extension is ready to use immediately.

Live Policy Updates

As of v6.3.43, managed policy changes (region, feature toggles, custom domains, regional preferences) are picked up on the next browser policy sync without requiring an extension or browser restart. The extension subscribes to chrome.storage.onChanged for the managed namespace and, on every change, it re-reads the managed values and broadcasts a refresh to all open tabs so the menu, time format, country code, download policy, and search visibility update in place.

A newly managed region needs nothing: every Genesys Cloud region is covered by the install-time permissions. A newly managed custom domain needs each user's Grant access once (see Custom domains).

Security & Privacy

Data Flow Overview

Mediabriz is a browser-based application that integrates with Genesys Cloud services.

• Interaction metadata is retrieved from Genesys Cloud APIs
• Media files are fetched from Genesys Cloud media endpoints
• The Mediabriz backend is used for:
  • Organization validation
  • Feature configuration
  • Optional processing (e.g., media analysis)

Mediabriz is not designed to proxy Genesys Cloud traffic.

Mediabriz is not designed to persist or store full conversations or customer media outside temporary processing required for the Service.

Activation Scope

The extension is designed to be active on:

• The configured Genesys Cloud region domains
• Optional administrator-defined custom domains

It is not designed to run on unrelated websites.

Mediabriz is designed to operate within the permissions of the logged-in user and is not designed to elevate or bypass Genesys Cloud access controls.

Troubleshooting

Applies to: Chrome and Edge

Policy Not Applied (Chrome and Edge)

• Navigate to chrome://policy (Chrome) or edge://policy (Edge) and search for the extension ID.
• Force a policy refresh from the admin console or wait for the next sync interval.
• Verify the user's device is in the targeted OU or group.
• Validate the policy JSON with a JSON linter.

Extension Not Installed (Chrome and Edge)

• Confirm the ExtensionSettings JSON has "installation_mode": "force_installed" and the correct update_url.
• Check that the extension ID is correct.
• Verify the profile is assigned to the correct device or user group.

Extension Not Activating (Chrome and Edge)

• Ensure organizationName is lowercase.
• Verify region matches one of the valid values in the Valid Region Values table.
• Check that the organization has an active subscription.

Invalid Managed Values Ignored (Chrome and Edge)

If a managed region value is not in the supported region list, the extension logs [MANAGED] Invalid region in policy, ignoring value: <value> and falls back to the user-set value (or remains unconfigured). The same applies to customDomainMode (only "addition" / "alternative" are accepted) and timeFormatOverride (only "24h" / "12h" are accepted). This is intentional fail-safe behavior - a typo in policy will not silently route the extension to the wrong API endpoint or mis-lock the configuration UI.

Inspect the extension's background service-worker console (chrome://extensions > Mediabriz > Inspect views: service worker) and search for [MANAGED] Invalid warnings to identify which value was dropped.

Extension Installed but UI Not Visible (Chrome and Edge)

• Verify host permissions are granted for the active domain.
• Ensure the user is accessing a supported domain.
• Confirm the configured region matches the environment.

Host Permission Issues (Chrome and Edge)

Yellow notice on the Config page: a host permission is missing. Click Grant access and allow the prompt. For Genesys Cloud this only happens when someone removed Mediabriz's site access in the browser (Details > Site access); for custom domains it is expected once per user and browser profile.

Genesys Cloud pages still blocked: if your ExtensionSettings policy uses runtime_blocked_hosts, add the four region hosts to runtime_allowed_hosts (see When to use runtime_allowed_hosts), refresh policy and fully quit the browser.

Mediabriz showing as OK under chrome://policy or edge://policy means the managed values arrived; Site access on the extension's Details page shows what is granted.

Custom Domain Issues (Chrome and Edge)

Mediabriz does not appear on the custom domain:

• Check customDomainEnabled is true under chrome://policy or edge://policy. Without it the domain list is ignored.
• Check the user allowed the domain. The extension's settings page shows a yellow notice that lists each domain without access, and the toolbar popup shows Permissions Required. Click Grant access and allow the prompt.
• Compare the entry with the host in the address bar. acme-corp.com covers only that host, not app.acme-corp.com; use *.acme-corp.com. Remove any https://, path or port. HTTP pages are not supported.
• Mediabriz runs on the page in the address bar, not inside frames. If your application shows Genesys Cloud in a frame from another domain, list the domain of the outer page.
• If your ExtensionSettings policy uses runtime_blocked_hosts, add the domain to runtime_allowed_hosts (see Custom Domain Deployment), refresh policy and fully quit the browser.

Mediabriz no longer appears on Genesys Cloud: customDomainMode is "alternative", which runs it on the custom domains only. Use "addition" for both.

A new domain in the policy does not work: each user allows it once with Grant access, the same as the first domains.

Organization Validation Failures (Chrome and Edge)

• Verify network connectivity to api.mediabriz.com (US) or eu.api.mediabriz.com (EU).
• Confirm the organization name and region match the values configured during onboarding.
• Contact us if the organization is not found or has been suspended.

Viewing Extension Logs (Chrome and Edge)

1. Navigate to chrome://extensions (or edge://extensions).
2. Enable Developer mode.
3. Find Mediabriz and click Inspect views: service worker.
4. Check the Console tab for [MANAGED] prefixed log messages.

Configuration Examples

Applies to: Chrome and Edge

Minimal Configuration

The simplest deployment requires only the organization name and region. All other settings use their defaults. Example only: the snippet below uses mypurecloud.com (US East). Replace it with your own region from the Valid Region Values table.

{
  "organizationName": "acme-corp",
  "region": "mypurecloud.com"
}

• Activates the extension for acme-corp on US East.
• All feature toggles use defaults (enabled).
• Users can configure custom domains and preferences themselves.

Full Configuration

A fully locked-down deployment with all fields managed by the administrator. Example only: the snippet below uses mypurecloud.de (Europe Frankfurt) to show that any of the 18 supported regions can be used. Replace it with your own region from the Valid Region Values table.

{
  "organizationName": "acme-corp",
  "region": "mypurecloud.de",
  "customDomainEnabled": true,
  "customDomainMode": "addition",
  "customDomains": [
    "*.salesforce.com",
    "crm.acme-corp.com"
  ],
  "searchEnabled": true,
  "searchByIdEnabled": true,
  "searchByDetailsEnabled": false,
  "exportPdfEnabled": true,
  "mediaDownloadEnabled": false,
  "countryCodeOverrideEnabled": true,
  "countryCodeOverride": "de",
  "timeFormatOverrideEnabled": true,
  "timeFormatOverride": "24h",
  "appLanguage": "en"
}

• Activates on Europe (Frankfurt) with two custom domains in "addition" mode.
• Disables search by participant details; all other features enabled.
• Disables media downloads - download buttons, drag-and-drop to desktop, video snapshots, and image/PDF edit-export are all turned off across the UI to prevent media exfiltration. (Office file previews rendered through Microsoft's Office Online viewer expose their own download button which is outside the extension's control - see the mediaDownloadEnabled row in the Field Reference for details.)
• Forces German phone formatting and 24-hour clock.
• Custom domains: each user allows them once with Grant access on the settings page.
• All fields are read-only for end users.

For deployment questions or technical assistance, visit our Support Center or contact us.