SharePoint across Glean
Connecting SharePoint does more than add a search source. It makes your SharePoint knowledge available everywhere Glean works: in search, in Assistant answers, inside agent workflows, and as actions your tools can take. This page explains where that content shows up and how access stays under control on every surface.
Access is always scoped to each user's existing SharePoint permissions. A user only ever sees the sites, pages, and files they could already open in SharePoint, whether the content reaches them through search, an Assistant answer, or an agent. Connecting SharePoint never widens who can see what. For the full model, see permission design.
What SharePoint powers in Glean
Once connected, SharePoint content powers experiences across Glean:
Search
SharePoint pages, Office documents, PDFs, and list items become first-class search results, ranked alongside every other source you connect. Because Glean understands activity signals (who authored, edited, and engaged with a document), the most relevant and authoritative SharePoint content rises to the top instead of relying on keyword matching alone.
Users can narrow to SharePoint with the app:sharepoint filter, and results respect site and library structure so a result links back to its original location in SharePoint.
Assistant
Glean Assistant uses your SharePoint content as grounding for its answers. When someone asks a question that your SharePoint pages or documents can answer, Assistant retrieves the relevant passages, synthesizes a response, and cites the underlying documents so the user can verify the source.
Assistant draws on both indexed content and, when real-time search is enabled, content fetched live at query time, so answers can reflect documents created moments ago.
Agents
Agents read and summarize SharePoint documents as steps in automated workflows. An agent might pull the latest version of a policy page, extract the sections that changed, and route a summary to the right team, all while honoring the permissions of the user the agent runs on behalf of. See agents for how to build these workflows.
Tools (actions)
Beyond reading content, Glean can let agents and Assistant take actions against Microsoft 365. These actions run on the Microsoft 365 MCP server and are configured separately from the indexing connector. Use them when you want Glean not just to surface SharePoint knowledge, but to act on it.