Forward
Native integration · Microsoft Graph OAuth

OneDrive + SharePoint integration

Forward connects to your Microsoft 365 OneDrive and SharePoint document libraries via the Microsoft Graph OAuth flow. Indexes spec PDFs, finish schedules, as-builts, and anything else your team keeps in OneDrive.

What Forward reads

  • Specifications (project manual PDFs, division-level files)
  • Finish schedules (FF&E plans, color-coded room schedules)
  • As-builts (record drawings, redline overlays)
  • Equipment cut sheets + submittal data archives
  • Photos archived from the field
  • Any other text-indexable file (Word, Excel, PDF)

Forward indexes the configured project folder on connect. Re-indexes incrementally as files change. Reads only — no writes, no edits, no deletes.

Microsoft Graph OAuth + permissions

  • Authority: /common — works with both personal Microsoft accounts AND Entra ID (Azure AD) tenants. One app registration handles every customer.
  • Delegated scopes requested: Files.Read.All, Sites.Read.All, offline_access, User.Read.
  • No Files.Write scope; Forward physically can’t modify your files.
  • Revoke at any time from Microsoft account → Privacy → Apps. Revocation terminates Forward’s access on the next API call.

Why OneDrive matters

Procore + Autodesk hold the project-management surface (RFIs, drawings, submittals). But specs, finish schedules, and equipment cut sheets often live in the GC’s OneDrive — owned by the architect or shared by the owner. Without OneDrive indexed, the bot can’t quote spec section 09 51 13 verbatim. With it indexed, spec retrieval is a 4-second text round trip.

See /use-cases/spec-search for the spec-section retrieval flow.

Setup time

~15 minutes of OAuth + folder-selection. The initial index typically completes in 5-15 minutes depending on file count. Re-indexing on file changes is automatic.