Claude Artifacts

Claude artifacts turn useful answers into things your team can open and reuse: a working document, a dashboard, or a small interactive tool. You can keep improving the result, find it outside the original conversation, and share access when it is ready. The practical change for a small company is fewer handoffs between having an answer and giving colleagues something they can use.

Start with a recurring internal job, such as the weekly sales review or a customer handover procedure. A reusable artifact gives that job a home. The question becomes who owns the content, who can change it, and when the underlying information needs updating.

The August 19, 2026 change matters specifically for Cowork artifacts. Newer ones follow the current saved-artifact system; older live artifacts follow a separate migration path. Legacy artifacts made in chat are another category, with their own publishing controls. Anthropic’s live-artifact guide

What Claude Artifacts Are Now

An artifact is a separate piece of work alongside your conversation. Think of the chat as the discussion around a workbench and the artifact as the document or tool being built on it. Claude can create documents, single-page websites, code, diagrams, dashboards, and interactive tools this way. What artifacts are

There are also named starting templates. Docs is for editable team documents, Slides for presentations, and Design for visuals, prototypes, and one-pagers. Those templates are available on every Claude plan, including Free. Dashboards is in beta on Pro, Max, Team, and Enterprise; Motion, for animations, is in beta on Team and Enterprise. Claude’s artifacts product page

A small custom dashboard and the named Dashboards template are different starting points. The worked example below asks for a simple dashboard from supplied sample data. It does not assume access to the paid Dashboards beta or a connected business system.

Make, Edit, and Find an Artifact

Use Claude on the web or Claude Desktop for the full workflow, including sharing settings. On mobile, Anthropic also supports creating, viewing, and editing docs, decks, and designs; changing sharing settings requires web or desktop. Supported surfaces

1. Enable the required capability. On Free, Pro, or Max, open Settings > Capabilities and enable Cloud code execution and file creation. On Team or Enterprise, this is under Organization settings > Capabilities. An organization owner also manages Artifacts under Organization settings > Artifacts. Requirements, organization setup
2. Describe a deliverable. Ask for an artifact in your conversation, naming its reader, source material, and purpose. For a template, choose Output in the message box and select the type, or open Artifacts in the sidebar and choose a template there. Creation options
3. Inspect the result beside the conversation. Check the content and try any controls. A sensible first edit is specific: “Keep the calculations; replace the chart with a table grouped by account owner.”
4. Edit through Claude or directly. Ask for changes in chat. Template artifacts also support direct editing, such as typing in a doc or adjusting a slide. In a doc or Markdown document, select the passage, choose Edit with Claude, and describe the change. Editing artifacts
5. Return through the sidebar. Your work is saved in Artifacts, accessible from any conversation. You do not need to remember which chat produced it. For an artifact someone invited you to, bookmark its link or reopen the invitation email. Finding your work, reopening invitations

If the result belongs in another tool, template artifacts offer Export. Docs can go to Word, PDF, Markdown, or Google Docs; decks can go to PowerPoint, PDF, or Google Slides. Sharing an editable artifact and exporting a file serve different handoff needs. Export options

Share an Artifact With the Right People

Current artifacts start private, and opening a shared one requires a Claude account. “Anyone with the link” does not mean an anonymous visitor can open it. The exception is a publicly published legacy chat artifact. Sharing and account requirements

The current sharing workflow is:

1. Open the artifact and click Share.
2. On Team or Enterprise, add colleagues and set their access. Enterprise can also add groups.
3. Under Who has access, choose the audience. Pro and Max offer Only you or Anyone with the link. Team and Enterprise offer invited people, anyone in the organization, or anyone with the link when an owner has allowed it.
4. Copy the link and send it through your normal team channel. Sharing steps

For a named email invitation on an eligible artifact, enter the address in the Share dialog, select its Invite option, choose access, then click Invite. The recipient must sign in with that email address. Outside invitations are a beta feature, and Team or Enterprise owners control them separately from external link sharing. Email invitations

