What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Claude Motion and Claude Dashboards do not receive universal access to your company systems just because you turn them on. Dashboards query a warehouse or connected app through the identity and permissions you configure. Motion works from the text, charts, shapes, images, and other context you supply, then produces editable animation code. Account roles, project settings, connector permissions, and artifact-sharing choices determine who can enable a feature, see its output, or export it.

The important distinction is that an artifact’s sharing setting does not replace access control on the underlying data. A dashboard can expose sensitive SQL and values, and a downloaded Motion MP4 can contain confidential information even after it leaves Claude. Treat source permissions and artifact audience as two separate reviews.

What Claude Dashboards and Motion actually do

Dashboards turn questions into SQL-backed views

Claude Dashboards accepts a plain-language question, writes and runs SQL against a connected data source, and presents the result as charts. Every chart exposes the SQL query it used and a label showing when the data was last refreshed. That makes a dashboard useful for quick exploratory questions, while giving you a way to inspect what was counted and how current the result is.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Anthropic’s help guide describes a dashboard as “an artifact made from the Dashboards template.” Its examples include “Build a dashboard of this quarter’s revenue by region.” and “Make a dashboard of my open Salesforce opportunities by stage and owner.” Those examples illustrate the interaction style; they do not mean every account has every connector or that Claude can read every table in a connected system.

Possible sources named in the documentation include Amazon Redshift, BigQuery, ClickHouse, Databricks, Snowflake, and connected applications such as Salesforce. Availability depends on the connector enabled for your account, its authentication method, and the privileges granted to the source identity.

Motion animates material you provide

Claude Motion creates an animated explainer from a prompt or supplied material. Anthropic says, “Claude writes code that animates your text, charts, shapes, and images, so you can edit every detail, word, and number.” You can edit the generated result and download an MP4. Motion’s reviewed documentation does not describe a separate, Motion-specific database-access role. Its practical access boundary is therefore the material and connected context you provide, together with your account, project, and artifact controls.

Motion and Dashboards are beta features. Anthropic reported more than 45 million Docs, decks, and designs created since those artifact types were introduced in an October 8, 2026 announcement, but that company-reported figure does not measure Motion or Dashboards usage.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Plans and feature availability

The current documentation describes these availability rules:

Feature Plans named as eligible Organization controls Status
Claude Dashboards Paid Pro, Max, Team, and Enterprise On Enterprise, an Owner must enable the feature. Owners can restrict it to selected groups with custom roles. Beta
Claude Motion Team and Enterprise The reviewed Motion documentation does not specify an independent Motion permission system; account, project, connector, and artifact controls still apply. Beta

Feature availability and labels can change as Anthropic updates plans, artifact sharing, and organization controls. On an Enterprise account, a missing feature may simply be disabled by an Owner rather than unavailable to the plan.

What Claude can access—and what it cannot infer automatically

Connected sources follow the identity you authorize

A dashboard does not bypass the warehouse or application’s security model. The connector authenticates with a particular user, service account, OAuth grant, or other configured identity. Claude can query only the datasets, schemas, records, and actions that identity is allowed to use. If a source account cannot read a table, the dashboard should not be treated as a way around that restriction.

Source-side permissions remain your responsibility. Before connecting, identify the exact warehouse or app, the account used for authentication, its role, and any row-, column-, or object-level scopes. A broad service account can expose more information than a narrowly scoped analyst account, regardless of who created the dashboard.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Remote web connectors and local desktop extensions are different

Anthropic distinguishes remote web connectors from desktop extensions. A remote connector authenticates to a cloud service and may be available across Claude surfaces. A desktop extension runs locally in Claude Desktop and can access local files, applications, or system resources within the permissions it receives.

Review the OAuth consent screen and extension permissions, install extensions only from trusted sources, monitor tool use, and periodically audit connected services. “Connected” is not a universal permission: the effective boundary is the specific source account and scopes granted to that integration. Anthropic explains the distinction in its desktop and web connectors guide and tool-connection tutorial.

