You walk out of a meeting with messy notes, and you leave with a meeting summary and a deck. This chapter shows how, and what your readers see when you share.
Projects (workspaces with files and instructions) are in chapter 3. Here, we talk about what comes out of Claude.
The five templates
Artifacts are introduced in chapter 1. You edit them yourself or ask Claude to, then you share or export them. They all live in the Artifacts tab.
The starting point of an artifact. Each template knows how to produce one kind of deliverable: Docs makes text, Slides makes decks, Dashboards makes dashboards. You pick it in the Artifacts tab, or you just ask in the conversation and Claude uses it.
Since September 16, 2026, there are five of them:
| Template | What it produces | Status in October 2026 | Plans |
|---|---|---|---|
| Docs | Rich text documents, with tabs | Out of beta on October 8, 2026 | All, Free included |
| Slides | Presentation decks | Out of beta on October 8, 2026 | All, Free included |
| Design | Mockups, websites, visuals | Out of beta on October 8, 2026 | All, Free included |
| Dashboards | Dashboards connected to your data | Beta since October 8, 2026 | Pro, Max, Team, Enterprise |
| Motion | Animations exported as MP4 | Beta since October 8, 2026 | Team and Enterprise |
Design and Motion have their own chapter: chapter 5.
Prerequisite: artifacts need the "Cloud code execution and file creation" option, in Settings > Capabilities. On Team and Enterprise, the owner turns it on in the organization settings. On Enterprise, Docs, Slides and Design are on by default starting October 15, 2026.
Claude Docs
Rich text documents, with several tabs if you want to split the parts.
To get started:
- In a conversation, type
/docsfollowed by what you want, or use the Output > Docs menu. - Claude writes the document from the conversation, your files or your connectors.
- You edit right inside it. You and Claude can write at the same time, like in Google Docs.
What you can do next:
- Comment section by section. Mention
@Claudein a comment ("@Claude cut this paragraph in half") and it applies the change. Claude also leaves its own comments. - Charts and diagrams from your connectors. Careful, they don't refresh on their own: they're a snapshot of your data at the time they were created.
- Export to Word, PDF, Markdown, or to Google Docs.
- Share by link on Free, Pro and Max. Your reader needs a Claude account to open it. Only two levels, view or edit: no "comment only" access for now. On Team and Enterprise, a Doc doesn't leave the organization, neither by link nor by email invite.
- Watch out when deleting. Deleting a Doc is permanent. No trash, and nobody can open it anymore.
Claude Slides
Decks Claude builds from your notes or from the conversation.
- You edit the slides right in the window.
- You present from Claude, without going through PowerPoint.
- Export to PPTX or PDF, or send to Google Slides, where the deck stays editable.
If you code, Claude Code has the equivalent: /slides followed by your brief creates a Claude Slides artifact.
Fix one passage without regenerating everything
Since June 12, 2026, you can edit a Claude draft in place. You highlight a passage, type the change, and Claude rewrites that spot without touching the rest.
Make it a habit. Asking "redo the document with this change" makes Claude rewrite the whole text, with the risk that it moves passages you'd already approved. And it uses a lot more.
When an artifact becomes a small app
An artifact can go further than a static document. Look at these three options before you share:
| Option | What it does |
|---|---|
| Connect apps | The artifact reads your tools. Each reader connects their own accounts. Pro and above. |
| Store data | The artifact keeps data, personal or shared. 20 MB max, text only. Pro and above. |
| AI artifact | The artifact calls Claude when someone uses it. |
When someone uses an AI artifact you shared, their own plan pays for the usage.
Dashboards (beta)
Since October 8, 2026, in beta on Pro, Max, Team and Enterprise. You connect a data source (BigQuery, Databricks, Snowflake, Redshift, ClickHouse or Salesforce) and ask for your dashboard in the conversation.
Each chart shows the query that produced it. Read it. It's the only way to check that "quarterly revenue" means the same thing to Claude and to your CFO.
Sharing an artifact
Every artifact starts private.
| Plan | Sharing options |
|---|---|
| Free | Docs can be shared by link. For other artifacts, the sharing help page doesn't mention a link on Free |
| Pro, Max | "Only you" or "Anyone with the link", plus email invites (beta) |
| Team, Enterprise | Internal to the organization by default. "Anyone with the link" only if an owner has turned on external sharing |
Three access levels: view, comment, edit. Docs only have two, view or edit. For a client, view is almost always enough. Sharing settings can be changed on the web or in the desktop app, not on mobile.
"Anyone with the link" means anyone who gets hold of the link, including through a forwarded email. No sensitive client data in an artifact shared this way.
Old artifacts
Artifacts created in chat before September 16, 2026 now carry the "legacy artifacts" label. If you're still working on one of them, the simplest move is to recreate it as a Doc or Slides to get comments, co-editing and exports.
On mobile
Since October 8, 2026, you can edit your docs, decks and designs from the mobile app. Handy for fixing a typo before a meeting. For bigger work, go back to your computer.
Walkthrough: from client meeting notes to a deck
You walk out of a meeting with Acme. You have messy notes and a steering committee in ten days.
-
Open a conversation in your "Client Acme" project (chapter 3) and paste your raw notes.
-
Type:
/docs Summary of today's Acme meeting: context, decisions, open points, next steps. Formal tone, one page max. -
Claude creates the Doc. You read it. One sentence says "budget approved" when it's actually conditional: you highlight it and type "budget approved subject to the October 20 committee".
-
On the "Next steps" section, you leave a comment: "@Claude turn this into a table with owner and date". It does.
-
You export to PDF to send to Acme. The share link also works on Pro or Max, but your contact will need a Claude account. On Team, a Doc doesn't leave your organization.
-
In the same conversation: "Make a 6-slide deck for the committee, based on this summary." Claude creates a Slides artifact.
-
You tweak two titles right in the slides, then you present from Claude or export to PPTX for your client who swears by PowerPoint.
The summary and the deck come from the same source. If a decision changes, you fix the Doc and ask Claude to carry it over to the deck.
When to use what
| You want... | Use |
|---|---|
| A text to review, comment on, send | Docs |
| A presentation | Slides |
| A visual, a mockup, a website, an animation | Design or Motion (chapter 5) |
| Track numbers stored in a database | Dashboards |
| A real app, a deployed website, a page generated from your code | Claude Code (chapter 6), which also publishes artifacts |
What Claude writes (output tokens) costs more than what it reads. A 15-page document or a 30-slide deck is a lot of output, and every full regeneration pays for all of it again. Fix in place and through comments. Chapter 11 gives the price gaps.
Question
Your client needs to review the Doc you just finished, and your team is on Claude Team. How do you get it to them?
Pick an answer to see the explanation.
Key takeaways
- Docs, Slides and Design: out of beta on October 8, 2026, on every plan.
- Highlight the passage to fix or leave an
@Claudecomment, instead of regenerating everything. - Every artifact starts private. Before you send a link, choose who gets access and with what rights. On Team, a Doc stays inside the organization, so for a client, export it.
- Whoever uses your shared AI artifact pays with their own plan.
- Read the query behind each chart in a Dashboard.