Features by connector
Pick a connector to see exactly what Claude can read and write — and filter by plan tier to see which capabilities are included in Solo or unlock at Team+. Every tool is a slice of real work you can hand off in plain English and review before it lands in the system of record.
Your file server in Claude — read-only, on your network
Your Windows file share stays on your network. Cohesive360 reaches it through a small outbound-only Windows agent — no VPN, no inbound ports. Claude gets 4 read-only tools to browse folders, search files by name, and extract document text (PDF/Word/text). The agent sees only the folders your IT points it at, a path guard prevents escaping them, and it reads as a Windows service account so no file-server credentials are ever stored.
Your file server, no VPN
The documents on your Windows file share never leave your network. A small Windows agent that can open the shares dials OUT to Cohesive360 over HTTPS — no inbound ports, no VPN, no firewall changes. Claude browses and reads through the agent, locally.
Read-only, scoped to the folders you choose
Four read-only tools — browse folders, search files, read documents. The agent sees only the shares your IT points it at; anything outside those roots is invisible and unreachable, enforced by a path guard that refuses to escape the configured folders.
No file-server credentials stored
The agent reads as the Windows service account it runs as — you grant that account read access to the specific folders. Cohesive360 never sees or stores a file-server password; there's one less secret for your firm to manage.
Capabilities
2 workflow areas. Click any capability to expand its “what you can ask” examples and the underlying tool names. Use the sidebar to jump.
Browse & search
Read · 2 toolsList the folders and files under the shares the connector is pointed at, and search for files by name across a root (or all roots). Everything is addressed by a friendly virtual path — Claude never sees or needs the real UNC path.
Browse & search
Read · 2 toolsList the folders and files under the shares the connector is pointed at, and search for files by name across a root (or all roots). Everything is addressed by a friendly virtual path — Claude never sees or needs the real UNC path.
What you can ask Claude
- “What folders can you see on the file server”
- “List everything in Matters/Smith, John”
- “Find files named 'demand' anywhere under Matters”
Underlying tools (2)
list_folderssearch_filesRead documents
Read · 2 toolsPull a file's metadata (type, size, dates) and extract the text of a document — PDF text layer, Word (.docx), and common text formats — so Claude can summarise, quote, or reason over it.
Read documents
Read · 2 toolsPull a file's metadata (type, size, dates) and extract the text of a document — PDF text layer, Word (.docx), and common text formats — so Claude can summarise, quote, or reason over it.
What you can ask Claude
- “Read the demand letter in Matters/Smith, John and summarise it”
- “What's the size and last-modified date of that PDF”
- “Pull the text of the retainer agreement so I can check the fee terms”
Underlying tools (2)
read_documentget_file_infoLimits and roadmap
What the File Serverconnector can't do today, and why. We update this when things change.
Not in the vendor's API
Capabilities the vendor handles through admin UI or internal endpoints rather than the documented public API.
- Writing, moving, or deleting files. v1 is strictly read-only — browse, search, read. Uploading or editing files on a share would be a separate, explicitly-scoped release with a staged review flow, never a silent agent-side write.
- OCR of scanned documents. The agent extracts a PDF's text layer; image-only scans return a note rather than guessed text. OCR is a future option, not part of this release.
On the roadmap
Technically possible but not yet prioritised. Email product@cohesive360.com if any of these would change your decision to roll out.
- Cloud document stores (SharePoint, NetDocuments, iManage). This connector targets Windows file shares (SMB / UNC). Cloud and hybrid DMS platforms are separate connectors — NetDocuments and iManage are on the on-prem roadmap.
Safeguards built into the connector
Defensive behaviours we put in the client because the underlying systems don't.
Outbound-only agent — no inbound access
The agent opens no ports and accepts no inbound connections. It dials out to Cohesive360 over HTTPS (443) on a long-poll — nothing on the internet can reach your file server through it.
Root containment — can't escape the configured folders
Claude addresses files by a virtual path inside the shares you configured. Any attempt to traverse out (../.., an absolute path, a symlink pointing elsewhere) is refused before a byte is read — re-checked against the real path to defeat link tricks. The agent can only ever read inside the roots your IT chose.
Read-only, no stored credentials
Only browse/search/read operations exist — there is no write, rename, move, or delete path in the agent. It reads as a Windows service account you grant, so Cohesive360 stores no file-server credentials at all.
We store no document data
Cohesive360 transports the request and streams extracted text back to Claude; we don't persist file contents or listings. Audit logs record the tool name and timestamp only — never the document.
What File Server via Cohesive360 is not
Honest boundaries — what Claude through this connector cannot guarantee.
Cohesive360 is a facilitation channel between Claude (Anthropic) and your File Servertenant. Claude's responses are Anthropic's output; the underlying data is the vendor's system of record. We transport requests and responses; we do not generate, review, or validate Claude's output, and we do not operate the vendor's API.
Claude can be wrong. It can misread a record, misinterpret a date, draft against the wrong matter, or summarise incorrectly. Treat every draft as a draft — review it before you accept it, particularly anything that affects a deadline, a client communication, or a matter already in motion.
The vendor can be unavailable. The API can rate-limit, return errors, or reject requests for reasons specific to your tenant configuration. When that happens, Claude will tell you — but we have no control over when or why the vendor refuses a call.