SharePoint Integration

The SharePoint integration lets your company connect Microsoft SharePoint to IntuitivePM. Use it when documents in SharePoint should become trusted context for agent workflows without giving agents Microsoft credentials.

With SharePoint connected, company admins can:

• Connect SharePoint through Microsoft OAuth.
• Discover SharePoint sites.
• Enable specific document libraries and folders.
• Preview files before using them as Knowledge Sources.
• Let approved agents read selected SharePoint files through IntuitivePM.
• Review audit events that show which SharePoint scope an agent read.

How It Works

IntuitivePM connects to SharePoint through Microsoft OAuth and Microsoft Graph. The Microsoft token is stored and used by IntuitivePM on the server side. Users and agent runtimes never receive Microsoft Graph credentials.

When an agent needs SharePoint context, IntuitivePM checks the workflow lease, selected Knowledge Source, enabled site, enabled library, and enabled folder. IntuitivePM then reads the selected file through the server-side gateway, extracts safe text when supported, records citations and content hashes, and gives the agent only the scoped context for its current task or workflow run.

SharePoint write-back is not enabled yet. Agents can read approved SharePoint files, but they cannot edit, delete, upload, or overwrite SharePoint content.

Prerequisites

• A Microsoft 365 tenant with SharePoint.
• Company admin access in IntuitivePM.
• SharePoint enabled for your IntuitivePM company.
• Permission in Microsoft 365 to authorize the IntuitivePM app.
• Access to the SharePoint sites, document libraries, and folders you want IntuitivePM to use.
• Agent orchestration enabled if you want agents to use SharePoint files as workflow context.

The default Microsoft OAuth scopes are:

• offline_access
• User.Read
• Sites.Read.All
• Files.Read.All

Your Microsoft tenant may require administrator approval before these scopes can be granted.

Connect SharePoint

1. Open System -> Integrations -> Integration Hub.
2. Open SharePoint.
3. Review the tenant consent checklist.
4. Select Connect SharePoint.
5. Sign in to Microsoft when prompted.
6. Review and approve the requested permissions.
7. Return to IntuitivePM after the OAuth flow completes.

After connection, the SharePoint card shows connection status. Open the SharePoint details to inspect connection health, connected user, token expiry, enabled libraries, enabled folders, and recent operational events.

Enable Sites, Libraries, And Folders

SharePoint content is disabled by default after connection. This prevents agents from reading a whole tenant just because OAuth succeeded.

To enable SharePoint content:

1. Open System -> Integrations -> Integration Hub.
2. Open SharePoint.
3. Select the SharePoint connection.
4. Sync sites.
5. Enable the sites IntuitivePM may use.
6. Select an enabled site.
7. Sync document libraries.
8. Enable the libraries IntuitivePM may use.
9. Select an enabled library.
10. Sync folders.
11. Enable only the folders IntuitivePM may use.

Use the most specific folder that is practical. For example, enable Customer Docs / Project A / Requirements instead of the full Customer Docs library when only one project needs that context.

Preview Files

Admins can preview files from an enabled library or folder before attaching the source to a workflow.

1. Open the SharePoint details.
2. Select the enabled library or folder.
3. Enter a search term when needed.
4. Select Preview files.
5. Confirm that the expected files appear.

Previewing files confirms that IntuitivePM can list the selected SharePoint scope. It does not expose Microsoft tokens to the browser or to agents.

Use SharePoint As A Knowledge Source

Company admins can create SharePoint Knowledge Sources for workflow nodes.

1. Open AI Agents -> Knowledge Sources.
2. Select New Source.
3. Choose SharePoint.
4. Select the SharePoint connection.
5. Select the enabled document library.
6. Optionally select an enabled folder.
7. Save the source.
8. Attach the source to a workflow node that needs those files.

SharePoint Knowledge Sources are most useful for project requirements, policies, customer documents, onboarding material, runbooks, and other document sets that agents should cite while working.

What Agents Can Read

Agents can receive scoped SharePoint file context for the work they are assigned to. Supported runtime file reads include:

• Plain text and common text-like files.
• PDF files.
• Microsoft Word .docx files.
• Microsoft Excel .xlsx files.

SharePoint file downloads are limited to 10 MiB per file in the current rollout. If a file is too large or its text cannot be extracted, IntuitivePM records the failure and the agent does not receive that file’s content.

Agents receive extracted text, source metadata, citations, and content hashes. They do not receive Microsoft Graph credentials and they do not browse SharePoint directly.

Audit Source Reads

Company admins can review SharePoint source activity from the SharePoint connection details and from connector audit diagnostics.

Audit filters can narrow events by:

• SharePoint connection.
• Document library or drive.
• Folder item.
• File item.
• Action.
• Actor type.
• Source type.
• Time window.

This is useful when you need to answer questions such as:

• Did an agent read a SharePoint file during a workflow run?
• Which enabled folder or library did the read come from?
• Which file item was read?
• Which agent, runtime, task, or workflow run was involved?
• How much content was returned?

Security Model

IntuitivePM uses these guardrails for SharePoint:

• Microsoft Graph credentials stay on the IntuitivePM server.
• Agent runtimes never receive Microsoft OAuth tokens.
• SharePoint reads are scoped to the active company, connection, workflow, node, and lease.
• Sites, libraries, and folders are disabled until an admin enables them.
• Source content is treated as untrusted data and converted before agents use it.
• Runtime file reads return citations and content hashes.
• SharePoint write-back is not enabled in the current rollout.
• SharePoint reads and operational events are auditable.

Troubleshooting

Recommended Setup

For most teams:

1. Connect SharePoint from the Integration Hub.
2. Enable only one pilot site.
3. Enable one document library and one folder for the first workflow.
4. Create a SharePoint Knowledge Source from that enabled folder.
5. Attach it to a low-risk workflow node.
6. Run a test task and confirm the answer includes citations.
7. Review audit events before enabling more libraries or folders.

Related Guides

• Integration Hub
• Agent Orchestration
• Assign Work To Agents
• Jira Integration