Which Plans Have Which Sharing Options?

This table follows Anthropic’s general sharing matrix, checked October 21, 2026. “Not listed” means the matrix does not include that option for the plan.

Source: Anthropic’s Share artifacts guide.

*There is a Docs-specific difference in Anthropic’s documentation: its Claude Docs guide explicitly includes Free, Pro, and Max for sharing a doc with anyone who has the link. Treat that as a statement about Docs, not a promise that Free can share every current artifact type.

Most artifacts offer view, comment, or edit access. Docs offer view or edit; editors can also comment. Give a reviewer view access unless their job requires changing the artifact. Access levels, Docs permissions

The audience restrictions matter more than the link button:

• Team and Enterprise default to internal sharing. An owner can enable external links globally or allow an individual artifact. External email invitations have a separate setting. Owner controls
• Connected or AI-powered artifacts cannot use “Anyone with the link.” Outside invitees also cannot use the parts that call Claude or use connectors. An internal tool is therefore not automatically suitable as a public customer app. Sharing restrictions
• Docs stay internal on Team and Enterprise. Docs also do not support external email invitations on any plan. Docs sharing

To restrict an artifact later, return to Share and change the audience. Remove named recipients separately when you want their access revoked. Stopping sharing

For plan selection, use Is Claude Free? and Claude Enterprise.

What Happened to Older Cowork and Chat Artifacts?

August 19 is the Cowork cutoff. Cowork artifacts created on or after August 19, 2026 follow the current system, are saved with your artifacts, and are available on web and desktop. Earlier live artifacts remain viewable and shareable, but cannot be edited in place. The older live experience is desktop-only. Cowork migration, surface availability

To update an old live artifact, open it, choose Share, and choose to republish it as a new artifact. If it already had a shared link, that link shows the new version; you can then edit the new artifact normally. Find older items in Artifacts, where they carry a Cowork label, and use Filter by to narrow the view. Republishing steps

Old live artifacts keep their old audience rules: organization-only links, with no public sharing or individual recipient selection. Anthropic’s migration guide says organizations using customer-managed encryption keys, or CMEK, zero data retention, or ZDR, and HIPAA-ready configurations keep using live artifacts. Live-artifact exceptions

That migration exception is not a blanket ban on every newer artifact feature. The current admin guide separately says artifacts are available with CMEK and describes an owner opt-in for templates in HIPAA-ready organizations. Those templates are outside the organization’s Business Associate Agreement and must not contain protected health information. Special configurations

September 16 is the legacy chat cutoff. Anthropic defines legacy chat artifacts as those made before September 16, 2026. They keep working, but new legacy artifacts cannot be created. On Free, Pro, and Max, open one and choose Publish to get its public link. On Team and Enterprise, the older workflow is Share, then Share & copy link. Sharing these chat artifacts also exposes files and attachments from their originating conversation; project-based artifacts require project access. Legacy definition, legacy publishing and sharing

Three Worked Business Examples With Prompts

These are illustrative recipes with invented inputs and expected results, not claims of a production deployment or a tested Claude session. They are ranked by how broadly useful they could be to a small company. Copy a prompt, inspect what Claude produces, then replace the sample material with your own approved inputs.

1. A Customer Handover Document

Best for: an operations or support lead whose colleagues repeatedly ask how to hand over unresolved customer work. The artifact could turn scattered notes into one editable procedure, with a named owner for every step.

Creation prompt:

Create a Claude Doc called Customer Handover. Its reader is a new support colleague. Use only these process notes: the support lead records the customer issue; the lead assigns an owner; that owner checks the proposed response; the owner records the handover before the next colleague takes over. Make sections for purpose, steps, owner, and unresolved questions. Put the steps in a table with Action, Owner, and Evidence columns. Do not invent response deadlines, approval rules, or customer policies. Mark missing details as To confirm. End with a reusable handover checklist.

