Claude Dashboards and Motion move into everyday reporting
Anthropic introduced Claude Dashboards and Claude Motion on October 8, 2026, extending Claude into business reporting and animated explainers. The launch announcement describes dashboards connected to services such as BigQuery, Snowflake and Salesforce, alongside animations made from editable code.
The practical question is how these tools fit into work people already have to defend and share. A chart needs a clear definition of its numbers. An explainer needs an agreed message. A colleague needs permission to open the result. Those checks should be part of the first trial, before a team adopts either tool for a recurring report.
Start with access and a specific question
Begin in the connector directory and review what the chosen service can read or change. On Team and Enterprise, an owner must first make the connector available. Users generally authenticate individually, although centrally managed authentication is an exception. Enable the relevant connector in the conversation. Anthropic’s connector guide says access normally follows the source account’s permissions. Custom connectors using a shared credential instead reach whatever that credential can access.
For an initial reporting trial, choose an existing account with access to only the required data. Owners can restrict connector actions so reading is allowed while writing is blocked. That gives a reporting experiment a narrower scope than a connector that can also modify the records being analyzed.
The artifact guide describes starting from Output in the message box or a template in the Artifacts tab. Dashboards is in beta on Pro, Max, Team and Enterprise. Motion is in beta on Team and Enterprise. Docs, Slides and Design are available on every plan, including Free.
A useful first brief would ask for weekly paid signups over the last eight complete weeks, grouped by channel, using the company’s agreed timezone and excluding test accounts. This is an illustrative brief, not an official product prompt. Defining those choices up front makes the output easier to compare with an existing report and gives a reviewer specific assumptions to challenge.
Check freshness and calculations before reuse
Each dashboard chart exposes its query and last refresh time. Keep those visible during review. Claude can revise artifacts through the conversation, and saved work remains in the Artifacts tab for later use. The same guide describes changing animation details such as wording, numbers and timing, then exporting an MP4.
The launch describes dashboards that stay current as source data changes. It does not specify a refresh interval or a latency guarantee. Treat freshness as something to verify for the connected source before using a dashboard in a meeting or operational decision.
For the signup example, compare the total with a trusted query, inspect how duplicate customers are counted, and check whether the current week is partial. Ask what happens when a source fails or returns no rows. Those are evaluation questions, not claims about automatic safeguards. A plausible chart can still answer a different question from the one the business intended.
Give Motion a finished message
Motion animates supplied text, charts, shapes and images through code. Anthropic says it does not create generated footage or synthetic people. That makes the launch relevant to explainers and presentation graphics built around material a team already has.
Settle the claim and numbers before polishing the animation. For a sales update, decide which comparison the audience should remember, how long they need to read it, and what conclusion the speaker will draw. After any revision, replay the full export to check labels, ordering, readability and timing. These are recommended editorial checks, not results from a hands on test.
Test sharing with the actual audience
Anthropic’s sharing guide says new artifacts start private and recipients need a Claude account. Artifacts that use connected apps or Claude cannot be shared through an anyone with the link audience. For a shared artifact that reads connected data, the viewer uses their own connections. Missing access produces an error for that part of the artifact rather than exposing the creator’s data.
An outside email invitation also has limits. Parts using connectors or Claude do not work for external invitees. Stored information can have a different audience because an artifact may use shared storage. Before distributing a report, check both what a recipient can retrieve and what has already been saved into the artifact. Test with an intended recipient’s account before promising a client or colleague a working dashboard.
Enterprise rollout needs several decisions
The administration guide requires cloud code execution and file creation before enabling Artifacts. Dashboards and Motion are off by default on Enterprise. Owners choose the templates in Organization settings under Artifacts. Docs, Slides and Design are scheduled to turn on by default for Enterprise on October 15, 2026, so administrators who want a different rollout should review those settings beforehand.
Sharing is a separate decision. External sharing controls links that anyone can open, while email invitations outside the organization have their own switch. Enterprise custom roles can narrow who starts a template, but they cannot override an organization switch that is off. Artifact work also uses existing Claude limits rather than a separate allowance. Include usage and access reviews in the trial instead of treating feature availability as a complete deployment plan.
Design users have a December deadline
The related Design migration guide sets December 14, 2026 as the closure date for standalone Claude Design. A migration started from the Artifacts page brings across the organization’s eligible design systems in one run. The originals remain in the standalone service until closure. Published systems that were not private become available to the organization, so review the migrated audience and default design system.
Projects are a separate issue. Anthropic says they continue working in the standalone version and that further project migration details are coming. Chats and comments are not carried over, and public project links stop working after closure. Save essential discussion before then. Projects can currently be exported individually through Share, Project HTML and the Project archive option. Do not assume that migrating the design system has preserved the surrounding project history.
The strongest first use is a small internal report with known data and a clear reviewer. Establish that the numbers, access and freshness meet the team’s needs, then decide whether animation adds clarity. That trial produces useful evidence about fit without committing the whole reporting process to a new beta.
