Source: ai-research/claude-blog-dashboards-and-motion-2026-10-08.md Product: Claude Dashboards (beta, paid plans), Claude Motion (beta, Team and Enterprise) URL: https://claude.com/resources/articles/dashboards-and-motion Published: 2026-10-08 October 2026 additions: creator and podcast field reports, cited inline in the First hands-on reports and Motion walkthrough sections. 2026-10-28 addition: raw/Claude_Motion_Will_Change_How_You_Work_Forever_8_Real_Use_Cases.md (Ben AI); see Motion business use cases. 2026-10-30 addition: the official launch video, raw/Introducing_Claude_Dashboards_and_Claude_Motion.md (see Launch video), and a plan-availability check against the live launch post. 2026-11-09 addition: raw/Anthropic_Just_Launched_Claude_DASHBOARDS_Master_it_in_14_mins.md (Robo Nuggets), raw/Claude_s_New_Artifacts_Are_Amazing_Master_it_in_15_minutes.md (Ben AI) and raw/Claude_2.0_Is_Here._EVERYTHING_in_15_Minutes.md (Futurepedia); see Building dashboards people use. 2026-11-13 addition: Anthropic’s 2026-11-10 launch post and Help Center guide for Claude Data (ai-research/claude-blog-sheets-whiteboards-data-2026-11-13.md, ai-research/anthropic-support-get-started-with-claude-data-2026-11-13.md), plus Ben AI’s walkthrough (raw/Anthropic_Just_Dropped_4_BIG_Updates_Master_it_in_15_min.md); see Generally available as Claude Data.

Name change: Claude Dashboards → Claude Data (November 10, 2026)

As of November 10, 2026, Claude Dashboards was renamed to Claude Data and reached general availability (GA). Enterprise organizations get Claude Data on by default starting November 20, 2026 per the launch post (the Help Center guide says November 19). ^[ambiguous] The companion article Claude Sheets, Whiteboards and Data uses the new name and covers the full November 10 artifact wave. Replace “Dashboards” with “Data” in the current UI; all setup steps and configuration in this article remain accurate. Source: ai-research/claude-blog-sheets-whiteboards-data-2026-11-10.md.

Two new Artifact types launched in October 2026: Dashboards (live data connected to a BI-style chart builder) and Motion (code-based animation for short explainer videos). Also: Docs, Slides, and Design moved out of beta to all plans, and the standalone Claude Design site at claude.ai/design merged into main Claude with a December 14 2026 cutoff.

Key Takeaways

  • Claude Dashboards: connect a data warehouse, ask a plain-language question, get a live-updating dashboard. Each number shows its underlying query; supported data sources include BigQuery, Snowflake, Redshift, ClickHouse, Databricks.
  • Claude Motion: type /motion to build short video-like animations from a prompt. Downloadable as MP4. Not AI-generated footage — Claude writes code that animates text, charts, shapes, and images.
  • Docs/Slides/Design: out of beta on all plans; 45 million docs/decks/designs created since launch. Decks export to Google Slides as editable files.
  • Docs and Slides in practice (Brock Mesarich, September 2026): Docs have editable tables, a checklist button and multiple tabs; Slides have a present mode with speaker notes and export to Canva, Gamma and Miro or download as HTML, PDF or PowerPoint.
  • Enterprise: Artifacts support CMEK; admins choose which templates their org uses.
  • Admin note: Dashboards and Motion are off by default — enable under Organization settings > Artifacts.
  • Update 2026-11-13: Dashboards is now Claude Data and generally available (2026-11-10). It is on by default on Team plans and turns on by default on Enterprise on 2026-11-20 per the launch post, or 2026-11-19 per the Help Center guide. ^[ambiguous] New formats, certified queries and live sharing are in Claude Sheets, Whiteboards and Data; a summary is under Generally available as Claude Data below.

Launch video (2026-10-08)

