Source
SharePoint, read where it already is
A SharePoint site is usually where the deal file, the matter file or the engagement file actually lives — along with every permission decision somebody made about it. Nemosyne reads the documents and takes the permissions with them.
What it captures.
- Documents in the site's libraries — Word, PDF, Excel, PowerPoint and the rest.
- The folder structure, which is often the only statement of what a document is about.
How it behaves.
- Authentication
- OAuth, against your Microsoft tenant.
- Permissions
- Per item — see below.
- Scope
- One site per connector, named when you register it. A connector with no site named is refused rather than allowed to read the whole tenant.
- A document
- One file. A 200-page PDF is one document; so is a one-page memo. Cost follows the reading, not the filename.
- Sync
- Continuous; only what changed is re-read. A failed pass backs off rather than starting over.
- Writes
- None. Nothing is ever written back into SharePoint.
What this means for permissions.
SharePoint's permissions carry through: a library only the deal team can open produces facts only the deal team can see, and a person who cannot open a document gets answers assembled without it. A fact drawn from two documents is visible only to people who can open both — permissions can narrow, never widen.
What we enforce, and the limits we publish →Questions this raises.
- Can it read more than one site?
- One connector serves one site. Connect several if you have several; each keeps its own credential and its own scope.
- What happens when access is revoked?
- Revoking access removes it from answers.
- Does it need admin consent?
- It needs an app registration in your tenant and consent for the scopes it reads with. It never asks for write scopes.
Connect it to what you already use.
Free for three people and about a hundred documents. No card, no expiry.
Start free →See also Google Drive · Salesforce · Slack · Gmail · HubSpot