Anthropic's November 10 update adds shared spreadsheets and whiteboards to Claude, makes its Dashboards feature generally available under the name Claude Data, and expands interactive connectors. The pieces target different parts of team work: sketching a problem, organizing structured information, analyzing connected business data, and using an existing app without leaving a Claude conversation. They form a wider workspace, but they are not one product with the same data access or maturity.
Use a Whiteboard before the team knows the answer
Claude Whiteboards is a shared board for arranging ideas, diagrams, flows and groups with Claude and teammates. A team can describe a launch plan or decision, move the pieces around together, then ask Claude to turn the settled board into a document or slide deck. Anthropic says Whiteboards is in beta on paid Pro, Max, Ultra, Team and Enterprise plans. Team plans have it on by default; an Enterprise owner must enable it in organization settings. A key boundary: a Whiteboard works from what is on the board and does not draw context from connected apps. It is a place to shape a discussion, not a live view of a team's project system.
Use Sheets for shared working numbers, not as a full Excel replacement
Claude Sheets lets a team and Claude edit the same spreadsheet cells, use formulas across tabs, format data, and import or export CSV and Excel files. It is also in beta on paid plans, with the same Team-on and Enterprise-off-by-default pattern as Whiteboards. The Help Center describes it as a light spreadsheet: it does not support features such as pivot tables, VBA, Power Query or live data pulled from connected apps, and mobile access is read-only. That makes it useful for building a tracker or first-pass budget with a team, while an existing financial model or live operational workbook may still belong in a full spreadsheet application.
Claude Data is for connected business information
Claude Data is the new name for Claude Dashboards, which Anthropic says is generally available. It connects to sources such as data warehouses and CRMs to build dashboards, data stories and narrated videos. Each chart shows the query behind it and when it was last refreshed. The organization can define certified queries so teams reuse approved metric definitions. Claude Data itself is available on paid plans; certified queries and live sharing remain beta. Team defaults enable these templates, while the current admin guide says Enterprise Data will turn on by default on November 19, 2026, unless an owner has already saved a different setting. Enterprise owners can enable it sooner.
Live sharing is a deliberate exception to the usual connector model: a colleague may see results from the dashboard owner's connected data source without connecting that source themselves. They see the dashboard results and can run only approved queries, not browse the underlying warehouse or CRM through the owner's login. Teams should decide whether this is appropriate for each dashboard and keep metric definitions and refresh timing visible when results inform a decision.
Interactive connectors bring app interfaces into the conversation
Interactive connectors are different from artifacts. They display a connected app's interface as an inline card, side panel or full-page view in Claude. A team might inspect an analytics dashboard or update a task board while continuing the conversation. Which actions are possible depends on the connector developer, and the connector uses the permissions already granted to the user's account. Team and Enterprise owners can disable interactive tool calls separately while leaving ordinary text-based connector access enabled. The current Help Center says the new side-panel and full-page experience is still rolling out on web and desktop, and those views are not yet available on Claude Mobile.
A practical way to evaluate the launch is to map each step of a team's workflow to the tool that owns its source of truth: Whiteboards for early thinking, Sheets for a collaborative working model, Claude Data for governed metrics, and interactive connectors when someone needs to work directly in an existing service. That flow may reduce context switching, but it does not remove review, permissions or data-governance work. Check the exact connector's read/write actions, confirm who can enable beta templates, and keep consequential numbers or changes reviewable in their system of record.