Joring Docs
Admin

Roll out Joring to your team

Deploy the browser extension through MDM, add terminal and desktop coverage, and confirm data is arriving.

A rollout has three parts: get the extension onto machines, decide who needs terminal coverage, and confirm the data is landing before you tell anyone the numbers are real.

Push the extension through your MDM

Deploy by extension ID and force-install, the same way you deploy any other managed extension. The install files under Settings → Devices carry the profiles, registry file and policy JSON for your MDM and platform, and sign the extension in through your identity provider; see Deploy Joring through your MDM. People should not be installing it themselves: a self-service rollout produces uneven coverage that looks like uneven adoption.

Chrome, Edge, Firefox, and Safari are supported. Chrome and Edge cover most fleets.

Safari takes three pieces instead of one policy file, all in the install files under Devices: the Joring for Safari app goes out through Apps and Books, a declaration keeps its extension turned on, and a configuration profile carries the same settings the other browsers get. A managed Safari then signs in through your identity provider in a tab that closes itself. Two limits are Apple's: the always-on state needs supervised Macs on macOS 15 or later, and on macOS 14 people still grant the extension access to each site the first time.

Add native and terminal coverage

The browser extension cannot see Claude Code or Codex. If engineering is in scope, push the desktop agent too, or their usage will be invisible and your adoption data will say the opposite of what is true. The same agent covers the supported native Claude, Microsoft 365 Copilot, Teams, and Slack AI surfaces.

See Supported AI tools for the full split.

Verify data is arriving

Open the organization view the next working day. You are looking for recognizable teams appearing, not final numbers — the first day is always partial because it only captures conversations that happened after install.

Set your policy before you widen the rollout

If you have governance requirements, configure them before the population grows. See Governance.

NextTeams and roles

Decide who administers Joring before you invite the organization.

On this page