SharePoint / OneDrive as persistent Project Sources: real-world document workflow use case
Hi everyone,
I would like to share a real-world use case regarding ChatGPT Projects and persistent Sources.
I work in a professional administrative/document-management environment where we manage a large amount of structured documentation through Microsoft 365, mainly:
SharePoint Online
OneDrive
Power Automate
PDF document generation
metadata-based document classification
structured folder hierarchy
Our workflows already rely heavily on:
centralized document storage,
naming conventions,
metadata,
automated PDF creation,
indexed project folders,
long-term contextual continuity.
Recently I noticed the new “Sources” feature inside ChatGPT Projects, where Google Drive and Slack can already be connected as persistent sources.
This is extremely promising.
However, in our environment, the real game changer would be:
SharePoint Online
OneDrive Business
as native persistent Project Sources.
Why this matters
Today, when using ChatGPT Projects, we still need to:
manually upload files,
re-upload updated versions,
recreate context repeatedly.
But our actual document ecosystem already exists in SharePoint.
Example:
Project: “Example Administrative Case”
Persistent source: SharePoint/Projects/ExampleCase/
Containing:
reports,
meeting minutes,
PDF correspondence,
financial statements,
automated documents,
categorized records,
historical archives.
The value would not simply be “opening files”.
The real value would be:
persistent contextual continuity,
multi-document reasoning,
metadata-aware retrieval,
continuously updated project knowledge,
AI reasoning over structured enterprise content.
Additional point
Our SharePoint structure is already AI-ready:
metadata fields,
consistent naming,
automated document flows,
categorized archives,
PDF indexing,
workflow-generated documents.
This feels like a very natural fit for ChatGPT Projects.
Questions
Is SharePoint / OneDrive planned as full persistent Sources for Projects?
Is there any beta or roadmap visibility for this?
Are there recommended approaches for enterprise/document-heavy workflows like this?
I would be very interested in testing or providing structured feedback if useful.
Thanks!
Discussion in the ATmosphere