Answer: For local computer access, your local executor can still export supported execution events, but cloud orchestration events do not reach your existing OpenTelemetry collector. Supported cloud records are available through the Compliance API, and for dots you use the Analytics API for usage and the Compliance API for supported audit records. Status: Confirmed Entry: tool/chatgpt/admin-and-enterprise/local-access-audit-coverage Revision: 2 Digest: sha256:663d81c244fa9479 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:49:35Z Last changed: 2026-11-17T14:01:27Z (Dots audit API: — → Compliance API) Last verified: 2026-11-20T13:37:33Z Next check: 2026-11-21T13:37:33Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Local OTel coverage | Your local executor can still export supported execution events | [1] | 2026-11-20 Cloud orchestration events | Cloud orchestration events do not reach your existing OpenTelemetry collector | [1] | 2026-11-20 Cloud records source | Compliance API | [1] | 2026-11-20 Collector endpoint change | Changing the collector endpoint does not restore cloud orchestration events | [1] | 2026-11-20 Compliance API vs OTel | Compliance API records do not replace every event in the earlier OpenTelemetry stream | [1] | 2026-11-20 Dots usage API | Analytics API | [1] | 2026-11-20 Dots audit API | Compliance API | [1] | 2026-11-20 MCP hooks | MCP hooks are not a substitute for audit coverage | [1] | 2026-11-20 Sources: [1] OpenAI. "Local computer access for Work Cloud and dots". https://learn.chatgpt.com/docs/enterprise/cloud-local-access.md Role: primary. Accessed: 2026-11-20T13:37:33Z Quote: "Your local executor can still export supported execution events." (Supports: Local OTel coverage) Quote: "Cloud orchestration events do not reach your existing OpenTelemetry collector." (Supports: Cloud orchestration events) Quote: "Use the [Compliance API](https://learn.chatgpt.com/docs/enterprise/compliance-api#audit-records-for-local-computer-access-with-work-cloud) for supported cloud records." (Supports: Cloud records source) Quote: "Changing the collector endpoint does not restore cloud orchestration events." (Supports: Collector endpoint change) Quote: "Compliance API records do not replace every event in the earlier OpenTelemetry stream." (Supports: Compliance API vs OTel) Quote: "For dots, use the [Analytics API](https://learn.chatgpt.com/docs/enterprise/analytics-api) for usage" (Supports: Dots usage API) Quote: "the [Compliance API](https://learn.chatgpt.com/docs/enterprise/compliance-api) for supported audit records" (Supports: Dots audit API) Quote: "MCP hooks are not a substitute for audit coverage." (Supports: MCP hooks) Snapshot SHA-256: 79be3c58a66ad22607caa6c45890cda91375f220cba85556e6b1ae14b932bad6 (captured 2026-11-17T14:01:25Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-17T14:01:27Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:37:33Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:37:33Z Last attempt: 2026-11-20T13:37:33Z Notes and limitations: Extracted automatically from a single official source (section "Review OpenTelemetry and audit coverage"). Related: https://latestn.com/tool/chatgpt/admin-and-enterprise/local-access-compatibility-requirements What compatibility and data requirements must be met before enabling local computer access for Work and dots? https://latestn.com/tool/chatgpt/admin-and-enterprise/manage-org-access How can organization admins manage or disable Sign in with ChatGPT access for members? https://latestn.com/tool/chatgpt/admin-and-enterprise/manage-pending-invitations How do I manage pending invitations in my ChatGPT API organization? https://latestn.com/tool/chatgpt/admin-and-enterprise/kodex-quick-question How do I submit a general compliance question to OpenAI through Kodex? https://latestn.com/tool/chatgpt/admin-and-enterprise/label-exclusion-availability Who can manage Outlook sensitivity-label exclusions in ChatGPT and in which workspaces are they available? https://latestn.com/tool/chatgpt/admin-and-enterprise/limit-gitlab-plugin-actions How can admins limit what the ChatGPT GitLab plugin can do? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T14:01:27Z | changed | Dots audit API: — → Compliance API | [1] 2026-11-17T14:01:27Z | changed | Compliance API vs OTel: — → Compliance API records do not replace every event in the earlier OpenTelemetry stream | [1] 2026-11-17T14:01:27Z | changed | Collector endpoint change: — → Changing the collector endpoint does not restore cloud orchestration events | [1] 2026-11-17T14:01:27Z | changed | Local OTel coverage: — → Your local executor can still export supported execution events | [1] 2026-11-17T14:01:27Z | changed | MCP hooks: MCP hooks are not a substitute for audit coverage. → MCP hooks are not a substitute for audit coverage | [1] 2026-11-17T14:01:27Z | changed | Dots audit records API: Compliance API → — | [1] 2026-11-17T14:01:27Z | changed | Compliance API coverage: Compliance API records do not replace every event in the earlier OpenTelemetry stream. → — | [1] 2026-11-17T14:01:27Z | changed | Cloud orchestration events: Cloud orchestration events do not reach your existing OpenTelemetry collector. → Cloud orchestration events do not reach your existing OpenTelemetry collector | [1] 2026-11-17T14:01:27Z | changed | Local executor telemetry: Your local executor can still export supported execution events. → — | [1] 2026-11-13T03:49:35Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/chatgpt/admin-and-enterprise/local-access-audit-coverage/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/chatgpt/admin-and-enterprise/local-access-audit-coverage POST: https://latestn.com/dispute/tool/chatgpt/admin-and-enterprise/local-access-audit-coverage with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/chatgpt/admin-and-enterprise/local-access-audit-coverage?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What OpenTelemetry and audit coverage is available for local computer access in ChatGPT? Revision 2, last verified 2026-11-20T13:37:33Z. https://latestn.com/tool/chatgpt/admin-and-enterprise/local-access-audit-coverage (accessed 2026-11-21T10:03:57Z). @misc{LatestN_tool_chatgpt_admin_and_enterprise_local_access_audit_coverage_r2, title = {What OpenTelemetry and audit coverage is available for local computer access in ChatGPT?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/chatgpt/admin-and-enterprise/local-access-audit-coverage}}, note = {Revision 2; digest sha256:663d81c244fa9479; last verified 2026-11-20T13:37:33Z; accessed 2026-11-21T10:03:57Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/chatgpt/admin-and-enterprise/local-access-audit-coverage