Close high value deals without complexity with contracts that are accurate, automated, and built into your CRM workflow.
Turn every contract into searchable, actionable data. Search across your portfolio, understand key terms, and stay on top of renewals and obligations.
Create, sign, and manage contracts in one place – integrated with your favourite tools to find your contract flow.
Filter
Google Workspace: source document link added to Oneflow docs
When a contract is created via the Oneflow add-on for Google Docs or Google Slides, Oneflow now attaches a direct link to the original source document in the Oneflow document.
What’s improved:
- Direct access to the original Google Docs/Slides file from the Oneflow document (respecting original access)
- Smoother handoff between drafting in Google Workspace and managing the contract workflow in Oneflow
Current limitation: changes made in the source Google Docs/Slides file can’t currently be synced back to the Oneflow contract.
Staff: Import documents across customer workspaces
Staff users can now import eligible documents from one customer workspace to another using a bulk operation, removing the need for manual engineering help.
This makes workspace moves faster and more reliable for customers, while reducing manual errors and freeing engineering time for product work.
Important details:
- This supports bringing documents from a workspace in Account A into a workspace in Account B.
- The existing merge process is still used when you need to move/merge entire accounts.
- This is an import/copy (not a move): the original documents remain in the source account.
- It’s not a full 1:1 transfer of everything around the contract (e.g. chats, tags, etc. are not included). Consider surfacing this clearly in Staff help.
- Documents are imported as PDFs and the “sides/parties” are recreated on the new document.
- All documents are imported except templates.
- Document state behavior:
- If the original was signed, the copy is marked signed with the original signed date.
- If the original is in any other state, the copy will be a Draft.
- Keeping the same state is not supported (it’s a copy/export-import flow, not a move).
- If the original has a duration box, the copied document will also have it.
- Duration reminders/notifications are not moved over as part of the import.
- Imports run in the background and can be tracked alongside other bulk operations.
- Users with limited access can’t be selected as the importer.
- The target workspace (destination) must be in the account currently open in Staff.
- If multiple workspaces need to be moved, the cross-account import is done one workspace at a time.
- No separate export/import of documents is needed.
- Tip: enable the feature flag skip_pdf_sections_imported to avoid “double footer” issues during PDF import (and to skip the party page). Remember to disable it after migrations.
What “parties recreated on the target side” means:
- The import creates a new document in Account B using the original as a template, attaches a copy of the PDF, and rebuilds the participant list to resemble the original.
- Company details copied: company name, org number, country, phone.
- “Our side” vs “other side” mapping is preserved.
- Internal users (our side): matched to Account B users by full name.
- Exactly one match → linked to that user.
- No match → added as a former participant (not a live user in Account B).
- Multiple matches → import fails for that document.
- Counterparties (other side): copied as guests (name, email, title, etc.), not linked to Account B users.
Other practical behavior:
- Organizers from the original are skipped.
- No emails/notifications are sent by the import (intended for archive, not re-sending).
- Signing method resets to e-sign (the new account may not have the same methods).
- If the original was signed, the new copy is marked signed with the original signed date.
- The Staff user running the import is added as organizer unless they already matched an existing role (e.g. signatory).
Product/UX note:
Several of the “practical behavior” points above (and the non-1:1 caveats like chats/tags not being included) are important enough that it may be worth surfacing them directly in Staff—both inline (similar to Account merge) and in Help.
Example use case:
A customer has several subsidiaries under one account, and one subsidiary is acquired by another company. You can move only the relevant workspace(s) to a different account—without merging the entire account.
New document list is now the default
We’ve fully switched to the new document list experience — the old document list has been removed and the new list is now the default for everyone.
Local fields (free text on PDF) now live on demo accounts
Local fields (free text on PDFs) are now live on all demo accounts, and the rollout has reached all accounts except Freemium.
Contract editors can create local data fields on the fly, place and reuse them anywhere in an agreement (including PDFs) without needing playbook or template-group access.
This reduces manual copy/paste and helps keep agreements accurate and consistent while we continue collecting feedback ahead of enabling it for all customers.
Help Center: https://support.oneflow.com/hc/en-se/articles/49761426437393-Local-Data-Fields
Content Search now includes PDFs & attachments (non-freemium)
Content Search now indexes PDFs and attachments across Oneflow contract sections, making it possible to search for information that lives inside embedded PDFs and uploaded files.
This update includes backfilling and reindexing so older documents become searchable too, helping teams find the right contracts faster and support post-sign workflows like reviews, follow-ups, and clause lookups.
Support for 150+ currencies in Document Value
Document Value now supports 150+ currencies, covering most commonly used currencies worldwide.
Microsoft Word version history in Oneflow
Microsoft Word add-in users can now view a Version History (audit trail) for contracts created from Word.
What’s included:
- Added/changed/removed content since the previous Word version (text, images, tables)
- Who made changes and when
- When the contract was created and last updated via the add-in
- Direct links to the Oneflow contract and the source Word document
Notes/limitations:
- Requires Track Changes enabled; accepted/rejected changes aren’t retained
- No formatting tracking, and no visual diff for images/tables
- 20 MB file limit per Word version
Local data fields — UI release (part 1)
We’ve started rolling out standalone data fields by exposing the Data field entry point in the Content sidebar (temporary frontend feature flag removed).
What to expect:
- Some users may see the new UI even if they don’t yet have access; functionality is unchanged.
- Users can now drag data fields from the Content tab as well as the Data Fields tab.
- Full standalone functionality still depends on backend support and permissions.
More backend and capability rollout will follow in subsequent releases.
Bulk actions: Select All for organizer management, move & delete
Bulk actions now support Select All, so actions can apply to all selected contracts—not just the ones currently visible on the page. Customers can add/remove organizers across multiple contracts, move multiple contracts, and delete multiple contracts at once across larger contract sets, saving time and reducing manual work.
Local fields (free text on PDFs) now live for demo accounts
Local fields (free text on PDFs) are now live for all demo accounts.
Contract editors can create local data fields on the fly, then place and reuse them anywhere in an agreement—including inside PDFs—without needing playbook or template-group access.
How it works: each datapoint must be its own data field so that when you set a value, it’s replicated everywhere that same field is used across the contract (unlike a normal “textbox” which wouldn’t stay in sync).
CSM feedback: replication is useful in some cases (e.g., initials on every page), but the team expects many “fill the gaps” PDF use cases where non-replicated free text would be more valuable.
Rollout plan: gather feedback next week; after Help Center updates, enable for all customers the week after (depending on internal stress testing).
Naming note: use “Local fields” consistently across surfaces and in external articles. Marketplace naming should already be fixed; follow-up planned with the team if anything still looks off.
Custom reports in Staff
Custom reports can now be managed directly in Staff—no more manual database work.
What’s new:
- View custom reports on the account Reports page
- Create and edit report configuration
- Activate/deactivate reports
- Delete reports
Access: Support and Development staff roles (view + manage).
Oneflow for Salesforce v5.21: contract creation reliability improvements
Smaller Salesforce package update focused on improving the reliability and usability of contract creation.
- Status badges now include icons for quicker scanning.
- Contract creation validates participant details and contract name before submission, showing clearer validation messages.
- UI fixes in the new contract creation flow, including template selection edge cases.
- Package API references upgraded to Salesforce API v64.0.
Create, sign, and manage contracts in one place – integrated with your favourite tools to find your contract flow.
