Give your team a report to read, a prototype to explore, or evidence they can check. Artifacts keep the deliverable, its files and its versions connected to the work.
Package the result so the next person has what they need. Here are three ways a team could use artifacts.
Turn sourced findings into an HTML brief with charts and supporting files. Attach it to the project, then link it in the article task so the writer starts from the same evidence.
Next step: a draft grounded in the brief.Bundle a browser prototype with its HTML, CSS, JavaScript and images. Let a reviewer explore it in Work’s sandboxed viewer, then publish a new version as the idea develops.
Next step: a concrete design discussion.After approved work is executed, attach the report, screenshots and output files to the task. Record the checks and outcome so a reviewer can see what was delivered.
Next step: an informed completion review.Illustrative workflows and graphics. Your assistant or configured executor creates the content and carries out the work; an artifact holds the result.
Improve the deliverable without scattering copies across conversations.
Revised findings and source notes.
Current versionSupporting evidence included.
Earlier version retainedInitial research and outline.
Earlier version retainedKeep work inside the workspace, or create a link for an outside reviewer when you have permission to share.
A restricted link can be opened by anyone holding the link and any required password. Review the content and audience before sharing. Agent-created links require the sharing permission and access to the artifact; agents manage links for artifacts they published.
A connected assistant can publish an artifact, revise it, attach it to the work and share it when authorized. You decide what it should produce and which actions need approval.
MCP supplies tools. Scheduled or unattended work also needs a configured executor and wakeup mechanism. Connecting outside agents through MCP is part of Premium.
An artifact is a deliverable with its own files, versions and connection to the work. It can hold a report, prototype, document, image, PDF or data object and be attached to a Space, task, ticket, project, company or client, or kept in the account library.
Yes. An HTML artifact can include CSS, JavaScript, images and supporting files and opens in Work's sandboxed viewer. Markdown documents, PDFs, images, files and structured data are also supported. An artifact is a deliverable; it is not a deployment of a production website or a guarantee of external API access.
Publishing updated files creates a new version of the same artifact and retains earlier versions. The existing card points to the updated deliverable. A sharing link can follow the latest version or stay pinned to one version for a specific review.
Yes, when your permissions allow it. Create a public or restricted link, optionally set an expiry, or add a password to a restricted link. Anyone holding a restricted link and any required password can open it. Links can be revoked. Agent sharing requires artifacts.share and access to the artifact; agents manage links for artifacts they published.
Keep the report, the files and the handoff connected.