Source: raw/Introducing_Claude_Dashboards_and_Claude_Motion.md — Anthropic, “Introducing Claude Dashboards and Claude Motion”, youtube.com/watch?v=en0GuyhieQk, 1:22, uploaded 2026-10-08. The auto-captions write “Claude” as “Quad”.

The video shows the two types used one after the other on one problem:

  • The setup. The presenter plays the operations lead at a bike-share company: “every weekday, the docks on the hill are empty by 8:15.”
  • Dashboard first. Claude pulls “a year of ride data from our data warehouse” and lays it out as a dashboard. Looking at it, “a story takes shape.”
  • Then Motion, from the dashboard. To explain the finding at the next all-hands, they ask Claude to turn the dashboard into an animation, and Claude “turns it into an animated narrative.”
  • Steer with comments on the video. “I can continue to tweak it and steer it with comments if I want to, right there on the video.” Colleagues it is sent to “can comment, too.”
  • Hand off. If the team wants to go further, “we can export it straight into their design tools.” The video does not name which tools; the launch post’s list is under Claude Motion below.

The pattern to copy is to find the finding in a Dashboard, then explain it in a Motion clip built from that dashboard, in the same conversation.

Claude Dashboards (beta, paid plans)

Connect to a company data platform, ask a question in plain language, get a dashboard that stays current as data changes.

Supported data sources: Amazon Redshift, BigQuery, ClickHouse, Databricks, Snowflake. Also works with other Claude connectors (e.g., Salesforce for opportunities).

Transparency features:

  • Click any number to see its underlying query.
  • Each chart shows when data was last refreshed.

BI handoff: Send dashboards to Amplitude, Grafana, Hex, Mixpanel, Omni, Perplexity, PostHog, or Sigma. Coming soon: Databricks Genie, Looker, monday.com, Tableau.

Example prompt: "Build a dashboard of this quarter's revenue by region"

Claude Motion (beta, Team and Enterprise)

Access: Type /motion in the Claude message box.

How it works: Claude writes code that animates text, charts, shapes, and images. Not a video generation model — no AI-generated footage or people. Animations are editable in a built-in editor or by prompting Claude, and downloadable as MP4.

Use cases:

  • 30-second all-hands explainer from a quarterly report
  • Animated chart for a board deck
  • Product walkthrough for customer onboarding

Video tool handoff: Adobe, Descript, HeyGen, Higgsfield, invideo, Luma AI, Runway. Coming soon: Canva, Captions.

Example prompt: "Animate how our pricing plans compare for the sales kickoff"

Docs, Slides, and Design — out of beta

Available on all plans. Over 45 million docs, decks, and designs created since launch.

  • Plan availability, in order. Anthropic’s September recap video, uploaded 2026-10-07, says “Docs, Slides, and Design are available on all paid plans today” (raw/What_s_new_in_Claude_-_September_recap.md). The next day’s launch post took the beta label off and put them “on every Claude plan, including Free” (checked on the live page, claude.com/resources/articles/dashboards-and-motion, 2026-10-30). These two statements describe consecutive days, so they do not conflict.

  • Enterprise default. Per the same live page, Docs, Slides and Design “turn on by default October 15” for Enterprise organizations, or admins can turn them on sooner. Dashboards and Motion stay off until an admin enables them.

  • Collaboration: Teams and Claude can edit the same doc, deck, design, or dashboard simultaneously.

  • Sharing: Can share outside org if admin allows.

  • Exports: PowerPoint and PDF; decks export to Google Slides as editable files.

  • Mobile: All three editable in the Claude mobile app.

  • Enterprise: CMEK support; admins choose which templates their org uses.

Note for decks sent by email/attachment: The Slides Artifact type downloads as .pptx or PDF — no need for a separate file.

Docs and Slides walkthrough — Brock Mesarich (2026-09-17)

