Skip to main content

6.5.2026 Release Notes

Figma integration, Excel & Outlook uploads, cancelable approvals, file-level scans across versions

Written by Daisy Akinbo

Warrant OS

Figma Integration

Connect your Figma workspace and import frames and pages directly into Warrant OS for compliance review. Multi-select is supported, so you can pull in a batch of designs at once and check text content against disclosure and brand requirements before anything ships, no exporting or screenshotting required.

New supported file types: Excel & Outlook templates

Warrant now accepts Excel files (.xlsx, .xls) and Outlook email formats (.oft, .msg) on the standard upload surfaces. They route through the same ingest and scanning pipeline as every other file type, so rate sheets, spreadsheets, and email campaigns can be reviewed without converting them first.

Cancel an approval flow

You can now cancel an approval at any stage, whether it's still pending or already approved. Canceling requires a quick confirmation and an optional reason, dismisses any outstanding approver tasks, notifies everyone on the flow, and records the action in the audit trail. Canceled flows stay visible with a clear status badge so the record always reflects reality.

File-level scans and approvals across versions

Scans and approvals now operate at the file level instead of being locked to a single version at a time. Run scans across multiple versions concurrently and approve at the file level, with scan and approval state visible across every version of a file.

Redesigned Customize Sheet for federal rules

The Customize Sheet was rebuilt and organized into clear sections (Identity, Scope, Geography, Applicability, Rule Logic, Lifecycle). Your team edits what it should, like severity and rule logic, while global values such as Regulator, Source URL, and Geography stay locked and consistent. Existing customizations are fully preserved.

Accurate source links on findings

Each scan finding's "View source regulation" link now points to the matched rule's actual stored source URL rather than a generic regulator homepage. If a rule has no source URL, the link is hidden instead of sending you somewhere unhelpful.

Did this answer your question?