Share your feedback
👥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.
🧰Tools - Ability to add custom fields
📍 Today: Tools appear to have a fixed set of attributes with no way for admins to add their own custom fields. For large enterprises, that breaks down quickly. We often need to track internal metadata on every application or tool, such as: EPR ID Internal application ID Owner organization Compliance classification Support tier Without custom fields on Tools, that information has to live somewhere else or be managed manually outside the platform. That creates duplicate admin work, inconsistent records, and weakens the Tool object as a reliable source of truth. ✨ Desired: Allow workspace admins to create and manage custom fields on Tools the same way mature enterprise platforms support extensible object metadata. At a minimum, admins should be able to: Add custom fields to Tools Choose field types such as text, dropdown, number, date, checkbox, and relationship fields where applicable Mark fields as required or optional Control who can edit those fields Filter, search, and report on Tools using custom field values Expose those fields in imports, exports, and API responses This would let enterprises adapt the Tool object to their own governance model instead of forcing every customer into the same fixed schema. 📊 Business Justification: For enterprise customers, extensibility is table stakes. Platforms like Salesforce and ServiceNow are widely adopted because admins can extend core objects to match internal operating models without waiting for a vendor to hardcode every field. Adding custom fields to Tools would help with: Governance: Store internal identifiers like EPR ID directly on the Tool record Compliance: Track classifications, review dates, or ownership attributes needed for audits Data quality: Reduce spreadsheet sprawl and duplicate system maintenance Scalability: Support large application portfolios with different business and technical metadata requirements Change management: Let admins roll out structured metadata as enterprise needs evolve For large organizations, the lack of custom fields creates avoidable manual work and makes it harder to use Tools as an enterprise-grade inventory object. ✅ Acceptance Criteria Admins can create custom fields on Tools without product team intervention Tool-level custom fields support common field types, including text, dropdown, number, date, and checkbox Admins can edit field configuration, including field name, required status, and available options where relevant Custom field values are visible on each Tool record Users can filter and search Tools by custom field values Custom field data is available in reporting, export, and API access Existing Tool records can be bulk updated or imported with custom field values
🧰Tools - Ability to sync with ServiceNow CMBD
📍 Today: PuzzleApp does not appear to have a direct sync with ServiceNow CMDB. That means admins and platform owners have to manage tool and system records separately, or rely on manual updates to keep the data aligned. In practice, this creates drift between the system of record and what users see in PuzzleApp, especially when ownership, dependencies, support groups, or lifecycle details change. ✨ Desired: Add the ability for PuzzleApp tools to sync with ServiceNow CMDB so core configuration and metadata stay aligned automatically. At minimum, admins should be able to connect ServiceNow CMDB as a source of truth and sync relevant records and attributes into PuzzleApp on a scheduled or near-real-time basis. Ideally, the integration would support field mapping, sync controls, and clear visibility into sync status and errors. 📊 Business Justification: For enterprise teams, ServiceNow CMDB is often the authoritative source for application and infrastructure metadata. Without a sync, admins are forced into duplicate maintenance, which increases admin overhead and raises the risk of stale or conflicting records. This impacts: Platform admins, who spend time reconciling data across systems App owners and support teams, who need accurate ownership and dependency information Audit and compliance stakeholders, who depend on reliable system-of-record alignment End users, who lose trust when tool metadata is incomplete or outdated At scale, even a small amount of manual upkeep per application becomes a significant operational cost. This is a common enterprise expectation in platforms such as ServiceNow, Workday, and Salesforce ecosystems, where integrations with source-of-truth systems reduce support effort and improve change management. ✅ Acceptance Criteria Admins can connect PuzzleApp to ServiceNow CMDB without custom engineering Admins can select which CMDB records or classes should sync into PuzzleApp Admins can map key CMDB fields to PuzzleApp tool metadata Sync can run on a schedule and/or on demand Failed syncs surface clear error messaging and retry guidance Synced records show last sync timestamp and source-of-truth status in PuzzleApp
👥People Tab - Expanding and collapsing the node
📍 Today: In the People tab, users can view the org structure but cannot expand or collapse individual nodes on demand. That makes larger org charts harder to navigate, especially when an admin, manager, or HR stakeholder only needs to focus on one branch of the organization at a time. In practice, the experience becomes noisy as the org grows. Users end up scrolling through unrelated teams, losing context, and spending extra time trying to visually isolate the reporting line they actually care about. The UI pattern used by Justsift is a strong example of the kind of interaction that would make this view much more usable. ✨ Desired: Add the ability to expand and collapse nodes directly within the People tab org chart. Users should be able to: Collapse branches they do not need to see Expand only the team, manager, or reporting chain they are reviewing Move through large org structures without losing visual clarity Ideally, this would follow the same familiar disclosure pattern users see in mature enterprise tools and org-chart experiences, where a node with direct reports can be expanded or collapsed inline without reloading the page. 📊 Business Justification: This matters much more at enterprise scale than it does in a small org. Improves usability for large orgs: HR, IT, and business stakeholders often work across hundreds or thousands of employees. A fully open chart becomes difficult to scan quickly. Reduces admin overhead: Admins spend less time explaining how to navigate the org chart or working around limitations during audits, planning sessions, and stakeholder reviews. Supports manager and HR workflows: Managers and HR teams often need to review one branch at a time for workforce planning, reorganizations, succession planning, and access discussions. Creates a more modern enterprise experience: Expand/collapse behavior is standard in platforms that deal with hierarchical data. Without it, the chart feels harder to use than comparable solutions. Improves adoption and trust: Small UX improvements like this have an outsized effect on whether users see the People tab as a practical system of record or just a static visualization. ✅ Acceptance Criteria Nodes with direct reports display a clear expand/collapse control Collapsing a node hides all descendant nodes in that branch Expanding a node restores the hidden branch without a full page refresh Users can expand one branch without automatically expanding unrelated branches The interaction performs well in large org charts The state change is visually clear and intuitive for end users
👥People Tab - Connecting People to Tab to Enterprise Directory
📍 Today: The People Tab appears to operate as a standalone experience rather than a connected enterprise directory. For large organizations, employee profile data already lives in systems like Workday, and admins should not have to recreate or manually maintain that same data in another platform just to make the People experience usable. The current limitation creates a few predictable problems: Admins have to manage duplicate records or incomplete people data. End users may see outdated reporting lines, job titles, departments, or profile details. HR and IT stakeholders have no reliable way to ensure directory data in PuzzleApp stays aligned with the system of record. Adoption becomes harder because the People Tab feels disconnected from how enterprise employee data is actually managed. ✨ Desired: Allow the People Tab to connect to an enterprise directory or HRIS so employee data can be sourced from a system of record such as Workday. At a minimum, admins should be able to: Connect PuzzleApp to an enterprise directory / HRIS source. Map standard employee attributes such as name, title, department, manager, location, and employment status. Control which fields sync into the People Tab. Define sync behavior such as scheduled refreshes and handling for new hires, transfers, and terminations. Preserve a clean end-user experience where people data feels native inside PuzzleApp even though it is system-connected behind the scenes. 📊 Business Justification: This matters because employee profile data is foundational infrastructure in enterprise environments. Without this capability, enterprise customers face: Higher admin overhead from duplicate data entry and manual cleanup. Data quality risk when employee information changes frequently across large populations. Poor end-user trust if people data in the People Tab is stale or inconsistent. Slower rollout and change management because HR, IT, and platform owners are less likely to support a disconnected profile model. Scalability limits for global organizations with frequent organizational changes, internal mobility, and compliance requirements around worker data accuracy. For large customers, this is not just a convenience feature. It directly affects whether the People Tab can be deployed as a credible enterprise experience. ✅ Acceptance Criteria Admins can connect the People Tab to at least one enterprise system of record. Admins can map standard employee fields to PuzzleApp profile fields. New hires, manager changes, title changes, department changes, and terminations can be reflected through sync rather than manual rework. Admins can choose which attributes are synced and which remain editable in PuzzleApp. Sync failures or field mapping issues are visible to admins through clear error handling. End users see accurate, current people data in the People Tab without requiring separate profile maintenance.
🧰Tools - Workspace-level tool library with workspace-specific adoption
📍 Today: Tools appear to be managed at the individual workspace level. In large enterprise environments, that means admins have to recreate or reconfigure the same tools repeatedly across multiple workspaces. This creates avoidable setup work, increases the chance of drift between workspaces, and makes governance harder when teams need a consistent approved toolset. It also creates a confusing admin experience when there is no clear distinction between centrally managed tools and workspace-only tools. ✨ Desired: Add tools at the All Workspace level first, so enterprise admins can maintain a central approved tool library once and make those tools available for adoption inside individual workspaces. Within each workspace, the tools area could be presented as My Tools or a similar workspace-level view that lets admins: Add approved tools from the central workspace library See which tools are centrally managed versus locally created Optionally create a workspace-specific custom tool when a local exception is needed This would mirror how mature enterprise platforms handle centralized configuration with local flexibility. 📊 Business Justification: For enterprise customers, duplicated setup across workspaces does not scale. A centralized tool library would reduce admin overhead, improve consistency, and support better governance. Key impacts: Lower admin effort: Configure once instead of repeating the same work in every workspace Better consistency: Reduce configuration drift across business units, regions, or environments Stronger governance: Make it easier to control which tools are approved for enterprise use Faster rollout: New tools and updates can be introduced centrally instead of workspace by workspace Cleaner change management: Admins can support standardization without blocking legitimate local exceptions ✅ Acceptance Criteria Enterprise admins can create and manage tools from an All Workspace level Individual workspaces can add or enable tools from that central library without recreating them from scratch Workspace admins can clearly distinguish between centrally managed tools and workspace-specific custom tools Workspace admins can still create local custom tools when needed Updates to centrally managed tools can be rolled out consistently across workspaces using them Permissions support appropriate separation between enterprise-level admins and workspace-level admins
Manage Tool Costs via MCP and Nova
We're adding the ability to add and read tool cost items through MCP and Nova. You'll be able to ask Nova to add cost items to any tool — including flat fee, per seat, one-time, and usage-based costs — without having to do it manually in the app.
Edit Tool Template Name and Description
We're adding the ability to edit the name and description of your saved tool templates. Simply click the edit button on any template you've created to update its details — keeping your template library organized as your tool stack evolves.
Color Sections, Labels, and Steps via MCP and Nova
We're adding the ability to set colors on sections, labels, and steps through MCP and Nova — so you can fully build out and style your workflows through AI without having to manually apply colors in the app.
Clickable Links on Tool Cards
We're adding clickable links to tools on the Tools Canvas. Each tool will inherit the URL from the tool directory by default, but you'll be able to edit it to a custom link for your workspace. Click the link to open the tool's URL directly — no need to search for it separately.
Add AI Agent as a People Type
We're adding "AI Agent" as a new type option under the People canvas — so you can document and track AI agents alongside your human team members in your operational workflows.
Summary Analytics in the Workspace Sidebar
We're bringing workspace-level analytics into the sidebar. You'll be able to see a summary of your workflow health at a glance — including step statuses and automation coverage — without having to navigate away from your current workspace.
View All Changelog Entries at the Section Level
We're adding a Changes tab to sections, giving you a rollup of all changelog entries tied to the steps within that section. Instead of checking each step individually, you'll get a consolidated view of what's changed across the entire process at a glance.
Flexible Tool Cost Tracking
We're expanding how you track tool costs in Puzzle. Instead of a single subscription cost, you'll be able to add multiple cost items per tool — each with its own cost type: Flat fee — a recurring fixed cost Per seat — cost based on the number of users One-time — a single payment Usage-based — estimated spend based on rate and usage This gives you a more accurate and flexible way to track what each tool actually costs your organization.
Dashboard for Settlement Data
I would like to have a dashboard built off the settlement data captured by the Claude routine. This would provide a more accessible and visual representation of the data, aiding in better analysis and decision-making.
Tool Templates for the Tools Canvas
We're introducing tool templates to the Tools Canvas — making it easier to reuse and share common tool stacks across workspaces. Here's how it works: Browse templates by clicking the new template icon on the Tools Canvas. You'll find Puzzle-curated templates under Explore, and your own saved templates under My Templates. Save your own template using the "Save as Template" option in a tool group's sidebar — similar to how workflow section templates work today. Use, edit, or delete your saved templates directly from the template library. Templates carry over tool names, layout, and notes — without any cost or billing information.
Tab-Level Permissions (Enterprise)
We're introducing tab-level permissions for the Workflows canvas, giving Enterprise workspaces more control over who can see specific tabs. By default, all tabs are public within a workspace — but owners and admins can switch any tab to private and control exactly which workspace members have access. Private tabs will display a lock icon so it's clear they're restricted. Members without access simply won't see the tab. This feature is available on the Enterprise plan. Users on other plans will see the option but will be prompted to upgrade to access it.