Source: raw/Anthropic_Just_Dropped_Claude_2.0_Full_Breakdown.md. Brock Mesarich, “Anthropic Just Dropped Claude 2.0 Full Breakdown”, youtube.com/watch?v=lrsW8k-dHSk, YouTube, uploaded 2026-09-17, before the out-of-beta post above. One creator’s test; the affiliate promotion in his Zapier segment is omitted.

The Output menu. Brock Mesarich shows Docs, Slides and Design as options under an Output menu in the message box, in both the web app and the Claude desktop app. In Cowork mode the same box also has a project picker and an approvals setting: manual, automatic, or skip all approvals. He expects chat and Cowork to merge into one mode, with Claude routing each request, but his account still showed the toggle when he recorded.

Docs. His test was a demo-client CSV with the prompt “turn this into a document that I can edit.”

  • The document builds live in an artifact pane on the right.
  • The layout looks like Notion: a title, a date and an @-mention byline, then a summary of the CSV and a table.
  • You edit it by hand. He changed a client’s status to “past due” in the table and described it as an Excel file “mixed with like a notion document.”
  • A checklist button turns content into a checklist.
  • A document can have several tabs. He added one named “past clients”; you fill a tab yourself or ask Claude to.
  • The Doc is an artifact, so it can be shared.

Slides. Same CSV, asking for “a slideshow that could visualize all of this data.”

  • Choose a design style before you prompt. The list includes design systems you set up in Claude Design; he picked his own, “Bramble”.
  • He edits slides “as if we were using something like Google Docs”: change text color, edit, add or remove text, and drag in an image.
  • Present opens present mode with speaker notes, which you can add for a real presentation.
  • Share gives two routes. Copy link shares the artifact. Export sends the deck to Canva, Gamma, Miro or “other different AI platforms”, or downloads it as an HTML webpage, a PDF, or a PowerPoint file. He downloaded the PDF.
  • His verdict on the deck: “pretty solid”, though it “definitely looks like AI generated this.”

Docs fed by a connector. His closing demo pulled Drip email-campaign stats through the Zapier MCP into a Doc; the setup is in Claude Connectors.

Claude Design migration

Previously at claude.ai/design. As of September 16 2026, Design is inside every Claude conversation. The standalone site stays available until December 14, 2026. Migrate team design systems using the “Migrate team design systems” button on the Artifacts page.

First hands-on reports (October 2026)

Added 2026-10-27 from creator videos and podcasts fetched 2026-10-21. These are single-user tests, not first-party claims.

Where to find them. Both appear as new types under Artifacts in the left sidebar, as well as through /motion (raw/Anthropic_Just_Dropped_Claude_Motion_Dashboards_+_More_AI_News.md). Plan access matches the launch post: Motion is Team and Enterprise only, and Dashboards is on every paid plan, Pro included.

A Dashboard is an Artifact built from a template. The same creator quotes Anthropic’s help center: a dashboard “is an artifact… just built from a new dashboard’s template.” The template adds the per-chart query view and the last-refreshed time. That answers the obvious question of how it differs from asking Claude for a dashboard artifact, which was already possible.

Data sources beyond warehouses. The creator built an Instagram post-analytics dashboard through a social-scheduling platform’s MCP connector, a tool he promotes with a link in his description. The launch post names warehouses plus “other Claude connectors”. In practice, any connector that returns data can feed a dashboard. ^[inferred] The AI Daily Brief describes the sources as “a CRM or accounting software” (raw/AI_s_First_Full_Field-Level_Disruption.md). The first-party list above remains the authoritative one.

Motion examples from the same creator:

  • A YouTube audience-retention CSV became a 30-second “where viewers leave” explainer.
  • A follower-growth CSV became an animated “city” that grows month by month.
  • Higgsfield Katana, which Higgsfield says is “powered by Claude Motion”, runs inside Claude through the Higgsfield MCP with /katana. One generation took about 20 minutes, and he judged the output much better than plain Motion. See Higgsfield MCP.

