Select a system to see how Sandstone connects.
- Zip
- Procurement intake that legal can actually finish. Vendor requests opened in Zip become legal matters with the purchase context attached. Sandstone maps supplier fields, pulls related agreements, and writes status back so procurement does not chase email.
- Coupa
- Spend and supplier data on every review. Coupa purchase orders, suppliers, and contract records sync into the matter graph. Counsel sees live commercial terms while drafting, and approved language can flow back into Coupa.
- iManage
- Work from the DMS you already trust. Sandstone reads workspaces and versions in iManage, extracts parties and obligations, and can file finished work back to the same matter — no second repository.
- NetDocuments
- Cabinets and workspaces as live context. Point Sandstone at NetDocuments cabinets. Precedents, playbooks, and executed files stay where they are, while the add-in and agents use them as structured context.
- OneDrive
- Folder-level sync for drafts and precedents. Map OneDrive folders into a matter. Sandstone watches for new drafts, keeps versions aligned, and uses those files as context for redlines and intake.
- Dropbox
- Shared folders without a migration. Connect Dropbox folders for automatic document context and two-way handoff. Legal keeps the shared-link workflow; Sandstone understands what the files say.
- Google Drive
- Drive files in the matter graph. Google Drive documents stay in place. Sandstone extracts terms, links counterparties, and keeps the Word and Docs workflows working from the same source of truth.
- SharePoint
- Libraries you already own. Point Sandstone at SharePoint libraries instead of exporting them. Auto-sync keeps site content current, and playbooks can cite the policies already stored there.
- Box
- Box as the system of record. Use Box for storage while Sandstone extracts terms, parties, and obligations. Finished drafts and executed copies can be filed back to the original folder.
- Asana
- Tasks that become legal work. Asana tasks convert into Sandstone requests with the project and assignee intact. Comments and completion write back so the business board stays current.
- Jira
- Tickets in, updates out. Intake Jira issues, gather the linked tickets and attachments, and post status or a drafted reply on the issue — without asking engineering to live in a legal portal.
- Linear
- Product issues with legal attached. Linear issues that need counsel become tracked requests. Assignees, priority, and comments stay aligned so product and legal share one thread.
- ClickUp
- ClickUp tasks routed to the right lawyer. ClickUp tasks open as intake in Sandstone. Assignment, comments, and done-status sync back so ops teams do not rebuild the same tracker twice.
- HubSpot
- Data sync for context — deals, contacts, companies. HubSpot objects sync into Sandstone as business context. Every request arrives with deal stage, contact history, and company records so counsel is not asking sales for the same fields again.
- Salesforce
- Data sync for context — accounts, opportunities, contracts. Beyond the seller add-in, Salesforce fields sync as structured context. Opportunity value, account hierarchy, and related contracts attach to the matter automatically.
- SAP
- Vendor, PO, and entity data on the review. SAP vendor masters, purchase orders, and legal entities map into Sandstone. Reviews start with the commercial picture already in the file.
- Notion
- Wikis that become living playbooks. Notion pages and databases sync as policy and playbook context. When the wiki changes, the positions Sandstone applies in Word can change with it.
- Confluence
- Spaces as institutional memory. Confluence spaces feed the knowledge graph. Policies, runbooks, and decision pages sit next to the contract they govern.
- DocuSign
- Send, track, and file envelopes from the matter. Launch DocuSign envelopes from Sandstone, watch status, and file completed documents back to the repository or DMS you already use.
- ServiceNow
- Enterprise tickets with legal context. ServiceNow incidents and requests that need counsel become Sandstone matters. Updates and attachments write back to the ticket so ITSM stays the system of record.
- Trello
- Boards that do not lose legal work. Trello cards convert into tracked requests. Comments sync both ways so a simple board can still drive a complete legal workflow.
- Zendesk
- Support tickets that need counsel. Zendesk tickets escalate into structured matters with the customer thread attached. Legal can reply from Sandstone or the Word add-in without losing the ticket ID.
- Ironclad
- CLM workflows plus Sandstone context. Keep Ironclad as a contracting system of record. Sandstone adds intake, Word-native redlines, and cross-channel replies so CLM is not the only place work can start.
- Workday
- Org and worker data before the first draft. Workday workers, orgs, and entities sync as context for employment, vendor, and policy matters. Requests start knowing who is involved and which entity is signing.
- Okta
- SCIM provisioning from the directory you already run. Okta users and groups sync through SCIM so Sandstone membership, teams, and roles stay mapped to your identity provider. Counsel is provisioned the same way as the rest of the company — no second user list.
- Google Workspace
- Identity and groups from Google, mapped into Sandstone. Google Workspace users and groups provision over SCIM. Seat assignment and team membership follow the org structure you already maintain in Admin Console.
- Microsoft Entra
- Entra ID as the source of truth for who can sign in. Microsoft Entra users and groups map into Sandstone through SCIM. Role and team assignment stay aligned with the directory, so access follows corporate identity.
- Ramp
- Spend and vendors attached to the review. Ramp vendors, cards, and bills attach to the legal review that follows the money. Counsel sees what was purchased and by whom without exporting a CSV.
Opp-1842 · Acme
Re: Acme MSA
Alex RiveraDM
