{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreie6h3omajv252xfymdtr23ko5ki3nw5atqhs4hay4o3omg4rwovku",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mlgxc4bv5a22"
  },
  "path": "/t/sharepoint-onedrive-as-persistent-project-sources-real-world-document-workflow-use-case/1380582#post_1",
  "publishedAt": "2026-05-09T19:10:16.000Z",
  "site": "https://community.openai.com",
  "textContent": "Hi everyone,\n\nI would like to share a real-world use case regarding ChatGPT Projects and persistent Sources.\n\nI work in a professional administrative/document-management environment where we manage a large amount of structured documentation through Microsoft 365, mainly:\n\n  * SharePoint Online\n\n  * OneDrive\n\n  * Power Automate\n\n  * PDF document generation\n\n  * metadata-based document classification\n\n  * structured folder hierarchy\n\n\n\n\nOur workflows already rely heavily on:\n\n  * centralized document storage,\n\n  * naming conventions,\n\n  * metadata,\n\n  * automated PDF creation,\n\n  * indexed project folders,\n\n  * long-term contextual continuity.\n\n\n\n\nRecently I noticed the new “Sources” feature inside ChatGPT Projects, where Google Drive and Slack can already be connected as persistent sources.\n\nThis is extremely promising.\n\nHowever, in our environment, the real game changer would be:\n\n  * SharePoint Online\n\n  * OneDrive Business\n\n\n\n\nas native persistent Project Sources.\n\n## Why this matters\n\nToday, when using ChatGPT Projects, we still need to:\n\n  * manually upload files,\n\n  * re-upload updated versions,\n\n  * recreate context repeatedly.\n\n\n\n\nBut our actual document ecosystem already exists in SharePoint.\n\nExample:\n\nProject: “Example Administrative Case”\n\nPersistent source:\nSharePoint/Projects/ExampleCase/\n\nContaining:\n\n  * reports,\n\n  * meeting minutes,\n\n  * PDF correspondence,\n\n  * financial statements,\n\n  * automated documents,\n\n  * categorized records,\n\n  * historical archives.\n\n\n\n\nThe value would not simply be “opening files”.\n\nThe real value would be:\n\n  * persistent contextual continuity,\n\n  * multi-document reasoning,\n\n  * metadata-aware retrieval,\n\n  * continuously updated project knowledge,\n\n  * AI reasoning over structured enterprise content.\n\n\n\n\n## Additional point\n\nOur SharePoint structure is already AI-ready:\n\n  * metadata fields,\n\n  * consistent naming,\n\n  * automated document flows,\n\n  * categorized archives,\n\n  * PDF indexing,\n\n  * workflow-generated documents.\n\n\n\n\nThis feels like a very natural fit for ChatGPT Projects.\n\n## Questions\n\n  * Is SharePoint / OneDrive planned as full persistent Sources for Projects?\n\n  * Is there any beta or roadmap visibility for this?\n\n  * Are there recommended approaches for enterprise/document-heavy workflows like this?\n\n\n\n\nI would be very interested in testing or providing structured feedback if useful.\n\nThanks!",
  "title": "SharePoint / OneDrive as persistent Project Sources: real-world document workflow use case"
}