Appearance
SharePoint Setup Beta
Many MSPs keep client runbooks, network diagrams, procedures, and onboarding documents in their own SharePoint. Connect SharePoint to sync those documents into Junto's knowledge base, where they're indexed for semantic search during ticket triage and in Explore. The agent can also browse and read the live files, and create or update documents with approval.
You choose which sites, document libraries, and folders to sync, and how each one is scoped: org-wide, one company, or a company per library or folder. The agent only ever sees the documents scoped to the ticket's company, plus the ones you share org-wide.
How Junto Connects
SharePoint connects through a Microsoft sign-in. There are no client IDs, secrets, or API keys to enter. Junto reads SharePoint as the account that signs in, so it can reach only the sites that account can open. Choose an account that can open every site you want to sync.
This connects your MSP's own SharePoint, not your customers' tenants. It's a separate connection from the Microsoft 365 integration, which manages your customers' tenants, and from OneNote. Junto supports one SharePoint connection per organization.
Prerequisites
- A Junto Admin or Owner account
- A Microsoft work or school account in your MSP's tenant that can open the SharePoint sites you want to sync
- Permission to grant the requested Microsoft permissions. Junto asks for delegated read and write access to sites and files (Sites.ReadWrite.All and Files.ReadWrite.All). Your tenant may require an administrator to approve these during sign-in.
- Companies in Junto, imported from your PSA, to scope documents to
Step 1: Connect SharePoint
- In Junto, go to Settings > Integrations > SharePoint.
- On the Connect SharePoint card, click Connect Microsoft account.
- Sign in through the Microsoft popup with the account whose sites you want to sync, and accept the requested permissions.
- When the card shows SharePoint is connected, click Enable SharePoint sync.
Once enabled, the settings page shows a connection strip with the connected Microsoft account, Tenant, and Last sync time, a Sync enabled switch, and a Disconnect button. Sync now and Add source sit in the page header.
Step 2: Add Sources
A source is a site, a document library, or a single folder.
- Click Add source.
- Search for a site by name and select it.
- Choose what to add:
- Add whole site -- Syncs the site's published pages and every document library on it.
- Open a library, then Add this library -- Syncs one document library.
- Open a folder inside a library, then Add this folder -- Syncs one folder and everything beneath it.
Locations you've already added are marked Added. A newly added source starts as Company per library (for a site) or Company per folder (for a library or folder), so nothing syncs until you finish scoping it.
Step 3: Scope Each Source
Select a source in the list to open its detail pane. Its scope decides which tickets can use its documents:
| Scope | What it means |
|---|---|
| Org-wide | Everything under the source is general knowledge, available on every ticket. For a site, its pages are included. Use this for internal procedures that aren't client-specific. |
| One company | Everything under the source belongs to one company. Pick the company from the Company list; nothing syncs until you do. For a site, its pages are included. |
| Company per library (sites) or Company per folder (libraries and folders) | Each document library, or each top-level folder, maps to its own company. Libraries or folders without a company are skipped. Suits the common layout of one folder per client. Site pages aren't synced with this scope. |
Switching scope on a source that already has mappings asks you to confirm. The old mappings stop being used, and the source's documents are filed again under the new scope on the next sync.
Map Libraries or Folders to Companies
For Company per library and Company per folder sources, the detail pane lists each library or top-level folder with a company picker:
- Auto-map by name -- Junto proposes matches between library or folder names and your Junto companies, marking exact matches. Review the proposals, then click Apply to save the ones you select.
- Manual mapping -- Pick a company for any row the auto-map didn't match. Leave a row Not mapped to skip it.
- Add new libraries automatically / Add new folders automatically -- When on, new libraries or folders created in SharePoint appear in the list on the next sync. They still need a company before they sync.
- Refresh -- Re-read the list of libraries or folders from SharePoint.
Sync
Junto syncs every active source daily. To sync sooner, click Sync now in the page header for all sources, or Sync source on one source. Each sync adds new and changed documents, skips unchanged ones, and removes documents whose file was deleted or whose source or mapping was removed.
Status badges show progress for each source and mapping: Synced, Syncing, Pending, Error, or Not mapped. A source in error shows the reason in the source list.
What Gets Synced
| Details | |
|---|---|
| File types | Word (.docx), PDF, PowerPoint (.pptx), text (.txt), and markdown (.md) |
| File size | Up to 25 MB per file. Empty files are skipped. |
| Site pages | Published pages, for sites scoped Org-wide or One company. Text from the page is synced; pages without text are skipped. |
| Per folder or library | Up to 5,000 files and 2,000 subfolders. Larger trees sync partially and show an error. |
| Not synced | Excel files, images, and other file types; encrypted PDFs. Scanned PDFs without a text layer contain no searchable text. |
Each synced document keeps a link back to its SharePoint file or page, so the agent can cite where an answer came from.
What the Agent Can Do
Once sources are synced, the agent searches your SharePoint documents in the knowledge base alongside your other documentation, always limited to the ticket's company plus org-wide sources. For live work, it has these tools:
| Capability | What Junto can do | Risk level |
|---|---|---|
| List locations | List the SharePoint locations the current company can use: its mapped libraries and folders plus org-wide ones | Low |
| Browse folders | List the files and subfolders inside a location, up to 1,000 items per folder | Low |
| Search files | Search the company's locations live by file name and content, including files added since the last sync | Low |
| Read document | Read the text of a Word, PDF, PowerPoint, text, or markdown file up to 25 MB. Long documents are read in parts. | Low |
| Create document | Create a new Word (.docx), markdown, or text file in one of the company's locations | Medium |
| Update document | Replace the full content of an existing Word, markdown, or text file | Medium |
All write actions require technician approval before execution. Read-only tools do not require approval. Every tool defaults to a minimum role of Technician. Admins can change either setting per tool under Tool Policies.
Scope and Behavior
- Company scoping: Every tool is confined to the locations mapped to the ticket's company plus org-wide locations. An item outside those locations is refused, even if the connected account can open it. In an organization-wide Explore chat, only org-wide locations are available.
- Where tools are available: The live SharePoint tools are available in Explore chat and ticket chat. During automatic ticket triage, the agent uses the synced documents through knowledge base search.
- Search: Live file search matches words in file names and content; it isn't semantic. For questions about what a document says, the agent searches the knowledge base first. A live search covers up to 10 libraries at a time, so narrow the request if results are cut short.
- Writes are fixed to their target: The destination folder, file name, or file being updated can't be changed after the agent asks for approval.
- Create: The file name's extension sets the format (.docx, .md, or .txt). Creating a file fails if a file with that name already exists in the folder; the agent updates the existing file or picks a new name instead.
- Update replaces the whole file: The agent reads the current document first and sends the complete new text. A Word document is rebuilt from that text, so custom formatting, images, and tables aren't kept. SharePoint keeps the previous version in the file's version history.
- New content and search: Documents the agent creates or updates become searchable in the knowledge base after the next sync. Until then, the agent can read them directly.
Example requests:
- "What does Acme's SharePoint say about their VPN setup?"
- "Find the network diagram in Acme's SharePoint folder."
- "Read Acme's onboarding checklist and summarize the steps for a new laptop."
- "Which SharePoint folders can you use for this ticket?"
- "Write up today's firewall change as a new document in Acme's SharePoint folder."
- "Add the new printer IP to Acme's network documentation in SharePoint."
Managing the Connection
- Pause syncing: Turn off Sync enabled on the connection strip. The page shows Paused, scheduled syncs stop, and the agent's SharePoint tools are unavailable until you turn it back on. Sources and mappings stay saved.
- Remove a source: Select the source and click Remove. Its company mappings are removed from Junto, and its documents leave the knowledge base on the next sync. Nothing is deleted in SharePoint.
- Open a source: Click Open in SharePoint to view it in SharePoint.
- Disconnect: Click Disconnect and confirm. Junto signs out of the Microsoft account, removes every source and its company mappings, and removes synced SharePoint documents from the knowledge base. Nothing is deleted in SharePoint.
Troubleshooting
- Sign-in fails or permissions can't be granted: Your tenant may require an administrator to approve the requested permissions. Have a tenant admin complete the sign-in, or approve the request in Microsoft Entra.
- "The Microsoft sign-in for SharePoint expired or was revoked": Click Connect Microsoft account and sign in again. Your existing sources and mappings are kept.
- A site doesn't appear in the picker: The connected account can't open it. Grant that account access to the site in SharePoint, or reconnect with an account that has access.
- Documents from a library or folder aren't showing up: Confirm the source's scope and that the library or folder is mapped to a company (unmapped rows are skipped). For One company sources, confirm a company is selected. Then click Sync source and check the status badge.
- A file isn't searchable: Check that it's a supported type, under 25 MB, and not an encrypted or image-only PDF. Files added since the last sync are searchable after the next one; the agent can still find them with a live search.
- "The folder is too large to sync in full": The folder or library has more than 5,000 files or 2,000 subfolders. Add smaller subfolders as separate sources instead.
- "This folder or library no longer exists in SharePoint" or "This site no longer exists in SharePoint": The location was deleted or moved. Remove the source and add its new location.
- "Sync ran out of time": Very large sources can take more than one run. The sync continues where it left off on the next run.
- The agent says no SharePoint folder is mapped to this company: Map a library or folder to that company, or set a source to One company for it.
- "SharePoint denied this request": The connected account can't read or write that file or folder in SharePoint. Check the account's permissions on the site.
- Create or update fails because a file exists or is locked: A file with that name already exists, or the file is checked out or open for editing. Choose a new name, or check the file in and try again.