Ctrlk
Harmonic SecurityResource LibraryContact
For the complete documentation index, see llms.txt. This page is also available as Markdown.

ChatGPT Work

Security guidance for ChatGPT Work, including managed workspace use, connectors, browser and Computer Use policy, scheduled work, artifacts, sandbox boundaries, and evidence gaps.

In short: ChatGPT Work turns ChatGPT into a general business agent for research, analysis, documents, spreadsheets, presentations, Sites, connected apps, browser tasks, and recurring work. Treat it as a workforce agent surface, not ordinary chat.

What to focus on first

Bring usage under management

Find desktop and web usage, force managed sign-in where available, enforce SSO and MFA, and assign Work by group and use case.

Review connectors and plugins

Separate read access from write, send, delete, publish, and share actions. Source-system permissions still apply, but Work makes them easier to combine.

Do not overclaim sandbox coverage

Desktop Work can use local permission controls, while hosted Work runs under ChatGPT workspace controls. Match the control to the execution path.

Gate browser and Computer Use

Signed-in browser state, screen contents, clipboard data, and desktop apps can become agent-visible. Disable or scope these surfaces for baseline users.

Constrain scheduled work and artifacts

Scheduled tasks, generated files, Sites, and shared artifacts need owners, destinations, expiry or review dates, and DLP coverage.

Build the evidence trail

Compliance logs help, but they do not capture every file, action, approval, or tool call. Join platform records with endpoint and source-system logs.

What is ChatGPT Work?

ChatGPT Work is OpenAI's general-purpose agentic workspace for business tasks. Use it for research, analysis, documents, spreadsheets, presentations, Sites, and workflows that need context from conversations, files, workspace resources, or connected systems.

Work is distinct from ChatGPT Codex, which is the software-development agent for repositories, terminals, code review, cloud tasks, and developer automation. Approve Work and Codex separately, even when both appear in the same ChatGPT desktop app.

Security boundary

Work can run in hosted ChatGPT contexts and, through the desktop app, on a local computer with selected local permissions. Those paths do not share one security boundary.

For every rollout, record:

  • whether the task is web, mobile, desktop, local, remote, or hosted;

  • which connected apps, plugins, files, folders, browser sessions, and artifacts it can reach;

  • which actions require approval before write, send, delete, publish, share, purchase, or external transfer;

  • whether generated files and Sites are covered by DLP, retention, and sharing policy; and

  • which evidence sources can reconstruct prompts, responses, files, tool calls, approvals, and downstream actions.

Security review checklist

  • Work usage is discovered across managed and personal accounts.

  • SSO, MFA, SCIM, workspace membership, and group-based access are enforced.

  • Connectors and plugins have reviewed owners, scopes, actions, and revocation paths.

  • Browser, Chrome, Computer Use, Appshots, Remote Control, and scheduled work are disabled or scoped for the baseline role.

  • Sensitive app categories such as admin, finance, HR, legal, security, customer systems, and production systems require approval or are blocked.

  • Sites, generated files, and artifacts have sharing, retention, and DLP controls.

  • Compliance exports are paired with endpoint, browser, source-system, repository, and SIEM evidence.

  • Prompt injection, exfiltration, destructive action, connector abuse, and public sharing tests are run before broad rollout.

Provider documentation

Applicable Harmonic guidance

Last reviewed: August 18, 2026

Related handbook guidance

PreviousOpenAI
NextChatGPT Codex

Was this helpful?