Quick answer
ChatGPT Work is OpenAI’s agent surface for longer, multi-step research, analysis, and finished deliverables. It can use the current chat, uploaded files, workspace resources, and authorized connected systems, then create review-ready documents, presentations, analyses, spreadsheets, or Sites.
Access is not one switch. Verify account plan, workspace role, Work entitlement, surface, region, credits, plugin policy, source permissions, action permissions, data controls, and output-sharing state separately.
Choose the right source
| Source | What it can add | Control that still applies |
|---|---|---|
| Current chat | Goal, constraints, examples, decisions | User-supplied scope and chat retention |
| Uploaded files | Briefs, datasets, drafts, references | File authorization, classification, retention, minimization |
| Workspace resources | Approved organizational context | Workspace administration, role, availability |
| Connected systems | Documents, repositories, tickets, channels, email, calendars, records | Native authentication, permissions, plugin policy, action controls |
| Local apps or files | Context available through supported desktop capabilities | Local permission profile, approvals, operating-system boundary |
OpenAI states that ChatGPT Work does not bypass connected-system access controls or grant new native permissions. A connector can still expand the amount of authorized information brought into one task, so use least privilege and inspect the requested scope.
Match the deliverable to the task
Start with a decision and an acceptance test. Ask for a source-backed memo when the job is synthesis, a spreadsheet when the value is a reviewable calculation, a presentation when the audience needs a narrative, or a Site when people need an interactive internal workflow.
For Sites, keep the first version private. OpenAI documents separate access, rollout, region, storage, data, publishing, and workspace-admin conditions. A generated preview is not approval to deploy or share it.
Access and spend checklist
OpenAI says ChatGPT Work and Codex share pricing, credits, and usage limits, while standard Chat usage is separate. Consumption varies with model, capability, context, duration, tools, connectors, retries, and output size.
Before rollout, verify:
- Current plan, member seat, Work access, surface, region, and workspace policy.
- Source accounts, shared connections, roles, plugin allowlist, and action settings.
- Monthly limits, group defaults, individual overrides, alerts, and stop conditions.
- Retention, residency, logging, compliance coverage, deletion, and connected-service policy.
- Human review before external writes, sharing, publishing, sending, deletion, or consequential execution.
The scheduled-tasks guide covers recurring work. The Chat vs Work vs Codex guide helps choose the surface.
Frequently asked questions
What is ChatGPT Work?
OpenAI describes ChatGPT Work as the agent in ChatGPT for longer, multi-step research, analysis, and finished work. It can use authorized chat, file, workspace, and connected-system context, then return documents, presentations, analyses, Sites, or other outputs for review.
Can ChatGPT Work access all company files?
No. OpenAI says connected source systems continue to enforce their own authentication and permissions. Access also depends on the user’s workspace role, enabled plugins, approved shared connections, surface, plan, region, and administrator settings.
Does ChatGPT Work include Sites?
ChatGPT Work can create Sites, but Sites has its own eligibility, workspace, region, storage, data, and sharing boundaries. OpenAI described Sites as a public beta for eligible paid plans and documented launch-region exclusions, so verify current access before planning a deployment.
Bottom line
Use ChatGPT Work when the outcome is multi-step, source-backed, and reviewable. Treat each source, tool, action, deliverable, schedule, and sharing destination as a separate permission and validation boundary.
Official sources
Source check: August 2, 2026. Verify current plan, region, rollout, credits, permissions, data controls, and product availability.