Motion does not automatically discover company systems

Supplying an image, chart, document, or prompt to Motion gives it that material as context; it does not, by itself, grant access to an entire drive, warehouse, or internal application. If the material came from a connected source, the source identity and connector scope still determine what could be retrieved. The resulting animation may nevertheless reproduce every sensitive value you supplied, so the output needs its own audience review.

Roles that control features, data, and exports

Team and Enterprise roles determine who can administer Claude for Work:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Admins can invite and remove members.
  • Owners and Primary Owners can change roles and manage native or custom integrations and capabilities.
  • Primary Owners are the only role that can request data exports on Team and Enterprise.
  • Enterprise Owners and Primary Owners can manage SSO and authentication, request audit logs, set data-retention controls, and manage feedback settings.
  • Enterprise usage analytics are visible to Admins, Owners, and Primary Owners.
  • Custom roles are an Enterprise feature; their effective permissions depend on the groups to which they are assigned.

The complete role matrix is in Claude’s Roles and permissions guide. A user’s ability to create a dashboard or Motion artifact is therefore separate from the organization’s ability to enable the feature, export account data, or inspect usage.

Anthropic states that “Your organization’s designated Primary Owner manages your Work account and all associated data.” A Primary Owner can request exports that may contain conversations, uploaded files, and usage patterns, and can remove a user’s account access. The organization decides which Claude services and features employees may use. Work-account questions should be answered against your employer’s policy and agreement, not consumer-account assumptions; see Who owns and manages the data of my team?.

Dashboard, artifact, project, and chat visibility

Artifacts begin private

Anthropic’s Artifacts documentation says artifacts are private until you share them. A newly created dashboard or Motion result is therefore not automatically visible to everyone in your organization. Sharing is an explicit action, but the available audience depends on the account type and organization settings.

On Team and Enterprise, an Owner or Primary Owner must enable external artifact sharing in Organization settings > Artifacts. Once enabled, check the specific audience before sending a link: it may be one invited person, your organization, or anyone who obtains the link. Consumer-plan artifact links can be shared with anyone who has the link. A copied URL or downloaded MP4 can also travel outside the controls of the original workspace.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Projects have separate visibility rules

Project visibility is not the same as artifact sharing. On Team and Enterprise, a project can be private to invited people or public to the organization, subject to organization settings. In a public project, the project’s knowledge and instructions may be available to the organization, but chats remain private unless someone manually shares them.

A private project shares its knowledge and instructions with invited collaborators according to their view or edit role. That permission does not automatically disclose every chat. Keep three decisions separate: who can enter the project, who can read a particular chat, and who can open a dashboard or Motion artifact.

The sharing behavior is detailed in Manage project visibility and sharing.

SQL visibility helps review but is not a security boundary

For each dashboard chart, inspect the displayed SQL and refresh timestamp. The query reveals which tables, filters, joins, and aggregations Claude used; the timestamp tells you how stale the result may be. This is a review aid, not a replacement for source-side authorization, data-quality checks, or a decision about who should see the chart.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Work-account privacy versus consumer-account privacy

Question Claude for Work (Team or Enterprise) Consumer Free, Pro, or Max
Who governs the account data? The customer organization is the data controller; Anthropic acts as processor under the commercial agreement. The individual account holder controls the account and its privacy settings.
Who may export or remove access? The Primary Owner can request exports and remove a user’s account access; organizational policies also apply. Controls are managed through the individual account.
Model improvement Anthropic says commercial product data is not used to train models unless the customer opts into the Development Partner Program. Users can adjust model-improvement settings. If they permit improvement use, Anthropic says data is delinked from user IDs before review and access is limited to a small group involved in training.
Special handling Retention, audit, feedback, and internal-use rules depend on the organization’s agreement and settings. Incognito chats are not used for improvement, but conversations flagged by safety classifiers may still be used for trust-and-safety purposes.

