For the complete documentation index, see llms.txt. This page is also available as Markdown.

Browser Compatibility

Supported browsers and required settings (JavaScript, cookies, and permissions).

Overview

Transform requires a modern, supported web browser. Core features require JavaScript and cookies.

Use this page when diagnosing login, rendering, or permission prompts. Use System Requirements for device and network recommendations.

Key Concepts

  • JavaScript: required to render the app UI

  • Cookies: required for session and preference storage

  • Site permissions: microphone and notifications (optional, feature-dependent)

  • Extensions: may interfere with scripts, cookies, or network requests

How It’s Used

Use this checklist during rollout. Use it as the first step in browser-based troubleshooting.

Benefits

  • Fewer “page won’t load” issues

  • More reliable sign-in sessions

  • Cleaner audio capture when Meeting Notetaker is enabled

Setup Steps

1) Use a modern browser

Use an evergreen browser on the latest stable version. Update the browser regularly.

2) Enable JavaScript

Confirm JavaScript is enabled for the Transform domain.

3) Allow cookies

Confirm cookies are allowed for the Transform domain. Avoid strict cookie-blocking modes for primary usage.

4) Allow pop-ups when required

Allow pop-ups for the Transform domain when a workflow opens a new window.

5) Configure site permissions (feature-dependent)

  • Microphone: required for Meeting Notetaker capture

  • Notifications: optional for browser-level notifications

Test in a private browsing window to reduce extension impact. Disable extensions that block scripts or cookies when issues occur.

Best Practices

  • Standardize on one browser configuration across a delivery team.

  • Avoid running heavy privacy or script-blocking extensions during delivery work.

  • Use a dedicated browser profile for delivery work when policy allows.

Summary

Browser compatibility depends on a modern browser, enabled JavaScript, allowed cookies, and correct site permissions. Isolate issues by testing without extensions and with a clean cache state.

Related:

Last updated