Worked result to check: the table should contain the four supplied actions. “Records the issue” belongs to the support lead; response checking belongs to the assigned owner. The evidence field can request a record or link without inventing a ticketing system. An unresolved question should identify who accepts the handover, because the notes do not specify that person.

Edit prompt: “Add a handover-accepted step, owned by the receiving colleague. Keep every other responsibility unchanged.”

A Team or Enterprise operator could share this internally and give the process owner edit access. Docs support simultaneous editing, and direct edits save automatically. That makes this a useful candidate for a maintained procedure. Working together in Docs

2. A Weekly Sales Dashboard

Best for: a sales manager who repeatedly converts a small export into a meeting summary. The artifact could provide a consistent view and let colleagues filter the same supplied snapshot.

Creation prompt:

Build an interactive dashboard artifact for our weekly sales meeting using only this invented sample data: Ada, Qualified, 4 deals; Ada, Won, 2 deals; Ben, Qualified, 3 deals; Ben, Won, 1 deal. Add an owner filter, a deal-count chart by stage, and a source-data table. Show the total deal count and label the page Sample data, manual snapshot. Counts are already aggregated, so sum the counts rather than counting rows. Do not calculate a win rate or imply that the data refreshes automatically. Keep the underlying data easy to inspect.

Worked result to check: the unfiltered dashboard should show 10 deals, split into 7 Qualified and 3 Won. Filtering to Ada should show 6, including 2 Won. Four rows must not become four deals. A ratio of Won to this snapshot’s total would not, by itself, establish the company’s sales conversion rate.

Edit prompt: “Add a compact table comparing Ada and Ben. Keep the stage definitions and the manual-snapshot label.”

If the job later needs connected business data, assess the paid Dashboards template. Anthropic describes charts with the underlying query, meaning the instruction used to retrieve the data, and the last refresh time. That is a different workflow from this supplied-data example. Claude Dashboards overview

3. A One-Page Capacity Calculator

Best for: an agency or service-team lead deciding whether another project fits this week. The artifact could make the arithmetic visible before someone commits the team.

Creation prompt:

Create a one-page interactive capacity calculator artifact. Inputs: number of people, available hours per person this week, and total committed hours. Calculate total capacity as people multiplied by available hours, remaining hours as capacity minus committed hours, and utilization as committed hours divided by capacity. Use sample inputs of 3 people, 30 available hours each, and 72 committed hours. Label the sample clearly. Show the formulas. Reject negative inputs, allow committed hours above capacity, and show a clear over-capacity message in that case. If capacity is zero, show Not available for utilization instead of dividing by zero. Keep inputs temporary and include Reset; do not add storage, connectors, or AI features.

Worked result to check: the sample means 90 hours of capacity, 18 remaining, and 80% utilization. Change committed hours to 99 and it should show 9 hours over capacity. Setting people to zero should not produce a misleading percentage or crash the tool.

Edit prompt: “Add a plain sentence stating whether a proposed 10-hour task fits the remaining capacity. Keep that task size editable.”

This is a deliberately small calculation. The lead still has to account for skills, leave, and which person can do the work. A total-hours answer cannot make those staffing judgments.

Three More Uses Worth Trying

The next opportunities are narrower. Each could work well when someone owns the source material and reviews the output.

Claude Code’s session pages, Design and Slides, and artifacts that call Claude are documented capabilities. The business payoffs above are suggested applications, not measured results. AI-powered artifacts use the signed-in user’s own Claude limits and do not require an API key. Artifact capabilities

Where Cowork, Claude Code, Skills, and Connectors Fit

Cowork can produce the artifact during a larger task. Anthropic distinguishes sharing an individual artifact from sharing the Cowork session itself: sessions cannot be shared. Use the artifact as the deliverable people open afterward. Cowork’s current limits Our Claude Cowork guide covers the broader workflow.

Claude Code can turn session work into a live page. Anthropic’s current help page makes artifacts available on every plan that includes Claude Code. Examples include annotated code-change walkthroughs, dashboards from session data, and investigation timelines. The page starts at a private URL and updates as the session continues. You can also use /design or ask for a doc; a doc opens beside the work on desktop, or through a web link from the terminal. Artifacts in Claude Code

