Share your feedback
Vertical swim lanes in workflow maps
Add Vertical Swim lanes to Workflow Maps Today, the workflow editor does not support vertical swim lanes. That makes it difficult to represent phases in a cross-functional process map using the layout people expect for this type of workflow. Desired: Let editors create vertical swim lanes and use them to organize the phases of a process map, so teams can see how work progresses across the process at a glance. Business Justification: Clear phase-based lanes make cross-functional workflows easier for admins to build and for employees and stakeholders to follow. This improves process readability and reduces the need for layout workarounds when documenting handoffs and ownership across phases.
Duplicate existing tool entry to add new instance
Today: When an admin adds a tool from Search tools, adding another instance of the same SaaS application requires repeating the setup manually. This becomes repetitive when an organization tracks separate instances of a product, or many Excel- and SharePoint-based tools, with different names, owners, URLs, or business units. Desired: Let admins create another instance from an existing tool entry or search result, using the existing tool details as a starting point. Admins should be able to edit instance-specific fields, including name, owner, URL, and business unit, before saving each instance as a separate tool record. Business Justification: Enterprise organizations often manage multiple deployments or workspaces for the same application, while smaller organizations may track many spreadsheet- and SharePoint-based tools. Reusing the existing tool details would reduce repetitive data entry, make catalog setup faster, and help admins maintain consistent records without losing the distinctions between instances. Acceptance Criteria An admin can start a new tool instance from an existing tool entry or its search result. Relevant tool details are prefilled, and the admin can edit name, owner, URL, and business unit before saving. Saving creates a separate tool record and does not overwrite or modify the source entry. The new instance appears in the Tools section and can be managed independently. Video Experience & Feedback
Default Workflow Step tool lookup to Tool tab definitions
Today, when adding a tool to a Workflow Step, the lookup box does not default to the tools already defined in the Workflow's Tool tab, so editors have a large list of tools to search from. Desired: when an editor adds a tool to a Step, preselect or prioritize the tools defined in the Tool tab as the lookup box's default options, while editors can still search for and select other available tools when needed. Business justification: reusing workflow-level tool definitions makes Step setup faster and more consistent, reducing repetitive searching and selection errors, especially for admins configuring many Steps across enterprise workflows. Acceptance criteria: Tools defined in the Tool tab appear as the default options when adding a tool to a Workflow Step. Editors can still search for and select other available tools. Existing tool definitions and Steps remain unchanged until an admin edits them.
View-and-comment role for organization users
Add a View and Comment permission type for organization users, alongside the existing Owner, Admin, and Editor roles. Desired: Add a View and Comment permission type. Users with this role should be able to access and read SOPs and add comments when clarification or feedback is needed, while being excluded from billing-impacting permissions and other administrative or editing controls. Business justification: teams need to share operating procedures with a broader audience without granting unnecessary access. A least-privilege role lets employees and stakeholders contribute feedback while reducing permission-management overhead, limiting accidental changes, and keeping billing and administrative responsibilities with designated owners. Acceptance criteria: Admins can assign an organization user the View and Comment role. Users with this role can view SOP content and add comments. Users with this role cannot edit SOP content or access billing and organization-admin controls. Existing Owner, Admin, and Editor permissions continue to work as they do today.
Sort the Tool List Alphabetically
Tools added to a workspace are currently listed by renewal date in the Tools Canvas sidebar. It would help to have a sort option for this list, including A-Z, so tools are easier to scan and find as the list grows.
Show Run Counts and Path Distribution on Connectors
Many processes need a way to quantify how work flows through them. It would help to enter the number of runs on a step and see how those runs split across paths. For example, on a conditional step, show that 40% of runs follow path A and 60% follow path B, with those figures displayed directly on the connectors. This would make it easier to plan scenarios and spot where volume goes, such as how many people answered “yes” versus “no”, or how many leads arrive from each source.
Private Notes on Workflow Steps
Agencies and consultants who map processes for clients often need to keep their own working notes on steps, separate from the documentation the client sees. It would help to have private notes on a workflow step that only the workspace owner and admins can view. These notes would not appear in public Shared Views. This is different from locked notes, which would still be visible to external viewers and only restrict editing.
Focus Mode for a Selected Step and Its Connections
In larger workflows, it can be hard to follow one step and the steps it connects to. It would help to have an option that greys out every other step when a step is selected, so only the selected step and the steps connected to it stay in full color. This would make it easier to trace a single path through a busy canvas and to focus on one part of a process at a time.
Comment Type Badges and a Filterable Comments Sidebar
Right now a step shows a single generic comment icon, so there is no way to tell what kind of comments it holds without opening it. A step with three pain points and a step with three ideas look the same on the map. It would help to have: Badges by comment type on the step: instead of one generic icon, each type gets its own color and count, for example “3 ideas, 1 pain point”, so the map shows where ideas, decisions and roadblocks sit at a glance. A filterable comments sidebar: clickable type icons that surface all comments of one type across the workflow. A setting to show or hide the badges: useful when sharing a map with stakeholders who may not need to see every pain point at first glance.
Create and List Workspaces via MCP
Through MCP, an agent can build most of a Puzzle workspace: tabs, teams, people, tools, maps and shared views. The workspace itself still has to be created by hand. Today that takes five steps: create it in the web app, copy its ID from the URL, add a new connector, restart, and sign in again in a browser. This makes it hard to onboard multiple organizations without manual work each time. It would help to have: Create workspace: takes a name, with an optional description and Tool Template, and returns the new workspace’s ID, URL and MCP link. List workspaces: returns every workspace the signed-in account can reach, with ID, name and URL. Immediate access: the existing sign-in reaches a newly created workspace right away, with no fresh browser login. Use case: a nonprofit gives every organization it serves its own workspace. An AI guide interviews each organization, reads their existing documents, and maps their journey in Puzzle for them to review and approve. Naming a Tool Template at creation would let each new workspace start fully stocked. Getting the new workspace ID back would also let an agent confirm that later writes land in the right workspace. This pairs with the long-lived API token request.
Featured Asset on Step Card
Currently, assets linked to a step are accessible through the step sidebar. It would be useful to designate a “featured asset” on a step, similar to how a featured tool works, so that the asset link is clickable directly on the step card on the canvas without needing to open the sidebar.
Automation Summary in Shared Views
We’re adding the Automation Summary to Shared Views at both the workspace and section level — so stakeholders viewing a shared link can also see the automation coverage of the processes you’ve shared with them.
New Navigation — Collapsible Sidebar with Folders
We’re redesigning the workspace navigation. The top bar is being replaced with a collapsible sidebar that organizes your Workflows, Teams, People, Tools, and Changelog in one place. You’ll also be able to create folders to group multiple tabs — giving you more flexibility to organize larger workspaces. A new global search (Command-K) lets you find anything across your workspace instantly.
Manage People-Tool Associations via MCP and Nova
We’re adding the ability to associate tools to people through MCP and Nova. You’ll be able to assign which tools a person is responsible for directly through AI — without having to configure it manually in the People canvas.
Configure Go-to, Alias, and Subflow Steps via MCP and Nova
We’re adding the ability to configure Go-to, Alias, and Subflow steps through MCP and Nova. You’ll be able to set the target steps and sections for these special step types directly through AI — making it easier to fully build out complex workflows without switching to the app.
Long-Lived API Token for Programmatic Puzzle Connections
Currently, connecting to Puzzle programmatically requires an interactive OAuth flow that needs to be re-authorized periodically — which works fine for individual use but isn’t practical for hosted apps connecting on a user’s behalf. A long-lived token (either a static API key or an OAuth refresh token scoped to a single workspace) would unlock use cases that public Shared Views and embeds can’t cover, such as keeping boards private behind a login, letting an app list and select workspaces and sections dynamically, and writing back to a board as plans change — all without requiring the user to re-authenticate each time.
More AI Models Available for BYOK
We’re expanding the model options available when using your own API key. In addition to existing options, you’ll now be able to connect Puzzle’s AI features to additional Claude (Anthropic) and OpenAI models — including GPT-4o Astra — giving you more flexibility and control over which AI powers your workspace.
Assets on Tools and Steps
We’re introducing Assets — a new way to attach and track resources directly on tools and steps. Each tool will have a new Assets tab where you can add items like documents, forms, webpages, workflows, and more, with a name, URL, type, description, and status. Assets linked to a tool will also appear on any associated steps, right below the Notes section in the step sidebar. You can manage assets through the app or via MCP and Nova.
Side-by-Side Cost Comparison
We’re adding a Cost Comparison tab to the workspace that lets you compare process costs across multiple sections or tabs. Set a current state and a future state, and get an aggregate breakdown of labor costs, tool costs, and labor hours — plus a net cost difference and projected annual savings. This feature is available on the Optimizer plan.
👥People Tab - Remapping Subordinates
📍 Today:When an admin needs to remap subordinates in the People Tab, the workflow is too manual and disconnected from the visual org structure. There is not a simple way to click an employee, choose a new manager, and have the reporting relationship update directly in the view. That creates friction in a process that is usually time-sensitive, especially during reorganizations, manager changes, acquisitions, or backfills. Admins have to work around the UI instead of making the change where they are already reviewing the org structure. ✨ Desired: Allow admins to click on an employee in the People Tab, select or search for the new manager, and have the system automatically redraw the reporting line in the org view. Ideally, this should feel like a direct-edit experience: Select employee Choose new manager Save the change Automatically refresh the org relationship and visual hierarchy This is the pattern enterprise admins expect from org management tools. Platforms like Workday and ServiceNow reduce admin effort by letting structural changes happen in context instead of forcing users to leave the org view and update records elsewhere. 📊 Business Justification: At enterprise scale, org changes happen constantly. A faster remapping workflow matters because it: Reduces admin overhead for HRIS and platform administrators managing frequent reporting-line updates Improves data accuracy by reducing manual steps and the risk of mapping someone to the wrong manager Improves the user experience for admins who are already using the People Tab as the source of truth for org structure Supports change management during reorganizations, manager transitions, and large-scale hierarchy cleanup Helps the product scale better for larger customers where org updates can affect dozens or hundreds of employees at a time Even small workflow improvements here can save meaningful time, reduce support requests, and make org maintenance feel much more intuitive. ✅ Acceptance Criteria An admin can select an employee directly from the People Tab org view An admin can search for and assign a new manager from that interaction Saving the change updates the reporting relationship without requiring the admin to navigate away The org chart redraws automatically after the change Permission rules ensure only authorized users can remap reporting relationships The experience works reliably for both one-off changes and repeated org maintenance tasks