Other field reports:

  • A seven-hour data run. Gavin Purcell (AI For Humans) asked Claude, on Opus 5.5, to “go find the last 100 years of movies data” and chart how genres changed. It took 7 hours and produced an interactive chart plus a set of findings. He frames it as presentation work that used to leave Claude (raw/Gemini_4_Argon_Meta_Muse_Wonder_Are_Good._Not_Great..md).
  • Give it a large brief. Anthropic’s Robert B, relayed by The AI Daily Brief: “Try giving it bigger briefs than you think it can handle.” Drew Fallon of Iris Finance made an animated product demo: “A year ago, this would cost tens of thousands of dollars.”
  • Max subscribers are left out of Motion. Matt Wolfe, on the $200 Max plan, points out that Max is sold with “early access to advanced Claude features”, yet Motion went to Team and Enterprise only. His workaround is to have Claude write the animation in JavaScript, or to use HyperFrames or Remotion (raw/AI_News_-_Haiku-5.5_Visual_ChatGPT_Grok_s_New_Trick_and_more.md).

Motion walkthrough — Robo Nuggets (2026-10-16)

Source: raw/Claude_MOTION_is_Unreal_for_Video._Master_it_in_12_minutes..md. Jay (Robo Nuggets), “Claude MOTION is Unreal for Video. Master it in 12 minutes.”, youtube.com/watch?v=Eg08Lr3zqdw, 12:08, YouTube, published 2026-10-16. This is one creator’s walkthrough, and the community pitch is omitted. His demo is a 20-second ad for a small-batch coffee roaster.

Interface and workflow:

  • Where it lives. In the Claude desktop app: Artifacts in the sidebar, then the Motion button next to Dashboard. Or type /motion, or pick Motion from the output menu, in any chat. Chat is on the left, the video preview on the right.
  • Plan in a normal chat first. Give Claude the rough idea, plus reference images, your brand site, or a video whose style you want. Go back and forth until it produces a detailed prompt covering the look, the scenes and their timing. Then open Motion in the same session and paste that prompt in. His reason: the result comes back “much closer to what we had in mind” and not off brief.
  • His model setting: Opus 5.5 on extra-high effort. The scene list appears in the right sidebar, and a build takes “around 1 to 4 minutes” depending on complexity.
  • Tweaks panel (bottom right). It lists every word in the current scene. Retype a brand name or a price (22 in his demo) and the video updates as you type. Scene length, speed and scene count are adjustable here too.
  • Comment on an element. For changes without words, click the comment button, click the object in the preview, and describe the change (“make it an iced coffee with ice cubes”). Claude reworks that piece only, and everything else stays identical.
  • Share and export. Share sends the project to teammates, who can duplicate it and have their own Claude edit it. Export gives MP4 with a choice of resolution, frame rate and quality; asking Claude to export does the same.
  • Cost. No separate charge. Each animation counts toward your plan’s usage limits, and longer, more complex ones use more. He notes Anthropic has not said how many videos a plan covers.
  • His analogy. A video model sells you “a finished cake”: a typo means a new generation. Motion gives you “the recipe”: every word, color, movement and timing is code, so you change one line and the rest comes out the same. The flip side is that it only draws text, shapes, charts and your own images.

Adding generated footage. Connect Claude to image and video models; Jay uses Kie.ai through a community “Key MCP” connector set up with an API key. He prices GPT Image 2 there at “about 5 US cents an image” and says he is not sponsored. Two patterns:

  • Footage first. Have Claude generate a realistic photo or clip (a roastery shot, beans pouring), then build the Motion animation over it. The words stay editable in Tweaks without regenerating the footage.
  • Motion as storyboard. Build the scenes in Motion, then pass them to a video model such as Seedance, which restyles each scene into a moving shot (his example used a soft hand-painted anime look). See Seedance via fal.ai for the API side.

Without Team or Enterprise. His alternatives are HyperFrames, which installs as a plugin and has a browser studio for scrubbing and edits, or a self-built local editing app. His view: Motion renders in Anthropic’s cloud and is usually faster, while HyperFrames and local rigs render on your own CPU. The workflow behind his self-built rig is in animate skill playbook.