For repeatable instructions, see How to Use Claude Skills. For access to business systems, see Claude Connectors. In an artifact that uses connected apps, each viewer connects their own accounts. A shared link does not lend them your permissions; an inaccessible source produces an error. Connected artifacts

Two Things Worth Building Around Artifacts

The strongest opportunity is a service that creates and maintains a team’s operating playbooks. An operations lead could pay for the work of interviewing staff, resolving conflicting instructions, assigning owners, and turning the result into usable Docs. The smallest useful delivery is one recurring process, a reviewed document, and a routine for keeping it current.

DataForSEO’s US English keyword overview returned 14,800 estimated monthly Google searches for “standard operating procedure template” in this run on October 21, 2026. That measures interest in the job, not demand for Claude or proof that those searchers will pay. The hard part is getting the company’s actual process right. Generic templates are easy to copy; reliable process knowledge and maintenance are the reason to hire someone.

A second opportunity is a sales-review dashboard tailored to one recurring meeting. The buyer could be a small sales team that wants agreed metrics and an easy-to-review view. Start with one approved export, owner and stage filters, visible metric definitions, and a refresh procedure. Consider connected data only after people agree what each number means.

The same DataForSEO check returned 1,000 estimated monthly Google searches for “sales dashboard.” That supports interest in the category, not a revenue forecast. The catch is ongoing data quality, permissions, and maintenance. A polished chart cannot settle disagreements about whether a deal belongs in the pipeline.

I would start with the playbook service. It has the broader observed search interest and can deliver useful work without first solving live data connections. These are opportunities to validate with buyers, not claims that an artifact alone is a complete commercial product.

What Artifacts Do Not Solve

An editable output still needs an owner and a review habit. For a small team, the change is from “answer, copy, format, circulate another file” to “supply context, review the artifact, share access, maintain it.” That can remove repeated formatting and copying, but it does not establish a measured time saving for your workflow.

Choose data behavior deliberately. Paid plans support personal and shared artifact storage on web and desktop. Shared storage means other users can see the saved information. Anthropic states a 20 MB, text-only storage limit per artifact; that is a limit on this storage feature, not a universal file-upload or artifact-size limit. Artifact storage

Also separate an editable page from fresh data. Charts inside Claude Docs do not refresh themselves; ask Claude to retrieve the latest information. For dashboards, inspect the query and refresh information where available. Docs charts, dashboard transparency

My recommendation is to keep the first artifact away from business-critical recordkeeping. Use a procedure, a review dashboard, or a small calculator that a colleague can check against known inputs. Expand its responsibility only after the team understands its data, permissions, and failure cases.

What kinds of artifacts can Claude create?

Claude can create documents, code, single-page websites, diagrams, dashboards, and small interactive tools. Named templates include Docs, Slides, Design, Dashboards, and Motion, with availability varying by plan. Artifact types and availability

What are 5 examples of artifacts?

For a small business, five useful possibilities are a customer handover document, a weekly sales dashboard, a capacity calculator, a launch one-pager, and an onboarding practice tool. These are suggested workflows; the prompts above show how to specify the first three.

How do I write a standard operating procedure?

Start with a real task and the people who perform it. Supply the actual steps, owners, required evidence, and unresolved questions. Ask Claude for a Doc, review every instruction with the process owner, then share it with the people who need it. Claude Docs supports drafting, direct editing, and team collaboration. Creating and editing a Doc

Your Monday Move

Pick the handover procedure your team explains most often. Reserve a 30-minute review slot with its owner, use the first prompt with your real notes, and check every assigned responsibility. The time slot is a planning suggestion, not a promise about how long generation or review will take. Share the result internally with the appropriate access, then have a colleague find it and use it without your explanation.

That final step is the acceptance test: the work is useful when someone else can return to it and act on it.

If you want a recurring team workflow built around these outputs, we can help with AI automation.