Anthropic’s consumer guidance specifically advises care with financial details, health records, credentials, and confidential documents. Read Who can view my conversations? for the current consumer settings. Do not assume a consumer privacy choice changes the governance of a work account, or vice versa.

For commercial accounts, review your organization’s agreement and admin policy alongside Anthropic’s processor-or-controller explanation. That is where retention, access, and contractual exceptions are defined for your deployment.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

A safe setup and review procedure

  1. Confirm eligibility and enablement. Record whether the account is Pro, Max, Team, or Enterprise for Dashboards, and Team or Enterprise for Motion. On Enterprise, ask an Owner whether the feature is enabled and whether a custom role limits it to particular groups.
  2. Inventory the exact source. Write down the warehouse or application, connector type, authentication identity, and scopes. Verify source-side roles, row or column restrictions, and whether the identity can read more than the dashboard requires.
  3. Test with non-sensitive data. Start with a small, representative dataset. Check that a user who should not see a table cannot retrieve it through a dashboard query or connected tool.
  4. Review every dashboard chart. Open the SQL shown for each chart, verify filters and joins, and record the last-refresh time. Investigate unexpected tables, broad filters, or stale data before using the result operationally.
  5. Inspect Motion inputs and output. Remove secrets and unnecessary personal data from prompts, images, charts, and documents. Review the animation frame by frame for values, labels, filenames, or metadata that should not leave the intended audience.
  6. Set the audience deliberately. Check whether the artifact is private, shared with named people, available to the organization, or accessible to anyone with a link. Confirm the Enterprise external-sharing setting before distributing a URL or MP4.
  7. Check project and chat settings independently. Confirm the project’s private or organization-visible status, each collaborator’s view or edit role, and whether the relevant chat was separately shared.
  8. Ask the Primary Owner about governance. Confirm retention periods, export procedures, audit-log availability, feedback settings, and the organization’s rules for employee-submitted files and conversations.
  9. Re-audit connectors. Review OAuth grants and desktop extensions after staff changes, connector updates, or role changes. Revoke unused integrations and narrow scopes where possible.

Common misunderstandings and how to correct them

“Enabling Dashboards lets Claude read everything.”

It does not. Access is constrained by the configured connector identity and source permissions. Correct the assumption by documenting the identity, testing denied objects, and reviewing each chart’s SQL.

“A private project makes every artifact private.”

Project visibility, chat sharing, and artifact sharing are separate controls. Correct the assumption by checking the artifact’s own share setting and the organization’s external-sharing policy.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

“A chart is current because it was generated today.”

The chart may use an older refresh. Read its last-refresh label and validate the source pipeline’s update schedule before relying on time-sensitive figures.

“Downloading an MP4 preserves Claude’s workspace protections.”

An exported file can be copied, emailed, or uploaded elsewhere. Apply your normal document-classification and distribution rules to the MP4 itself.

“Consumer incognito rules apply to a company account.”

Work accounts are governed by the customer organization’s commercial arrangement and admin settings. Ask the Primary Owner which policy applies instead of inferring it from consumer controls.

Decision checklist for administrators and data owners

  • Do we know the plan, beta status, and Owner who enabled the feature?
  • Which exact source, identity, OAuth grant, or local extension supplies the data?
  • Are source-side roles narrower than the maximum data the connector could expose?
  • Has someone reviewed every dashboard query, filter, and refresh timestamp?
  • Does the Motion output contain confidential values, personal data, credentials, or hidden metadata?
  • Is the artifact private, organization-visible, named-recipient, or link-accessible?
  • Are project membership, chat sharing, and artifact sharing documented separately?
  • What can the Primary Owner export, retain, audit, or remove under the organization’s policy?
  • Have consumer model-improvement settings been distinguished from commercial-account terms?
  • Are unused connectors and desktop extensions revoked and their permissions periodically rechecked?

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.