Motion business use cases — Ben AI (2026-10-15)

Added 2026-10-28. Source: raw/Claude_Motion_Will_Change_How_You_Work_Forever_8_Real_Use_Cases.md. Creator: Ben AI · URL: https://www.youtube.com/watch?v=KIiayWHqf2c · Duration: 17:06 · Platform: YouTube · Uploaded: 2026-10-15. One agency founder’s uses, mostly from his own business; his community pitch is left out.

Where he runs it. Motion appears under Artifacts in the Claude desktop app, in both Cowork and Claude Code. He built his longest demo in the Code tab. He says a Team plan needs at least two seats, so trying it costs “$40”. That figure is his, and it isn’t checked here.

Editor details beyond the walkthrough above:

  • Tweaks work per scene and cover style, fonts, on-screen text, scene duration and speed.
  • Download is MP4 or GIF. A shared video appears in teammates’ live artifacts tab.
  • Motion can’t carry a voice track itself. His workaround is to ask Claude to “add a voice-over with ElevenLabs and send me the MP4 here”. Claude combines the video with the generated audio and returns an MP4 in the chat. For a YouTube Short he instead had Claude cut the audio from his original video.
  • He found output in Anthropic’s own brand style looked better than in his, and guesses “probably cuz it’s trained on it”. That is speculation.

Three habits he repeats across the use cases:

  • Storyboard first for anything longer than a short clip, including the captions and voice-over script when there is narration. Iterate on it, then build.
  • Give a reference video whose animation style you want followed.
  • Apply a design system so output is on-brand without describing it each time.

The eight use cases:

  1. Data into an animated explainer. His CRM leads, exported to a Google Sheet, became a 60-second ideal-customer-profile video: lead volume, sources, company sizes, wins and losses. One prompt.
  2. Product or service demo. A 90-second demo of his app. He told Claude the app was installed on his Mac and to “open it and take screenshots of every screen you need”, which it did through computer use. He gave a reference demo, and it took two storyboard iterations.
  3. Client onboarding tutorials. A 2-minute getting-started video in five chapters, with the brief “write the voice-over script, one short sentence per step, and show each sentence as a caption on screen”. He later cut it into 20 to 30 second clips for a tutorial page and is moving the narration to his own ElevenLabs voice clone.
  4. Social shorts from long videos. “Find the best 30-45 seconds where I explain one of the prompting rules on its own”, in 9:16, with three reference reels for style, using his original audio.
  5. Weekly analytics video to Slack. A 60 to 90 second video covering YouTube, revenue, email, community and website. It pulls the last 7 days through connectors and compares them with the 7 before. After a storyboard round on which metrics to show, he asked: “Can you create a scheduled task to recreate this exact video in this format every Monday at 8:00 a.m. and post it in Slack into the team channel?”
  6. Client progress reports. It read Fireflies call transcripts and his project-management tool, then listed what was agreed, done, in progress and still to do, with due dates. The goal line: the client “should watch this and in 60 seconds know exactly where his projects stand.” He plans to send these alongside, or instead of, PDF reports.
  7. Deck to video. His weekly internal marketing deck became a 45 to 60 second video, with each slide as one scene and every chart animated. He suggests building the slide template first and then converting slides, because it is more efficient.
  8. Team update video. Every Monday, a 60-second video of what each person worked on and their focus this week, built from meeting transcripts, task lists and Slack. It can be scheduled the same way as the analytics video.

The marketing-relevant pattern: Motion plus a scheduled task turns a recurring report into a recurring video, with no video model involved. ^[inferred] For the dashboard version of the same report, see Ben AI’s six-step dashboard process.

Building dashboards people use — Robo Nuggets and Ben AI (added 2026-11-09)

