ChatGPT Enterprise/EDU retires individual-user app sync on August 10, with full disablement on August 14

What changed and when

LABEL: factual reporting. OpenAI is retiring individual-user sync for connected apps in ChatGPT Enterprise/EDU and replacing it with admin-managed sync plus plugin-based access, a change first recorded in the August 10, 2026 release notes and dated August 10, 2026. The shift means user-authorized sync flows stop being a supported onboarding path and IT administrators become the only parties who can configure knowledge ingestion from external services.

The actor in the Event record is OpenAI acting through the ChatGPT Enterprise/EDU product surface, and the object being retired is individual-user sync for connected apps in favor of admin-managed sync and plugin-based access. This is a governance change rather than a capability addition: existing workflows that depended on end users linking their own personal Google Drive, SharePoint, GitHub, or CRM accounts will need to be re-cut by admins using plugins. Teams that already had administrator-managed sync in place do not need to undo that configuration, but they do need to confirm their connectors map cleanly to the new plugin set.

Treat the August 10, 2026 date as the policy effective date, and the August 14 deadline as the operational cutover.

Confirmed facts admins must act on

LABEL: factual reporting. The release notes specify two calendar anchors that developers and workspace owners should not confuse. Starting August 10, 2026, new individually authorized sync connections are no longer available, so any team that tried to onboard a new integration after that point via the old user-sync flow is already past the entry cutoff.

On August 14, existing individual-user sync connections will be disabled, and deletion of associated synced data will begin, which means any retrieval-augmented features, search indexes, or fine-tuning corpora built from those syncs are at risk of removal on that day. Administrator-managed sync is unaffected by the retirement, which is the migration target for teams that want continuity. Admins are directed to review workspace connector settings by August 14 and take concrete actions: enable the Google Drive plugin and, where synced knowledge is required, configure admin-managed Google Drive sync using domain-wide delegation; enable the SharePoint plugin and configure admin SharePoint sync; and enable the non-synced GitHub plugin, which explicitly does not perform sync.

Pending replacements and partner-dependent connectors

LABEL: factual reporting. Several connectors in the published table do not have replacement plugins ready, and OpenAI states it will communicate availability of replacement plugins for GitLab Issues, Azure Boards (Azure DevOps), and Basecamp. Until those replacements ship, admins running ChatGPT Enterprise/EDU workspaces that relied on those individual-user syncs have no plugin-based equivalent listed in the release notes, which is a real gap to plan around before August 14.

, Zoho CRM, and Pipedrive — is in a different posture: admins are told to identify affected users and workflows and notify them that synced access will end, because OpenAI is actively working with each partner to provide a replacement rather than offering an in-product plugin today. This two-track posture means the August 14 disablement is firm for the user-sync path, but the substitution timeline is uneven: some migrations are a plugin switch, others are a notification plus a waiting period.

Reader impact for developers and admins

LABEL: impact analysis. The operational impact lands on three groups. Workspace administrators become the sole owners of connector configuration, which is a workload shift but not a capability loss for teams that already used admin-managed sync for regulated services.

End users who had personally authorized syncs lose their existing data pipelines on August 14 and need to be told that their linked content will be deleted, which is the kind of change that breaks internal demos, retrieval pipelines, and any saved prompts that referenced synced files. Engineering teams building on top of ChatGPT Enterprise/EDU knowledge should treat this as a breaking change in their dependency graph: any service whose ingestion path ran through a user-authorized sync must be re-pointed at the corresponding admin plugin before August 14, or the synced index will silently disappear.

Teams using GitHub should specifically note that the replacement is a non-synced plugin, which means code search and repository ingestion flows that depended on indexed content will need a different mechanism.

Uncertainty and what to watch

LABEL: uncertainty framing. The release notes leave several open questions that admins should monitor between now and August 14. First, replacement timing for GitLab Issues, Azure Boards (Azure DevOps), and Basecamp is described only as forthcoming, so any workspace that relied on those syncs has no firm migration date and should treat August 14 as a hard deadline to find a temporary workaround.

, Zoho CRM, and Pipedrive — depend on third-party replacement work, which is an external dependency admins cannot accelerate; teams should capture which users and workflows touch each one before disablement so they can prioritize which replacements to chase. Third, the exact deletion behavior of synced data after August 14 is not enumerated: the notes say deletion of associated synced data will begin, but do not specify the retention window or whether admins can export it. Watch for a follow-up note clarifying retention, and confirm with your OpenAI account team before assuming the data is recoverable post-cutover.