[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-changelog\u002Fpartner-connect":3,"docs-tabs-changelog\u002Fpartner-connect":6},{"content":4,"lastmod":5},"# Change history: Partner Connect\n\n[← Changelog](\u002Fdocs\u002Fchangelog). Entries: 34.\n\n- 2026-11-14 [BC-1114-1: Partner Connect application keys grant access to AI models only](\u002Fdocs\u002Fchangelog\u002F2026-11-14#bc-1114-1-partner-connect-application-keys-grant-access-to-ai-models-only)\n- 2026-11-04 [FIX-1104-1: requesting vibe:storage when connecting in COMPANY mode](\u002Fdocs\u002Fchangelog\u002F2026-11-04#fix-1104-1-requesting-vibe-storage-when-connecting-in-company-mode)\n- 2026-11-03 [NEW-1103-13: account hint in the Connect authorization link](\u002Fdocs\u002Fchangelog\u002F2026-11-03#new-1103-13-account-hint-in-the-connect-authorization-link)\n- 2026-10-30 [FIX-1030-10: previous webhook cleanup no longer closes Bitrix24 for a Company connection](\u002Fdocs\u002Fchangelog\u002F2026-10-30#fix-1030-10-previous-webhook-cleanup-no-longer-closes-bitrix24-for-a-company-connection)\n- 2026-10-22 [NEW-1022-5: Who is connected to a company key](\u002Fdocs\u002Fchangelog\u002F2026-10-22#new-1022-5-who-is-connected-to-a-company-key)\n- 2026-10-20 [NEW-1020-7: Company connections: readiness checks at every phase](\u002Fdocs\u002Fchangelog\u002F2026-10-20#new-1020-7-company-connections-readiness-checks-at-every-phase)\n- 2026-10-20 [NEW-1020-8: AI for company connections with separate administrator consent](\u002Fdocs\u002Fchangelog\u002F2026-10-20#new-1020-8-ai-for-company-connections-with-separate-administrator-consent)\n- 2026-10-19 [FIX-1019-2: Connect revokes the presented Cowork device key](\u002Fdocs\u002Fchangelog\u002F2026-10-19#fix-1019-2-connect-revokes-the-presented-cowork-device-key)\n- 2026-10-17 [NEW-1017-6: sign-in source label for device flow](\u002Fdocs\u002Fchangelog\u002F2026-10-17#new-1017-6-sign-in-source-label-for-device-flow)\n- 2026-10-14 [FIX-1014-6: Connect sign-in accepts a localhost redirect address for both client types](\u002Fdocs\u002Fchangelog\u002F2026-10-14#fix-1014-6-connect-sign-in-accepts-a-localhost-redirect-address-for-both-client-types)\n- 2026-10-14 [BC-1014-14: PKCE is also enforced for confidential clients](\u002Fdocs\u002Fchangelog\u002F2026-10-14#bc-1014-14-pkce-is-also-enforced-for-confidential-clients)\n- 2026-10-13 [BC-1013-1: App address outside the platform: https only, not with an app or server key](\u002Fdocs\u002Fchangelog\u002F2026-10-13#bc-1013-1-app-address-outside-the-platform-https-only-not-with-an-app-or-server-key)\n- 2026-10-12 [BC-1012-4: The vibe:storage scope is not granted to Partner Connect applications](\u002Fdocs\u002Fchangelog\u002F2026-10-12#bc-1012-4-the-vibe-storage-scope-is-not-granted-to-partner-connect-applications)\n- 2026-10-12 [FIX-1012-5: A vibe:storage scope refusal on a Partner Connect key no longer suggests an administrator grant](\u002Fdocs\u002Fchangelog\u002F2026-10-12#fix-1012-5-a-vibe-storage-scope-refusal-on-a-partner-connect-key-no-longer-suggests-an-administrator-grant)\n- 2026-10-12 [NEW-1012-6: refusal outcomes for COMPANY clients](\u002Fdocs\u002Fchangelog\u002F2026-10-12#new-1012-6-refusal-outcomes-for-company-clients)\n- 2026-10-12 [NEW-1012-7: Refusal codes for company connections](\u002Fdocs\u002Fchangelog\u002F2026-10-12#new-1012-7-refusal-codes-for-company-connections)\n- 2026-10-12 [FIX-1012-8: Consistent refusal for closed company connection issuance](\u002Fdocs\u002Fchangelog\u002F2026-10-12#fix-1012-8-consistent-refusal-for-closed-company-connection-issuance)\n- 2026-10-12 [NEW-1012-10: Company connection status polling](\u002Fdocs\u002Fchangelog\u002F2026-10-12#new-1012-10-company-connection-status-polling)\n- 2026-10-09 [BC-1009-19: Bitrix24 account approval for AI access in Connect applications](\u002Fdocs\u002Fchangelog\u002F2026-10-09#bc-1009-19-bitrix24-account-approval-for-ai-access-in-connect-applications)\n- 2026-10-08 [NEW-1008-8: Partner Connect: a \"Connect AI\" button example for an application inside Bitrix24](\u002Fdocs\u002Fchangelog\u002F2026-10-08#new-1008-8-partner-connect-a-connect-ai-button-example-for-an-application-inside-bitrix24)\n- 2026-09-30 [BC-0930-31: Key revocation with a server outside its owner and Bitrix24 account scope](\u002Fdocs\u002Fchangelog\u002F2026-09-30#bc-0930-31-key-revocation-with-a-server-outside-its-owner-and-bitrix24-account-scope)\n- 2026-09-28 [FIX-0928-15: empty POST requests receive the intended validation response](\u002Fdocs\u002Fchangelog\u002F2026-09-28#fix-0928-15-empty-post-requests-receive-the-intended-validation-response)\n- 2026-09-14 [FIX-0914-17: Connect app authorization on self-hosted portals](\u002Fdocs\u002Fchangelog\u002F2026-09-14#fix-0914-17-connect-app-authorization-on-self-hosted-portals)\n- 2026-09-14 [FIX-0914-23: rate limit descriptions state the platform-wide cap and point at the header with the effective value](\u002Fdocs\u002Fchangelog\u002F2026-09-14#fix-0914-23-rate-limit-descriptions-state-the-platform-wide-cap-and-point-at-the-header-with-the-effective-value)\n- 2026-09-13 [NEW-0913-2: a Partner Connect application requests the vibe:ai scope itself](\u002Fdocs\u002Fchangelog\u002F2026-09-13#new-0913-2-a-partner-connect-application-requests-the-vibe-ai-scope-itself)\n- 2026-09-12 [NEW-0912-2: device_id parameter in the device-flow confirmation link](\u002Fdocs\u002Fchangelog\u002F2026-09-12#new-0912-2-device_id-parameter-in-the-device-flow-confirmation-link)\n- 2026-09-11 [NEW-0911-7: The flow_ref field in the device-code response](\u002Fdocs\u002Fchangelog\u002F2026-09-11#new-0911-7-the-flow_ref-field-in-the-device-code-response)\n- 2026-09-09 [FIX-0909-8: the spec declares the 429 refusal of endpoints that carry their own rate limit](\u002Fdocs\u002Fchangelog\u002F2026-09-09#fix-0909-8-the-spec-declares-the-429-refusal-of-endpoints-that-carry-their-own-rate-limit)\n- 2026-09-09 [FIX-0909-10: the token endpoint's rate-limit refusal is now machine-readable](\u002Fdocs\u002Fchangelog\u002F2026-09-09#fix-0909-10-the-token-endpoint-s-rate-limit-refusal-is-now-machine-readable)\n- 2026-09-08 [NEW-0908-12: key issuance now says whether the key got access to Bitrix24 data](\u002Fdocs\u002Fchangelog\u002F2026-09-08#new-0908-12-key-issuance-now-says-whether-the-key-got-access-to-bitrix24-data)\n- 2026-09-07 [NEW-0907-13: `\u002Fv1\u002Fcowork\u002Fme` and `\u002Fv1\u002Fcowork\u002Fstate` now name the Bitrix24 account the key is bound to](\u002Fdocs\u002Fchangelog\u002F2026-09-07#new-0907-13-v1-cowork-me-and-v1-cowork-state-now-name-the-bitrix24-account-the-key-is-bound-to)\n- 2026-09-04 [NEW-0904-9: a partner application can revoke its own key](\u002Fdocs\u002Fchangelog\u002F2026-09-04#new-0904-9-a-partner-application-can-revoke-its-own-key)\n- 2026-09-02 [NEW-0902-6: device-flow accepts a device identifier](\u002Fdocs\u002Fchangelog\u002F2026-09-02#new-0902-6-device-flow-accepts-a-device-identifier)\n- 2026-08-11 [NEW-0811-10: granted_scopes — the issued key's actual scopes in the exchange response](\u002Fdocs\u002Fchangelog\u002F2026-08-11#new-0811-10-granted_scopes-the-issued-key-s-actual-scopes-in-the-exchange-response)\n",null,{},1794739521541]