Sources: Jay (Robo Nuggets), “Anthropic Just Launched Claude DASHBOARDS (Master it in 14 mins)”, youtube.com/watch?v=9RPUZLJ4v7Q, 14:48, uploaded 2026-11-05 (raw/Anthropic_Just_Launched_Claude_DASHBOARDS_Master_it_in_14_mins.md). Ben AI, “Claude’s New Artifacts Are Amazing (Master it in 15 minutes)”, youtube.com/watch?v=Lodg0K3_zqk, 14:54, uploaded 2026-11-09 (raw/Claude_s_New_Artifacts_Are_Amazing_Master_it_in_15_minutes.md); its Docs, Slides and Design parts are in Claude Docs and Claude Slides. Both are creator videos; their community pitches are omitted.

What both report about the product. The two accounts agree with each other and with the launch post above.

  • Where to start. Artifacts in the sidebar, then the Dashboard button; or ask for a dashboard in any chat; Ben also uses /dashboard. Every dashboard you make is saved under Artifacts.
  • Plans. Jay: on every paid plan; on Enterprise it is off by default while in beta, so the account owner must turn it on.
  • Each dashboard stores its own data. Both give the same limits: up to 100 MB of data (the numbers and text) plus 1 GB of files (Jay: images and icons; Ben: files such as CSVs). Ben says this makes refreshes efficient because only new data is pulled. The launch post does not give these limits.
  • A shared dashboard uses the viewer’s connectors. Jay: by default it uses “the connections and the connectors of whoever opens it.” Ben: “a teammate without your Stripe connector won’t see your revenue.” This matches the per-viewer connector calls in Claude Artifacts. Jay’s way around it is to store the data inside the dashboard, so viewers do not need the same connectors.
  • Traceable numbers. Ben: click any number to see “the exact query, formula, and the raw data behind it.”
  • Change it by comment. Jay’s example: click the margin figure, comment that you want gross margin compared with last quarter, and send it to Claude.
  • A chat box inside the dashboard. Turn on Settings, Capabilities, “AI-powered artifacts”, then ask Claude to add a chat box. Anyone with the link can ask a question and Claude answers from the dashboard’s data, including teammates who do not use Claude.
  • Warehouses. Jay names Snowflake, BigQuery and Databricks, added through Customize, then Connectors, or by asking Claude to add them.

Jay’s five pillars: why, where, what, how, when.

  1. Why: the goal. He takes three dashboard types from the 2006 book Information Dashboard Design:

    • Operational: what is happening now (open support tickets by how long they have waited).
    • Strategic: are we on track (monthly revenue against the annual goal).
    • Analytical: what would get us there faster (customers who cancel compared with those who stay).

    Have Claude interview you one question at a time until the goal is clear, before it builds anything and spends tokens.

  2. Where: data sources. He reverses the old order: connect every source first, even minor ones, then work with Claude to trim. Two tips:

    • No connector? Have Claude build a CLI for the app. His example is MyFitnessPal; see Printing Press for a tool that does this.
    • Paying only for the data? Ask Claude to reverse-engineer the metric. His example is VidIQ’s outlier score, which is roughly a video’s views against the channel’s average. Check the results roughly match before cancelling the subscription.
  3. What: metrics that matter. Give Claude the dashboard’s goal and your business goals and ask which metrics matter. Put the top three to five as large headline numbers at the top (he calls them BANs, “big aggregate numbers”) and the rest below, with expandable “more info” sections.

  4. How: presentation. Avoid “chart junk”: 3D gauges, speedometers, and pie charts with many categories. A dashboard that shows all the data is “a glorified spreadsheet.” Pick a reference design system from styles.refero.design (his choice, because each comes with a markdown file an agent can read), Mobbin or Dribbble. Screenshot two or three, swap in your brand colours, and ask Claude for mock-up layouts to choose from. You can also send Claude the styles.refero link and ask for three designs that suit your business (Refero Styles).

  5. When: refresh. A dashboard only for you can refresh when opened, so it uses no tokens when unused. A team dashboard should refresh on a schedule, for example every weekday at 7:00 a.m. with yesterday’s numbers.

