Separate legacy artifacts from the new system
Regular new Cowork artifacts have used the updated system since 19 August. Earlier live artifacts remain usable but are republished for changes. Anthropic lists exceptions for organizations using CMEK, ZDR or HIPAA configurations. Identify the system used by the actual account before migration.
Sharing is a separate data decision
Connected artifacts use the viewer’s permissions. Artifacts using connected apps or Claude questions remain internally shareable. This does not replace inspection of stored content. Test a dashboard with a second account: which values can it see, what stays hidden and how is missing access shown?
A dashboard needs a business contract
Define the meaning, time range, source and refresh behavior of each metric. Distinguish an empty result from zero and from a connection error. Inspect the actual view on small and large screens before sharing. Compare important values with their source; a visually finished interface is not yet an accepted business application.
Decision matrix
| Decision point | Proceed when | Stop when |
|---|---|---|
| Assignment boundary | Documented: data source, runtime, permissions, version and export. | Scope, data or accountability remains unresolved. |
| Workflow evidence | The review records the data source, version and permissions of a specific working state. The controlled export can be linked to that state and is checked for completeness and correct content. | There is only an unevaluated demo without acceptance evidence. |
| Operational control | Owner, approval, fallback and next review date are defined. | Avoid: using a live preview as a system of record. Without a traceable state and reviewed export, a live preview cannot serve as authoritative evidence or a system of record. |
Keep it verifiable
Primary sources
- Use artifacts in Claude CoworkSource checked:
