Connect SharePoint
Bring documents from a Microsoft SharePoint site into Keystone so people and agents can ask questions with sources.
Console sign-in stays email OTP. Microsoft sign-in is only used for the connector consent and site access.
Before you start
You need:
- A Keystone role of operator or owner
- A Microsoft account that can admin-consent apps for your directory (usually Global admin or SharePoint admin)
- The SharePoint site URL (and optional folder) you want to sync
- Preferably a team scope for that department (you can create one during connect)
Supported file types today include Word (.docx) and common text formats (.md, .txt, and similar). PDFs are not extracted yet.
Connect with Microsoft
- Sign in to Keystone → Settings → Connectors.
- Choose Connect SharePoint.
- Sign in to Microsoft and accept the consent prompt for your organization.
- On Choose a SharePoint site:
- Prefer pasting the site URL if search shows “No sites found” (new sites often miss search).
- Optionally set a folder path to limit the crawl (for example
Shared Documents/Policies). - Choose a Scope. For department libraries, pick a team scope—or use + New team scope on the same screen.
- Choose Connect and sync.
Keystone grants its app read access to the site you picked, then starts syncing.
After the first sync
- Open Sources. You should see documents with SharePoint titles under that connector’s scope.
- Open Ask and ask something only that library would know.
- On the connector card, check last-run stats (new/changed, skipped, removed).
If sync says ok but Sources is empty, see Sync and Sources.
Permissions and access (best practices)
Keystone maps SharePoint sharing into who can read the derived memory:
- Specific people and groups on the file are respected.
- Documents with no mappable permissions are skipped (not opened to everyone).
- “Anyone in the organization” links become readable by everyone who can see that connector’s scope—avoid them on department libraries.
People in the team scope you chose can recall that connector’s memory (along with mapped SharePoint users). Operators reviewing Sources can see ingested documents for troubleshooting.
Do
- Use a team scope per department site
- Share department files with the department group or named people
- Prefer
.docx/.md/.txtfor important policies
Don’t
- Point department content at the Organization scope
- Rely on org-wide sharing links for sensitive libraries
- Expect PDF-only libraries to produce facts yet
When files change or disappear
Sync runs about hourly by default. You can always click Sync now.
| Upstream change | What Keystone does |
|---|---|
| New or edited file | Ingests a new version and re-extracts facts |
| Sharing changed only | Updates access without re-downloading content when possible |
| File deleted or removed from the crawl | Removes that source and facts that only came from it |
Delete a test file in SharePoint, sync, and Ask again—those facts should disappear after the sync finishes.
Multiple sites
Use one connector per site (or folder) and a matching team scope. See Department isolation.