On security, Jay’s view is that storing data in a dashboard means trusting Anthropic the way a business already trusts SharePoint, Gmail or Google Drive. Decide by how sensitive the data is.

Ben AI’s five steps and two uses.

  • Two kinds of dashboard:
    • A general one you check every day, week or month. His covers YouTube and his marketing channels.
    • One that answers a single question: why churn went up last quarter, which channel brought the best customers last month, or whether the last price increase cost customers. These used to need days or an analyst; he says they are worth building even for a short-term question.
  • His steps:
    1. Goal: “What decision should this dashboard help me make?” Keep it to one to three decisions, because “too many metrics is the number one reason people stop using a dashboard.”
    2. Metrics: five to ten at most. Brain-dump the ones you know and ask Claude to suggest more.
    3. Check the data: ask Claude to confirm it can get every metric and how it will count each one.
    4. Plan the design: paste two or three screenshots you like (Pinterest, Dribbble or Mobbin) and ask for two or three variations.
    5. Build: with /dashboard or a prompt. Finish with comments, then share through Share (it appears in teammates’ Artifacts tab) or by link.
  • His cap has tightened. In September he allowed up to 15 metrics (A Business Dashboard You’ll Actually Use); here it is five to ten.

Where they differ. Jay connects every source before choosing metrics. Ben chooses metrics first, then checks Claude can get them. Both are single-creator methods.

Motion, briefly. Ben’s overview repeats his October Motion advice (storyboard first, give a reference video) and names two editor details: a scene bar showing how long each scene lasts, and editing text directly on any frame. He also says you cannot add your own voice-over or MP3 files yet.

Rollout, per Futurepedia. In “Claude 2.0 Is Here. EVERYTHING in 15 Minutes” (raw/Claude_2.0_Is_Here._EVERYTHING_in_15_Minutes.md, uploaded 2026-11-03), Futurepedia says Dashboard and Motion are still in beta and that his plan, which he calls “Ultra”, did not show Motion yet. That fits Motion being Team and Enterprise only. “Ultra” is not a Claude plan name recorded elsewhere in this wiki. Resolved 2026-11-13: Ultra is the new name of the Max 20x plan ($200 a month), per Anthropic’s Help Center (ai-research/anthropic-support-what-is-the-ultra-plan-2026-11-13.md), so his account is a consumer plan without Motion, as expected.

Renamed to Data (2026-11-11, Eliot Prince). In raw/I_Stopped_Using_PowerPoint_Word_Excel._Claude_Does_It_All_Now.md, the Artifacts tab lists the dashboard type as Data (“previously called dashboards”). A data tab in the top right shows where each number came from, with the code, results and logs; the numbers are editable, and a refresh button re-pulls them. No first-party Anthropic source confirms the rename yet. See A Client Pitch Pack Built in Claude Artifacts. Confirmed 2026-11-13: Anthropic’s launch post dated 2026-11-10 makes Claude Dashboards generally available as Claude Data; see the next section.

Generally available as Claude Data (added 2026-11-13)

