Integrating your org
Setting Lore up for an org touches two concerns:
- Knowledge: governance hooks deliver your org’s Rules and memory to every AI session, capture collects what members do with AI, and memory holds what the org knows.
- Usage & cost: Claude telemetry reports usage from each machine, and usage connectors pull it from each vendor.
This guide walks through the steps in order. Each one links to the page that covers it in full. In the painel, your org’s AI Integration → Setup page (/orgs/{org}/integration) shows the same checklist with the state of each step, and Coverage (/orgs/{org}/integration/coverage) shows, per member, who has the hooks, when they last uploaded captures and when their telemetry last arrived.
| Step | Done | Plan |
|---|---|---|
| Members & sign-in | Once per org, in the painel | Custom identity provider: Pro |
| Rules & SDD framework | Once per org, in the painel | All plans |
| Governance hooks | On each machine (lore hooks install) | All plans; org mode: Pro |
| Capture | Optional. Once per org, in the painel; its hooks come with lore hooks install | Uses the org’s storage plan |
| Memory | Nothing to install | Pro |
| Claude telemetry | Once per org (claude.ai console or MDM) | Pro |
| Usage connectors | Once per org, in the painel | Pro |
Members & sign-in
Once per org, in the painel. Invite people on the org’s Members page. Each member signs in once with lore login, and the hooks, the CLI and the MCP connector all use that sign-in. On Pro, members can sign in with your company’s identity provider instead of GitHub: see Org Identity Provider.
Rules & SDD framework
Once per org, in the painel. List the Rules and Skills every session must get on Mandatory Packages (Mandatory Rules), and choose the org’s Spec-Driven Development framework on SDD Framework (SDD frameworks). On a machine, lore sdd status shows which framework applies to the current project, and lore pull with no package installs it.
Governance hooks
On each machine. Every member runs:
lore hooks install --org=<your-org>
lore hooks statusThis adds Lore’s session-start hook to each AI tool on the machine, so every new session starts with the org’s Rules and memory. See Governance hooks and Individual mode. A repository can carry the hook for everyone who opens it (Repository mode), and on Pro, IT can deploy it as managed settings that members can’t turn off (Org mode). The Governance Hooks page shows coverage per install.
Capture
Optional. Once per org, in the painel. The org owner turns capture on in the Captures page’s capture policy, choosing projects, harnesses and retention, and acknowledges the org’s responsibility for the data. There is no separate install: once the policy is on, lore hooks install also adds the capture hooks. Run it again on machines that installed the hooks before. See Session capture.
Memory
Nothing to install. Memory is the org’s shared knowledge. AI tools read and write it through the MCP connector, governance hooks deliver the most relevant records at session start, and, when distillation is on, captures become memory candidates that wait on Memory Review. Browse it on the Memory page. Org memory requires Pro. See Reading org memory.
Claude telemetry
Once per org, by the org owner. Claude Code reports its own usage and cost metrics to Lore. On the painel’s Claude Telemetry page, the owner creates an org ingest key and rolls the configuration out to everyone through the claude.ai console or an MDM drop-in (Intune, Jamf and others): see Org rollout. Members have nothing to run.
lore hooks install doesn’t configure telemetry: the ingest key is org-wide and shown only once, so it travels with the org’s rollout, not with each member’s install. To check a machine, run lore hooks status. It reports Claude telemetry: configured (managed), configured (user) or not configured, and never prints the key.
Telemetry is attributed to the email of the member’s Claude account, which may differ from the email they sign in to Lore with. When it does, open Members and add the Claude email to that member under Other emails. Coverage then shows one row for the person, and their usage counts as a member’s. Other emails never sign in to Lore. If that email had been added as a separate member, remove that member first. Records that arrived before the email was added stay flagged as non-member in usage reports.
Cowork usage is configured separately, once, in claude.ai: see Cowork telemetry.
Usage connectors
Once per org, in the painel. The org owner connects each vendor’s admin API on Usage Connectors, and Lore pulls the org’s usage and cost every hour into AI Usage. See AI Usage Connectors.