SharePoint & OneDrive Integration

LithicBlue connects to your Microsoft tenant through the Microsoft Graph API. A tenant administrator grants consent once for the organisation; then individual SharePoint sites can be connected to projects. The connection reads from SharePoint into LithicBlue, so edits are always made in SharePoint and flow through to the project: one authoritative copy of every document. Access respects your existing SharePoint permissions.

Open Settings → SharePoint in LithicBlue and click Start admin consent flow. You will be redirected to Microsoft to sign in as an administrator and approve the permissions LithicBlue requests.

1. In LithicBlue, go to Settings → SharePoint.
2. Click Start admin consent flow.
3. Sign in to Microsoft as a tenant administrator and review the requested permissions.
4. Approve. You are returned to LithicBlue and Step 1 shows Tenant consent active with your tenant ID.

With tenant consent active, the Connected sites section unlocks. Connect the site that holds your source documents. Each site shows its status:

• Active: connected and syncing.
• Awaiting site grant: the connection is registered but a site owner still needs to approve access. A site owner can approve it themselves via the connect flow, or you can ask an admin.
• Revoked: access was withdrawn; reconnect to restore it.
• Error: open the site to read the message.

Once a site is connected, map a folder to a project. LithicBlue mirrors the folder and keeps it in sync, so your team keeps working in SharePoint exactly as before.

Folders can overlap. You can map a client folder to one project and a workstream folder inside it to another, and each project gets its own copy of the files it covers, with its own analysis.

OneDrive for Business is part of the same Microsoft Graph connection. Files shared into a connected SharePoint site are available to the mapped project; keep project source documents in the SharePoint site so everyone on the project works from the same authoritative location.

A file carrying a Purview label that encrypts it syncs normally and appears in your project file list marked as protected, but cannot be analysed and contributes nothing to your insights. Labels that only add a visual marking are unaffected. Nothing about the file changes in SharePoint, and you can still open it there exactly as before. See how protected documents are handled.

If you need one analysed, speak to whoever manages sensitivity labels in your organisation: there is no password to supply for an encrypting label, so the change has to be made in the label policy. They can confirm which label is applied and whether it is the right one for a library shared with LithicBlue — a label that marks documents without encrypting them keeps the classification visible while still allowing analysis.

• “Admin consent error.” The Microsoft sign-in was cancelled or the account was not a tenant admin. Re-run Start admin consent flow with an administrator account.
• A file shows as protected. A sensitivity label that encrypts the document has been applied to it, so its contents cannot be read or analysed. The file stays in your project list and can still be opened in SharePoint. Your Microsoft administrator can confirm which label is applied.
• A site is stuck on “Awaiting site grant.” A site owner needs to approve access, either through the connect flow or via an admin.