Sources: Anthropic’s launch post, “Introducing Claude Whiteboards, Claude Sheets, and Claude Data” (2026-11-10, ai-research/claude-blog-sheets-whiteboards-data-2026-11-13.md); the Help Center guide “Get started with Claude Data” (ai-research/anthropic-support-get-started-with-claude-data-2026-11-13.md); Ben AI’s walkthrough (raw/Anthropic_Just_Dropped_4_BIG_Updates_Master_it_in_15_min.md, https://www.youtube.com/watch?v=vyhzL1tW7rE). Full write-up: Claude Sheets, Whiteboards and Data.

  • Name and status. Claude Dashboards is now Claude Data and is out of beta. Anthropic’s reason for the rename is that the product covers more than dashboards. Existing dashboards keep working.
  • Plans and defaults. Pro, Max, Ultra, Team and Enterprise. On by default on Team; on by default on Enterprise from 2026-11-19 unless an owner has already saved a setting (Help Center; the launch post, re-fetched 2026-11-14, says November 20 ^[ambiguous]). This replaces the off-by-default admin note above for Data; Motion is unchanged.
  • Three more formats from the same data: Scrollyteller (a scrolling story), Visual short (a narrated short video) and Visual analysis (a written summary).
  • Certified queries (beta). A data team marks the official query for a metric; Claude reuses it in new dashboards and charts built on it carry a badge.
  • Live sharing (beta). A third answer to the viewer-connector problem described above. Setting a connector to “Your access” in the Sources menu lets people in your organisation see current results through your connection, limited to the dashboard’s own queries. Storing data in the dashboard, or having each viewer connect, still work.
  • Refresh changed. Dashboards used to reload on every open. They now cache, with a refresh cadence set per dashboard, and refresh when opened only if due. The Help Center says Data does not refresh on a schedule of its own, so Jay’s scheduled 7:00 a.m. refresh would need a scheduled task.
  • Also new: design systems apply to Data artifacts, and version history shows who edited and restores an earlier version.
  • Partners named for Claude Data: Amplitude, Mixpanel, Omni, PostHog, Sigma and ThoughtSpot. The October post’s hand-off list was longer and included Grafana, Hex and Perplexity; the new post does not say whether those still apply.

Try It

  1. Turn a CSV you already report on into a Motion clip. Retention, funnel or revenue-by-month data works well. Ask for a 30-second explainer, then edit the wording or numbers by prompting rather than starting again.
  2. Point a Dashboard at a connector you already use. Use a CRM, analytics tool or scheduling platform, not only a warehouse. Click a number to check its query before you share the dashboard.
  3. On Max or Pro without Motion, ask Claude for a coded animation, or use another Claude motion-graphics method. Futurepedia’s style-prompt method is one worked example: Code-Drawn Explainer Videos in Claude Chat.
  4. Admins: both types are off by default. Enable them under Organization settings > Artifacts.
  5. Plan in chat before you open Motion. Agree the look, scenes and timing in a normal chat, then paste the resulting prompt into /motion. Fix wording with Tweaks and individual objects with comments, instead of regenerating.
  6. Schedule one recurring video. Build a weekly results video once, agree a storyboard on which metrics it shows, then ask Claude to recreate it every Monday and post it to your team’s Slack channel (Ben AI’s use case 5).
  7. Name the dashboard’s job before prompting. Pick operational, strategic or analytical (Jay), and answer “what decision should this help me make?” (Ben). Keep three to five headline numbers at the top.
  8. Decide how a team dashboard gets its data before you share it. Either store the data inside the dashboard, so viewers need no connectors, or pull live, so each viewer needs the same connectors. Then set it to refresh on open or on a schedule. Since 2026-11-10 there is a third route inside an organisation: live sharing with “Your access” (beta).

Open Questions

  • Team plan minimum. Ben AI says a Team plan needs a minimum of two seats and costs $40 to try Motion. Neither the seat minimum nor the price is checked against Anthropic’s pricing page.
  • Audio. Ben AI says Motion can’t hold a voice track, so narration is added by Claude after export. Whether Anthropic plans native audio isn’t stated in the launch post.
  • Dashboard storage limits. The 100 MB data and 1 GB file limits come from two creators who agree; no Anthropic source in this wiki states them.
  • “Ultra” plan. Futurepedia says he is on an “Ultra” plan. No Claude plan by that name is recorded in this wiki; it may be a caption error or a plan not yet covered. Resolved 2026-11-13: Ultra is the renamed Max 20x plan; see Claude Usage Limits Playbook.
  • October hand-off partners. Whether Grafana, Hex, Perplexity and the “coming soon” tools from the October post still apply to Claude Data is not stated in the November post.