Share your feedback
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
👥People Tab - Show account association and access status in the People tab
📍 Today: In the People tab, a person record does not clearly indicate whether that person is tied to an actual PuzzleApp account or what level of access they have. For admins, that creates unnecessary guesswork during routine user management. We can see the person, but we cannot immediately tell: Whether they have an active account Whether they have ever been provisioned into the platform What access level or role they currently hold That slows down common workflows like access reviews, troubleshooting, onboarding validation, and cleanup of stale records. It also increases the risk of making the wrong assumption about whether someone is truly in the system versus simply listed in People data. ✨ Desired: Each person in the People tab should display a clear visual indicator when they are associated with an actual PuzzleApp account, along with a concise view of their current access. At a minimum, admins should be able to quickly identify: Account associated: yes or no Account status: active, inactive, pending, or similar Access level / role This should be visible inline from the People tab without requiring extra clicks just to confirm whether someone has an account and what they can access. 📊 Business Justification: At enterprise scale, admins and HR platform owners need immediate visibility into identity and access state. When that information is buried or unclear, it creates avoidable admin overhead and weakens confidence in access governance. This matters because it directly affects: Compliance and access reviews: Teams need to validate who has system access without piecing it together manually Admin efficiency: Reduces time spent opening profiles or cross-checking multiple places just to answer simple access questions Support deflection: Cuts down on tickets and internal questions like “Does this person actually have an account?” Onboarding and offboarding accuracy: Makes it easier to confirm provisioning status and spot mismatches early Scalability: What is manageable with a small user base becomes noisy and error-prone across larger employee populations This is a common pattern in mature enterprise platforms like Workday, ServiceNow, and Salesforce, where admins can quickly distinguish between a directory/person record and a provisioned user account with assigned access. ✅ Acceptance Criteria Each person record in the People tab clearly shows whether it is linked to an actual PuzzleApp account Admins can see the user’s current access level or role directly from the People tab The indicator is visible in list/table views without needing to open each record Account state is easy to distinguish at a glance using clear text, iconography, or both The display supports common admin workflows such as access review, onboarding validation, and troubleshooting The indicator behaves consistently across all people records where account linkage exists
👥People Tab - Centralize the People Tab at the All Workspace Level
📍 Today: The People tab appears to be managed at the individual workspace level. In a large enterprise environment with multiple workspaces, admins have to recreate and maintain the same people structure and org chart repeatedly in each workspace. That creates duplicate admin work, inconsistent people data between workspaces, and avoidable drift over time. It also makes every new workspace rollout more expensive to configure and govern. ✨ Desired: Allow People records and org structure to be managed once at the All Workspace level and inherited into each workspace automatically. By default, each workspace's People tab should reflect the centralized source of truth, with clear rules for whether any workspace-level overrides are allowed. 📊 Business Justification: Enterprise scalability: Large organizations often split workspaces by business unit, geography, security boundary, or program. That does not mean they should have to rebuild the same people model in each one. Lower admin overhead: Centralized management would eliminate repetitive setup and reduce the ongoing maintenance burden for platform admins. Better data consistency: A single source of truth for people data would reduce errors, mismatched org charts, and inconsistent manager visibility across workspaces. Cleaner change management: Org changes, manager changes, and team restructures could be maintained once instead of updated in every workspace manually. Aligned with enterprise expectations: Platforms like Workday, ServiceNow, and Salesforce generally centralize core people or directory data and reuse it across business structures rather than requiring duplicate configuration. ✅ Acceptance Criteria Admins can create and maintain People records at the All Workspace level. Workspace-level People tabs can inherit the centralized people structure automatically. Updates made at the All Workspace level sync to all connected workspaces. Admins can clearly distinguish inherited data from workspace-specific data. New workspaces can adopt the centralized People structure during setup without manual re-entry.
🔁 Workflow Tab - Add sticky notes
📍 Today: PuzzleApp workflows are useful for mapping and walking through processes, but there is no lightweight way to capture observations in context while reviewing the workflow. When admins, HR stakeholders, managers, or end users spot an improvement opportunity, they have to leave the workflow, document it somewhere else, and manually translate it into follow-up work later. That breaks the review flow and increases the chance that improvement ideas are lost or disconnected from the exact step where they were identified. ✨ Desired: Allow users to place sticky notes directly on the Workflow tab while building or walking through a workflow. Sticky notes should act as lightweight, in-context annotations for questions, risks, friction points, and improvement ideas. From there, users should be able to convert a sticky note into a task in common task management platforms such as ClickUp, Asana, Jira, and Monday.com, while preserving the note content and workflow context. 📊 Business Justification: At enterprise scale, workflow reviews often involve cross-functional participants including platform admins, process owners, managers, HR stakeholders, and operational teams. Without an in-context capture mechanism, teams rely on screenshots, side notes, and follow-up meetings to reconstruct what was discussed. That creates unnecessary admin overhead, slows continuous improvement, and weakens change management. Comparable platforms such as Miro, FigJam, and other workflow collaboration tools make annotation easy because feedback stays attached to the work itself. Adding sticky notes plus task conversion would help PuzzleApp: Reduce friction during live workflow reviews and process improvement sessions. Preserve context so ideas are tied to the exact workflow step where the issue was found. Shorten the time between identifying an improvement opportunity and assigning follow-up work. Reduce manual re-entry into external systems, which lowers the risk of missed action items. Improve adoption by making PuzzleApp a better working surface for both discovery and execution. ✅ Acceptance Criteria Users can add, move, edit, and delete sticky notes on the Workflow tab while building or reviewing a workflow. Sticky notes remain visually anchored to the relevant workflow area or step. Sticky notes support enough content for concise improvement notes, risks, and follow-up ideas. Users can convert a sticky note into a task directly from the UI. Task creation supports at least ClickUp, Asana, Jira, and Monday.com. The created task includes the sticky note text, workflow name, and a link or reference back to the relevant workflow step. Users can see whether a sticky note is still open or has already been converted into a task. Permissions for creating, editing, and converting sticky notes align with existing workflow access rules.