November 2025 release notes (25.23)

Ziflow’s latest updates include a public preview of its new Figma plugin for in-app proofing, customizable mandatory Custom Properties at the intake form level, enhanced SCIM provisioning with user role support, expanded email sender controls for all plans, and new admin warnings to prevent errors when editing Custom Properties.

Now in Public Preview: Ziflow’s new Figma plugin

Ziflow’s all-new Figma plugin is now in public preview, bringing the full power of collaborative proofing directly into the design environment where creative teams work.

With this release, Figma users can create, version, and review proofs without leaving their design workspace—bridging the gap between design creation and formal review. The plugin transforms live design files into static, review-ready proofs, keeping reviewers aligned to a single version while eliminating manual exports, screenshots, or scattered feedback channels.

Key capabilities include:

• Proof creation from the Figma canvas: Turn your Figma frame or artboard into a static, reviewable proof in just a few clicks—no exports required.
• Version control: Upload new versions directly from Figma while maintaining a full audit trail of changes, comments, and approvals.
• Centralized feedback: Collect contextual feedback in Ziflow’s structured review environment, ensuring stakeholder comments are captured and tracked consistently.
• Simple access for reviewers: Reviewers don’t need a Figma login to participate, making feedback loops faster and more inclusive.

During the public preview period, we’re actively gathering customer feedback to refine the Figma plugin before general availability. If your team uses Figma, now’s the perfect time to test the plugin and share your input. Encourage your design team members who use Ziflow to download it from the Figma Community today! For more information, see Install and use the Figma plugin.

Making Custom Properties mandatory at the Intake Form level

Custom Properties have always had simple binary settings: they can either be set to “mandatory” for all proofs across an account or completely optional during proof creation. That global configuration hasn’t always worked well for teams that collaborate with external vendors, who may need to enforce specific data requirements while keeping things more flexible internally.

With this release, Ziflow now allows Admins to make specific Custom Properties mandatory at the Intake Form level—without requiring those same fields to be mandatory across the entire account.

This added flexibility helps creative operations teams ensure that external contributors complete all required fields (like “project name”, “project ID”, “campaign name”, “asset type”, et cetera) when submitting new proofs, while keeping internal workflows lightweight and adaptable. For more information, see Use intake forms for automated proof creation

Adobe Creative Cloud Plugins: New Changes required filter in Proofs view

We’ve added a new filter in Ziflow’s Adobe Creative Cloud plugins that allows users to quickly filter and view all proofs with the status Changes required. This makes it easier for designers to focus on proofs that need revisions directly from within their Adobe applications.

If your Admin has customized the name of the “Changes required” status, you’ll still see this default label in the filter menu. The filter will correctly reference all proofs currently in that status, regardless of the custom display name used in your account.

This update streamlines the review and revision process for creative teams, helping users quickly identify and act on proofs that need updates—without leaving their Creative Cloud workspace. For more information, see Ziflow Adobe plugin.

Pass user type information via SCIM

Ziflow has long supported SCIM (System for Cross-domain Identity Management) to simplify user provisioning, especially for teams using Okta or other SSO platforms. With this update, SCIM provisioning now supports passing user type information when creating new users in Ziflow.

Supported roles include: ZIFLOW_USER, ZIFLOW_LITE_USER, ZIFLOW_MANAGER, and ZIFLOW_ADMIN. If no user type is specified, the provisioned user will default to the standard User role.

This update was driven by customer feedback. Ziflow continues to evolve its integrations with single sign-on providers, and this improvement gives Admin, IT, and Operations teams more granular control over seat allocation and role management. For more information, see SCIM provisioning with Okta.

Users on all plan types can now specify email sender

Until now, only Admins on Enterprise plans were able to control the “sender” for proof notification emails, such as those sent when creating a new proof or version. With this release, we’re adding a new setting under Proofing Settings → Senders, allowing users on Free, Standard, and Pro plans to specify who notification emails should come from.

The new setting, “Sender of email when creating a new proof or new version,” includes the following options:

• Proof Owner
• User creating the proof or version
• System (default)

All other sender configuration settings will remain unchanged for Pro users.

This update gives teams on all of Ziflow’s subscription plans more flexibility in how review notifications are delivered—especially useful for teams that want emails to appear more personalized or better aligned with their internal communication standards. For more information, see Email Settings.

New warning message when editing Custom Property settings

Previously, changing a Custom Property’s configuration—like switching its type (for example, from single-select to multi-select) or modifying its values—could lead to errors or failures in connected automations, filters, or reporting. This issue was most visible with Ziflow Connect Flows that rely on those properties remaining consistent.

With this release, Ziflow will now display a confirmation warning when an Admin edits an existing Custom Property, which states that making this change is irreversible and may cause issues in areas where the property is used.

This added safeguard gives Admins a chance to double-check before applying a change that might impact downstream workflows, reporting, or automation.