Claude auto-connect beta changes how staff connect approved apps

What changed

The announcement explains that enterprise-managed authentication previously required a supporting identity provider. Auto-connect removes that requirement by checking that the signed-in Claude member belongs to the organisation. This is the scope described by Anthropic; it does not mean every external app or every personal account becomes connected automatically.

Named integrations include Amplitude, Apollo.io, Atlassian, Datadog, Dropbox, Figma, Granola, HubSpot, Linear, Mixpanel, Notion, PagerDuty, Semrush and Supabase. The company also says developers of their own MCP servers can add support themselves or use a compatible authentication provider.

For marketing operations teams, the change concerns the connection process around tools that may hold analytics, planning or CRM information. It does not establish that Claude receives identical read or write capabilities in every app. Those permissions depend on the integration and the access approved for it.

Before adopting the workflow, confirm plan eligibility, the intended apps and the identity match for staff who will use them. Review the app’s requested permissions and the organisation’s normal onboarding and offboarding process. Removing a repeated sign-in step does not remove the need to understand which records a connected service can access.

The original announcement is an unsigned Claude for Business post. This article covers that enterprise beta separately from Anthropic’s Personal Finance product, which has different users, eligibility and data. No recommendation to purchase Claude or any named integration is implied, and the post does not supply a measured productivity result for an advertising team.