What's new

Uploading the same .docx twice now triggers a Possible duplicate document warning that tells you which contract and version already contains the file, so you don't accidentally fragment your history across multiple records.

• Byte-level match — Fusial fingerprints every upload and compares against the versions already stored in your organization
• Catches both sides — the original file you uploaded and any identical file Fusial exported from another contract
• Scoped to your org and ignores deleted contracts
• Override when you mean it — click Upload anyway to add it as a new contract or version, e.g. the same template used on two unrelated deals

Ask questions about a contract in plain English without leaving the contract page. Chats are scoped per contract, shared with teammates who can see it, and notify prior participants when someone replies — but read-only: the assistant advises, it doesn't act.

• Two entry points — chat pill on the contract page, or a chat region in the inspector when you've opened a specific redline
• Grounded in the contract — title, type, your role, counterparty, status, latest extraction summary, key terms, and the surrounding paragraph for redline-scoped chats
• Threaded history — every chat persists per contract; a Chats popover in the top bar lists your recent conversations across the org
• Auto-titled — Fusial generates a short title after the assistant's first reply
• Notifications follow your preferences — in-app, email, and / or Slack, mutable per user as Chat reply
• Permissions match the rest of the app — viewers can read existing chats but can't start new ones or post
• Fully audited — start, reply, and delete are all recorded on the contract

Export final used to be blocked while any edit was still pending. Now you can ship a partial draft at any point in the review and finish the remaining decisions in Fusial afterward.

• Export stays available regardless of how many edits are pending
• Decided edits are applied to the recompiled .docx; pending edits are skipped, not preserved as tracked changes — they stay attached to the source version inside Fusial
• The new version is stamped with how many edits were skipped, and the skip count is recorded in the audit log
• The counterparty only sees decisions you've actually made

Two new actions in the contract More actions (⋯) menu give you a way to clear out your active workspace without losing the audit trail.

• Archive — moves the contract out of the active list while keeping every version, redline decision, comment, chat, and audit-log entry intact. Reversible from the same menu. Status filter on the contracts list now defaults to active statuses, so archived contracts stay out of your normal view until you ask for them.
• Delete — permanently removes the contract, all its versions, related data (edits, comments, assignments, chats), and the stored .docx files in object storage. The audit-log entry for the deletion is preserved so you keep a record of what was removed and by whom.
• Both are owner / admin / member actions; viewers cannot archive or delete.

Set up rules that run against every new contract after Fusial extracts it. Matching contracts get assigned, re-owned, or put on a different SLA — without anyone touching them. Contracts that don't match any workflow are ingested normally with default ownership and SLA.

• AI-powered matching — describe what the AI should look for in plain English ("contract contains substantial data privacy provisions"), and Fusial checks each upload against your rule
• Structured filters too — match on contract type (NDA, MSA, SOW, DPA, etc.), your role, counterparty relationship, or contract value
• Auto-assign with context — route matching contracts to the right person or team, with an optional note explaining why they're getting it
• Change ownership on the fly — reassign the contract owner based on what the AI sees
• Override the SLA — apply a stricter or looser deadline when a workflow matches, e.g. data privacy contracts get a 1-day legal review instead of the default 2-day
• Priority-ordered — lower priority numbers run first; when two workflows both override the SLA, the lowest number wins

Set deadlines on contracts based on their status, and get notified before things slip. Define an SLA rule once (e.g. "internal review must finish within 2 business days"), and Fusial tracks every matching contract automatically.

• Status-based deadlines — trigger an SLA when a contract enters a status like "In review," with deadlines measured in business days
• Auto-match or workflow-assigned — apply a rule to every new contract that matches, or scope it to specific workflows
• Pre-deadline warnings — get a heads-up 24 hours out, 4 hours out, or any cadence that fits
• Email and Slack notifications — owners and assignees are notified by default; add specific teammates per rule under "Also notify"
• Breach tracking — overdue contracts are flagged on your Fusial dashboard so nothing gets lost

Every action across your workspace is now recorded and searchable. Open Settings → Audit log to see who did what, when, and to which contract.

• Broad coverage — AI responses applied, reopened, or rejected; bulk decisions; edits and comments accepted or reopened
• Filter by date, action, or user — narrow down to a specific person, time window, or action type
• Search by user or contract title — jump straight to the events that matter
• Expand any row for the raw payload — see the underlying event data, including edit IDs and decision metadata