Skip to Content
V1GovernanceOrg mode

Org mode

Org mode is rolling out. It needs signed Lore CLI packages for device management, which are being prepared.

In org mode, IT deploys Lore’s hook through device management into each AI tool’s admin-managed settings. On managed devices members can’t turn it off, and org owners see coverage per person, tool and device. It requires the Pro plan and an org owner.

How it works

On each device, the bundle’s script runs:

lore hooks install --scope=managed --org=<your-org> --harness=claude,codex,copilot,cursor lore hooks status --json

--scope=managed merges Lore’s entry into each tool’s managed configuration and keeps the rest of your policy:

  • Claude Code: its own drop-in managed-settings.d/lore-hooks.json;
  • Codex: a marked block in requirements.toml;
  • Copilot: its own policy.d/lore.json;
  • Cursor: the enterprise hooks.json.

It backs up any file it changes, and running it again is safe. The second command prints the result for your MDM’s logs. Paths per OS are in the harness reference.

Before you start

  1. Deploy the Lore CLI to the devices.
  2. Plan for sign-in. Each member signs in once with lore login, and the hook uses that sign-in. Until then, the session shows a one-line notice.
  3. Claude Code and claude.ai managed settings. If your org configures Claude Code in claude.ai (Admin Settings → Claude Code → Managed settings), Claude Code ignores file-based managed settings. Add "managedSourcesBehavior": "merge" there, or add Lore’s hooks block to it directly.

Download the bundle

In the panel, go to Governance Hooks → Organization. Choose your device management tool and the AI tools, then download the bundle. It contains:

  • intune/, jamf/, kandji/, generic/: the scripts per device management tool;
  • preview/: the managed configuration each tool will end up with, for review.

Runbooks: Intune, Jamf, Kandji, other tools.

Exclusive mode

Lore’s managed hook can’t be disabled by members either way. Exclusive additionally turns on each tool’s “only managed hooks” switch (allowManagedHooksOnly in Claude Code, allow_managed_hooks_only in Codex). That also blocks members’ own hooks and, in Claude Code, some plugins and status lines. Only use it as a deliberate org policy.

Verify

  1. The script output lists each tool with scope managed and your org.
  2. On a device, a new session can quote your org’s Rules.
  3. Within an hour, the device appears as Enforced under Governance Hooks → Coverage.

If the plan lapses

Managed hooks keep running and still deliver your org’s Rules, but each session starts with a notice that the org’s plan no longer includes managed delivery, and coverage shows Managed · plan inactive. Org memory also stops, because it’s a Pro feature.

Remove

Run lore hooks uninstall --scope=managed as administrator through the same tool. It removes only Lore’s entries.

© 2025 Lore · Built by M1 Cloud