Three September changes with different boundaries
Release notes describe Library file and folder sharing on 9 September, additional connected storage providers on 10 September and multiple accounts for more plugins on 17 September. These are separate capabilities with distinct availability boundaries. The full Library interface is on the web; mobile search and recent-file access are not the same experience. New external sources roll out according to account and plan. Check the storage provider and its connection in the actual business account. General Library availability does not mean every external source is included or that every available document can also be edited through ChatGPT.
Distinguish original files, uploads and generated outputs
A connected file remains associated with its original service. A document uploaded to ChatGPT and an output generated there are separate Library items. Employees should recognise these differences. Include the authoritative filename, storage location and required source date in the request. If several versions exist, ask the assistant to flag the discrepancy rather than silently choosing one. Follow the original-source link when checking important claims. The documented Google Drive integration includes My Drive and directly shared content; Shared Drives are not included in the help guidance checked for this article. This boundary matters when the company keeps its main documents in team storage.
Example: handing over a project across storage services
A project lead needs a handover based on an approved service description, a status report and an outstanding-task list. Instead of uploading everything again, they select the available source files in Library. The requested output is a table of task, owner, deadline and source. Conflicting dates remain open issues. The lead checks critical rows against the original documents before passing the handover on. This is a suggested process, not a documented customer result. Start with three clearly named files. Asking the assistant to work across a whole folder makes sense only when its contents, permissions and expected selection are sufficiently understood.
Multiple accounts require explicit selection
Broader multiple-account support can make information from different signed-in services available in one conversation. That is not a reason to mix personal and business information without a defined purpose. State the required account and data scope explicitly. When an employee works for several clients or business entities, associate each task with the correct one. Use a harmless test to confirm which connection was actually used. Permissions and actions still follow the connected accounts. A similarly named document in personal storage must not silently replace a missing business document. Account selection is part of the task specification, not a detail to leave unresolved.
Check sharing and ownership before distributing files
Depending on availability, Library sharing supports named recipients, workspace access and roles such as Viewer or Editor. For shared folders, uploaded files belong to the folder owner; a contributor who later loses folder access also loses access to files they uploaded there. Decide where authoritative project records should live over time. Read-only access is often sufficient for a handover. Test access from the recipient’s perspective and remove unnecessary content before sharing. Name the person responsible for reviewing access when the project ends. Deleting a conversation is also not a reliable way to remove files saved separately in Library.
Common questions about Library and connected files
Does visible mean editable? No. The connection, supported actions and permissions determine what is possible. Is every cloud file automatically an appropriate source? No: version, business validity and account selection still matter. What if a file is missing? Check the source, identity and enabled actions before substituting a manual upload. Should a team rely on one person’s private folder? Technical sharing capability and suitable business ownership are different issues. A pilot needs only a small documented file set. Evaluate whether each important statement traces back to the correct original and whether unauthorised recipients remain excluded, rather than checking only that a summary was produced.
Keep it verifiable
Primary sources
- OpenAI: Using Library to manage filesSource checked:
- OpenAI: ChatGPT release notes, September file and account updatesSource checked:
