Tag: sharepoint
CLAUDE.md hierarchy: lock at two levels, split the libraries, audit the rest
CLAUDE.md hierarchy looks tidy in a personal repo. Push it across departments and it splits into a tree most users cannot reason about. Lock at two levels. Split read-only governance from read-write working content. Run a seven-check audit on every new file. Anything deeper is a vanity hierarchy that breaks in weeks.
How to make a single root CLAUDE.md load across your whole organization
Drop a CLAUDE.md at the root of a SharePoint site and nothing propagates. Each Claude product reads CLAUDE.md a different way. Four parallel loaders, all pulling from one canonical file, are what makes a single source of truth actually land in every session across Claude Code, Desktop, web, and Cowork.
SharePoint vs OneDrive for AI - where your files live decides what AI can see
When AI indexes your files, SharePoint and OneDrive expose data very differently. Here is how permission models, governance gaps, and the oversharing problem change everything about where you store documents for AI workflows.
Why organizing your files comes well before doing any sort of AI
A Seagate study of 1,500 enterprise leaders found 68% of business data went unused in 2020. AI amplifies whatever state your files are in. If SharePoint is a graveyard of duplicate presentations and orphaned project sites, AI just indexes the mess faster. File organization is not a nice-to-have before AI adoption. It is a prerequisite.
How to organize SharePoint and OneDrive so Claude can actually find your documents
Your SharePoint and OneDrive setup is organized for people browsing folders. Claude reads metadata. That mismatch is why the M365 Connector finds nothing useful and Cowork struggles with your files. Restructuring for AI access takes a weekend and pays off immediately.