Documentation
Confluence and SharePoint
Connecting REAP to Confluence (opens in a new tab) and SharePoint (opens in a new tab): prerequisites, permissions, setup, what is read and written, troubleshooting.
Overview
Planned, not available today: runbooks, design documents, standards and naming conventions ingested from these systems as citable context for investigations. Today, the same documents are ingested from files and agreed exports.
Status Planned Not available today and without a date. The sections below describe the design, so a reviewer can see what the integration would read and write; tell us if you need it.
Prerequisites
- Confluence Cloud (opens in a new tab)/Data Center or SharePoint Online (opens in a new tab) site
- Read-only integration identity with access to the agreed spaces/libraries
Permissions requested
| Scope | Permission | Why |
|---|---|---|
| Read | Named spaces (Confluence (opens in a new tab)) or document libraries (SharePoint (opens in a new tab)) | Organizational context |
Setup
- Identify the spaces/libraries that hold runbooks, designs and conventions.
- Grant read access to the integration identity.
- In REAP: Integrations → Knowledge → source, credentials, spaces; set refresh interval.
- Verify that a known document is citable in an investigation.
What REAP reads
- Pages and documents in the agreed spaces, with titles, timestamps and authors
What REAP writes
- Nothing
Troubleshooting
| Symptom | Likely cause | Check |
|---|---|---|
| Document not cited | Not in an ingested space, or not yet refreshed | Check the source list and last refresh time |
Changelog
- September 2026 · page created (draft).
Engineering to confirm
- Refresh interval defaults; file types supported
Last reviewed: October 7, 2026 (draft) · Owner: solutions engineering · Corrections: security@reapnet.ai