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 Filevine projects, hand-off-able to Claude
Cohesive360 exposes your Filevine tenant to Claude through 32 purpose-built tools across 10 capability areas. Projects (read + update), contacts, notes, tasks, calendar, deadlines, document metadata, case team management, firm user directory, and Collections — Filevine's per-project-type custom data sections — with both reads and tenant-aware updates. Bound to your firm's API key, region-pinned to US or Canada, with writes that draft for review before they commit.
Projects, not tabs
Filevine calls cases 'projects' — the connector lets Claude search and open them, pull the case team, scan deadlines, draft notes, and create tasks without you clicking through a dozen tabs.
Per-user API key, scoped by your seat
Connect with an API Key + Secret generated inside Filevine's admin Settings → Integrations panel. Permission scope is whatever the admin who generated the key has — Claude inherits exactly that surface, no more.
US + Canada — pinned to one org
Tokens are region-scoped and your connection is pinned to one org. Switch orgs by disconnecting + reconnecting; multi-org users can keep a separate Cohesive360 seat per Filevine tenant if needed.
Plan tiers gate capability areas, not API access scope. For pricing, see the Pricing page.
Capabilities
1 workflow area in Team plan+. Click any capability to expand its “what you can ask” examples and the underlying tool names. Use the sidebar to jump.
Filevine's Collections are the per-project-type custom data sections firms model their workflows in — medical providers, witnesses, defendants, damages calculations, lien tracking. The connector exposes discovery (list project types → list sections → read items) plus an update path.
Filevine's Collections are the per-project-type custom data sections firms model their workflows in — medical providers, witnesses, defendants, damages calculations, lien tracking. The connector exposes discovery (list project types → list sections → read items) plus an update path.
What you can ask Claude
- “List the custom sections defined on the Garcia project's project type”
- “Pull every medical provider on the Lopez project”
- “Update the treatment-end-date on the Tampa General entry to last Friday”
Underlying tools (4)
list_project_typesget_project_type_sectionsget_project_collection_itemsupdate_collection_itemLimits and roadmap
What the Filevineconnector can't do today, and why. We update this when things change.
Pending vendor support
Documented endpoints that currently fail on production tenants. Support tickets open; vendor UIs work as the fallback.
- Authorization Code (OIDC) flow. Filevine supports OAuth 2.0 Authorization Code + PKCE for registered partner apps. We've built the helper but the live partner-app registration is pending Filevine's developer-relations approval.
On the roadmap
Technically possible but not yet prioritised. Email product@cohesive360.com if any of these would change your decision to roll out.
- Document upload + download. Filevine uses a two-step pre-signed-URL flow for binary files. The platform-side binary streaming layer is the same one powering SA + Clio document handlers; we're wiring Filevine through it in Phase 0.2.
- Collection item CREATE / DELETE. Phase 0.1.1 ships Collections read (get_project_type_sections + get_project_collection_items) and update (update_collection_item). Creating + deleting items are Phase 0.2.
- Time entries + billing. Filevine has a billing module. Surface is large; we'll prioritise it after the binary-document work lands.
Safeguards built into the connector
Defensive behaviours we put in the client because the underlying systems don't.
PAT-based auth — revocable from Filevine
Connect with an API Key + Secret. The key is bound to one Filevine admin user; the firm can revoke it instantly from Settings → Integrations → API Keys and the connector loses access on the next call.
Encrypted credential vault
Your API key + secret are stored in our credential vault: AES-256-GCM encrypted, master key in Azure Key Vault, ciphertext bound to your user ID + connector slug — a stolen blob can't be decrypted as another connector's credentials.
Permissions inherit the key owner's role
Filevine's API runs as the user who created the key. If that user can't see or edit a project in the Filevine UI, Claude can't reach it through the connector either.
1-hour bearer with proactive refresh
Filevine issues 1-hour bearer tokens via OAuth 2.0 client_credentials. The connector refreshes ~60s before expiry to keep calls smooth and falls back to exponential backoff on 429 with up to three retries.
Writes preview before commit
Notes, tasks, appointments, deadlines, and contacts all draft for review by default. You see the payload Claude is about to POST; one nod commits it through the API.
What Filevine via Cohesive360 is not
Honest boundaries — what Claude through this connector cannot guarantee.
Cohesive360 is a facilitation channel between Claude (Anthropic) and your Filevinetenant. 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.