Field noteNov 11, 20266 min read1 source

Working with Claude Sheets, Whiteboards, and Interactive Connectors

In one minute

Anthropic says Claude can now help teams build spreadsheets, whiteboards and dashboards, while interactive connectors let partner apps appear inside Claude. The change extends the assistant from answering questions and generating documents into a shared workspace for structured work, with enterprise controls intended to constrain connected tools and data access.

What happened

Anthropic’s announcement introduces Claude Sheets, Claude Whiteboards and Claude Data, which was formerly called Dashboards. The company describes these as new artifact types that build on Claude’s existing ability to create documents, slide decks and designs, as well as Claude Motion, which it identifies as a beta product for turning content into short animations. The announcement does not state a release date beyond “starting today” for the described additions, nor does it specify pricing or a subscription tier for each artifact type.

Sheets is a collaborative spreadsheet experience: a team and Claude can organize data, create and edit formulas, and work across multiple tabs. Whiteboards is a digital space for teams to lay out and organize ideas together in a meeting, then ask Claude to summarize what they found. Claude Data connects to tools such as Snowflake and Salesforce. Anthropic says it can use definitions certified by a data team, a capability marked beta, to create dashboards, visual data stories or narrated short videos. The company also says users can ask Claude to make custom artifacts such as an account tracker, daily briefing, project status board or contract review table.

Anthropic says Claude can carry the same context through successive artifacts, so an idea can move from a whiteboard to a spreadsheet and then to a dashboard without users restating the details. That is the product proposition: not just a collection of generated files, but a continuing workflow in which teams can work with information in different formats. The announcement describes collaborative use, but does not define how simultaneous editing, version history or artifact sharing works.

A separate change upgrades interactive connectors. Starting today, partners can embed their apps directly in Claude, letting users work in services such as Adobe and Atlassian without switching tabs. Anthropic says plugins from Salesforce (beta), NetSuite and Workday (beta) include built-in skills for tasks such as sales-call preparation, financial-data analysis, and handling time off and expenses. Claude Meetings, which would join calls to take notes and update documents, is described as coming soon, not as available now.

The announcement also describes controls for enterprise use. Enterprise administrators can decide who may use products and connectors and set organization-wide spending limits. Anthropic says Claude works within existing tool permissions, and administrators can limit connector actions—for example, allowing it to read Slack but not send messages. Its auto-connect feature is in beta on eligible Team and Enterprise plans. Anthropic says Enterprise data is encrypted in transit and at rest, and describes audit logs, a Compliance API, and isolated virtual machines for each cloud session in the new Enterprise experience.

What the archive adds

New Runtime’s earlier coverage on Claude Dashboards and Claude Motion (2026-10-09) described data dashboards and code-authored animation as extensions to Claude’s artifact suite. The present announcement renames Dashboards as Claude Data and adds Sheets, Whiteboards and embedded partner apps: this is a new event that also develops a known product direction.

Trend signal

This supports the assumption that major assistant products are turning generated outputs into task interfaces, rather than stopping at conversational answers. Claude’s spreadsheets, whiteboards and dashboards are bounded formats for collaborative work. See Model answers become task interfaces. The announcement establishes product direction, but does not independently demonstrate usage or outcomes at scale.

Why now

Anthropic frames the release as an effort to bring to other teams the context-rich workflow it associates with Claude Code: engineers work from a codebase, while other teams’ context is spread across email, apps and drives. Its connector and artifact additions address that stated gap by combining connected context with outputs teams can edit together.

Connections to other events

Anthropic says Claude’s connectors are built on the Model Context Protocol, the open standard it introduced for connecting AI to tools. The announcement also says Claude Marketplace lists more than 9,000 connectors and plugins, including community-built ones. This positions the new embedded apps as a more interactive layer on top of an existing integration ecosystem, rather than a replacement for connectors.

Why it matters

For teams building with AI, the notable shift is from asking an assistant for a one-off answer to asking it to help maintain a work product that several people can inspect and revise. A spreadsheet, project board or dashboard can make an AI contribution easier to put into an existing business process than an isolated chat response. Carrying context between formats could also reduce repeated prompting when work moves from brainstorming to analysis.

That promise depends on whether teams can trust the data and govern what Claude does with it. Anthropic’s examples of certified data definitions and administrator-controlled connector actions point to two practical requirements: outputs need shared business meaning, and permissions need to match the task. Teams should test whether generated artifacts preserve those definitions, expose enough provenance for review, and behave correctly under their connector permissions before treating them as operational records. The release describes capabilities, not independently measured productivity gains.

Limits and uncertainty

Anthropic does not provide a complete feature-by-feature access matrix, prices, usage limits or rollout schedule in the announcement. Some capabilities are explicitly beta, including certified data definitions, Salesforce and Workday plugins, and auto-connect on eligible plans; the company does not quantify their reliability or availability. The cited customer examples are company-selected testimonials, not independently evaluated studies. The announcement does not report error rates, data freshness guarantees, controls for reviewing changes, or comparative results against existing tools. Claude Meetings is future-facing, with no release date stated.

Skill to build now

Pick a low-risk recurring workflow that already moves through more than one format—for example, meeting notes to a project tracker to a status dashboard. Write down the source of truth, the fields that must remain consistent, and the actions Claude may take versus those requiring human approval. That gives your team a concrete test plan when these artifact and connector capabilities are available in its account.

Reader takeaway

Claude’s new artifacts and interactive connectors aim to keep collaborative work inside the assistant, moving context from discussion into editable spreadsheets, whiteboards and dashboards. The useful test for builders is not whether Claude can generate each format, but whether teams can verify the result and safely connect it to the systems where their work already lives.

Evidence / sources

  1. 1claude.com/de/resources/articles/more-ways-to-work-with-claude-sheets-whiteboards-and-interactive-connectors
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicClaudeExplore the claude topic hub.
  2. 02topicAnthropicExplore the anthropic topic hub.
  3. 03archiveField NotesOpen the latest editorial analysis.
  4. 04sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract