/ New releases · 5 min read

ChatGPT Library: work across connected business folders

ChatGPT’s Library update brings supported connected folders into the file workflow. Use it to select the right documents, compare versions and keep a clear trail back to the originals.

Reviewed 2026-09-28

What changed on 10 September 2026?

OpenAI’s 10 September 2026 release notes describe a Library update for working with folders from supported services including Box, Dropbox and SharePoint. It makes it easier to bring connected files into a conversation instead of repeatedly finding and uploading individual copies.

The practical benefit depends on a basic discipline: choose the right folder and the right version. Easier access does not resolve contradictory documents or tell you which draft your manager approved.

Check access before planning the workflow

The update is rolling out on the web; check your plan, workspace and connected-app availability. OpenAI’s published plan wording is not consistent enough to treat every account as eligible. Mobile support was described as following later, so do not assume the web workflow is already available on your phone.

Existing source-file permissions still matter. Connect only an authorised service and select material you are permitted to use. If a folder is missing, check the connection and its permissions rather than copying private files into a broader shared location.

Worked example: compare two quarterly plans

Imagine a fictional operations team with a Q3 plan, a proposed Q4 plan and a separate approved budget in its business drive. The manager wants to know which commitments changed and which still need approval.

A general summary of all three files could blur the difference between a proposed action and an approved one. Your brief should name the purpose of each document. The Q4 proposal can explain what is being requested; the approved budget establishes what has actually been authorised.

Before starting, note the filenames, dates and approval status yourself. If those details are unclear, resolve them with the document owner. An AI should not choose an authoritative version simply because its filename includes “final”.

Use the connected Library step by step

  1. Connect the approved supported service through your account’s available app controls. Review the access requested.
  2. On the web, open Library and select the relevant folder, or use Add from library or a supported mention from the conversation. The current Library help page explains the available controls.
  3. Identify the exact documents and versions you want compared. Ask the tool to list the files it can use before it starts.
  4. Give each file a role: previous plan, proposed plan or approved reference. Ask for changes and unresolved conflicts.
  5. Open the original sources for the changes that affect budgets, deadlines or customer commitments.
  6. Save a checked decision note with the source filenames and dates. Keep approval decisions in the team’s normal record system.

Copy this original comparison brief

Prompt to adapt

Use only these selected files: [Q3 approved plan], [Q4 proposed plan] and [approved budget]. First list the filenames and any visible version dates. Compare commitments by topic. For each change, show the previous position, proposed position, source location and whether the approved budget supports it. Do not treat a proposal as approval. Flag conflicting dates or amounts and write “not confirmed” when a file does not answer the question. Finish with the decisions the operations manager needs to make. Do not change, move or share any source file.

Check version conflicts and missing evidence

Suppose the proposed plan adds two training sessions while the budget only funds one. The useful answer is a visible decision gap. It should not quietly assume the budget will increase, or delete the second session to make the documents agree.

Ask for a short supporting extract where a conclusion matters. Open that passage in the original and check the context. A heading, link or filename alone does not prove the interpretation is right.

Connected files can also change after you complete the review. Record when you checked them and which versions supported the decision. For a significant decision, preserve an approved record using your organisation’s normal process.

Start small and keep the source of truth clear

Begin with a small folder and a question whose answer you can verify. You do not need to connect the whole company drive to learn the method. If your account does not have the new Library controls, a permitted manual upload can still support the document-comparison exercise; it is a different access route.

For help practising this with your team’s document workflow, use the workshop enquiry form on the 27 AI homepage.

Common questions

Does connecting a folder make all its files public?

Do not assume that. Source permissions and the connected service govern access, and you should review the permissions requested. This guide does not ask you to publish or broaden access to files.

Can I use this Library update on mobile?

The cited release describes a web rollout with mobile support to follow. Check the current official guide and your account before relying on mobile availability.

What if two files disagree?

Show the conflicting statements and their sources. Ask the document owner which is authoritative; do not let the AI silently choose a version.

Sources and further reading

Feature details can change. These sources were checked on 2026-09-28.