Claude adds legal artifacts, with source links and sharing limits
Anthropic added a ready-made legal artifacts gallery on October 28. It extends Claude for Legal, launched in May, rather than introducing another model. Teams can adapt example-filled tools with their documents and connectors. Anthropic says outputs link to their sources, with Claude handling an initial pass before a lawyer reviews the results.
What the gallery actually does
| Artifact | Intended task |
|---|---|
| Cite check | Compare claims and quotations with source material |
| Matter board | Organize matters, owners and next steps |
| Playbook deviation board | Surface differences from company contract terms |
| Tabular review | Extract selected contract terms into a source-linked table |
The gallery also covers jurisdiction comparisons and regulatory timelines. Partner contributions include Goodwin’s AI Governance Benchmark and Harvey Intake. These are vendor-described capabilities, not independently measured accuracy results.
Open the legal gallery in Claude. ByteForward verified the announcement and documentation, but has not run the templates.
A small evaluation before a wider rollout
An illustrative evaluation could use a handful of synthetic contracts with deliberately different renewal dates. Ask for a table containing the document name, extracted date, supporting passage and a blank reviewer sign-off column. Keep an answer key outside Claude, then compare every row with it. This is a suggested product test, not a tested result or a legal conclusion.
A useful failure to record is not just an incorrect date. Also check whether the source link opens the right passage, whether missing information stays visibly missing, and whether a colleague can reproduce the result with their own permitted sources. A polished table alone cannot answer those questions.
Access and connectors are separate checks
The general artifacts documentation lists artifacts across Free, Pro, Max, Team and Enterprise. Connecting apps to artifacts requires Pro, Max, Team or Enterprise on web or desktop. That general availability does not establish access to every legal template or third-party service. The legal announcement does not provide a complete per-template entitlement table.
Artifacts require the code execution and file creation capability to be enabled. Connected tools need initial approval, and users can disable individual tools. Tools requiring approval for every action are unavailable to artifacts. Each person connects their own apps, including when opening a shared artifact. Organization owners can restrict this capability.
Sharing a workflow is not sharing unlimited access
According to Anthropic’s sharing guide, artifacts begin private. Team and Enterprise owners control external sharing. A viewer normally uses their own source connections rather than inheriting the creator’s access. Stored shared information is a separate consideration, so inspect what an artifact saves before entering sensitive material.
External email invitees cannot use parts powered by Claude or connectors. Link sharing also has restrictions for artifacts using Claude or connected apps. Sharing settings must be changed on the web or desktop, not mobile. Those boundaries matter when a reusable internal workflow is intended for a client or outside partner.
The practical takeaway is to evaluate the output and the recipient experience separately. Keep professional review in the workflow, confirm who can open the artifact and its underlying material, and do not treat a source link as a guarantee that a generated conclusion is correct.
