OpenAI tightened ChatGPT Enterprise workspace export controls so owners can block bulk conversation exports and require dual approval on large archive jobs.
OpenAI’s Enterprise note today is aimed at the quiet way data leaves a workspace: the export button, not the dramatic screenshot. Owners can now block bulk conversation exports and demand a second approver when someone queues a large archive job. That will annoy the person who liked downloading everything on a Friday. It will delight the CISO who has watched “I needed a backup” turn into a zip file on a personal drive.
What is in scope
Bulk export and archive flows sit under the new toggles. Ordinary chatting, including the human habit of copying a paragraph into a ticket, is not what OpenAI is pretending to solve here. If your threat model is an employee pasting secrets into a prompt, you still need training, logging, and maybe a network DLP product. If your threat model is a departing admin exporting six months of workspace history, these controls are the missing seatbelt.
Dual approval matters. A single owner key that can both configure and exfiltrate is how “break glass” becomes “break trust.” Require a second human. Write down who those humans are. Rotate them when roles change.
How to roll it out without a mutiny
Announce the change before you flip it. Tell teams where legitimate archives should go—usually a company bucket with retention rules. Give compliance a path to request an export that leaves an audit trail. Then turn off casual bulk download.
OpenAI is admitting that Enterprise customers treat chat history like a records system even when the product marketing still says “assistant.” Records systems get export gates. Tuesday’s update is OpenAI catching up to how companies already behave. Turn the gates on, then go verify your actual sensitive chats are not living in a consumer workspace by mistake.
Audit checklist for owners
This week, list who can approve exports, confirm that consumer ChatGPT accounts are not holding company work, and sample one archive request end-to-end so compliance sees the dual-approval prompt before a real incident. Write the policy in one page and link it from the Enterprise admin notes. Controls that nobody rehearses become theater the first time legal asks for a clean export under a deadline.