Skip to main content

Backlog

5

Under consideration

Feature Request

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.

MacAlmon
Feature Request

Missing icons in minimized left navigation

The left navigation menu does not show the icons it should when minimized (the customer believes there should be about six), which can lead to unpredictable navigation when moving between the change log and the regular workflows. https://www.loom.com/share/c5fcb81734fb408f91cc0b8f975f8703

Mike Roberts
Feature Request

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

MacAlmon
Feature Request

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.

MacAlmon
Feature Request

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.

MacAlmon

Next up

5

Committed and queued

In Progress

5

Actively being built

Feature Request

Cost View Toggle on the Canvas

We’re adding a cost toggle to the toolbar (press M) that shows step costs directly on the canvas. On Optimizer, it also shows section costs, so one click puts the cost information in front of you when you’re comparing options and making decisions. This replaces the frequency bubble that currently appears on steps.

Operations
Feature Request

Changelog Scope and Cost Analysis Tabs

We’re giving the Changelog more room for planning. Each entry now has a Scope tab and a Cost Analysis tab. Cost Analysis shows current state and future state side by side. You add tabs or sections to each, and you can leave out items by status, such as archived steps. A labor cost breakdown by section, step type, role and person shows which processes, tasks and roles are becoming more efficient. A tech stack comparison shows the change in tool costs. Nova’s scope writer is now collapsed by default, which gives the page more space.

Operations
Feature Request

Comment Mode with Type Filters

We’re adding a comment mode to the canvas toolbar (press C to turn it on or off). When it’s on, steps without comments fade back and steps with comments show a bubble with their comment count, so it’s clear where conversations are happening. A key lets you filter by comment type, such as notes, decisions, ideas and questions, to jump straight to the comments you care about. Resolve a comment and its bubble clears, so you can work through a map and close out each conversation as you go.

Operations
Feature Request

Move Steps, Tools, Roles and People to Another Tab in Bulk

We’re expanding bulk actions so you can select multiple steps, tools, roles or people and move them to another tab in one step. This makes it quicker to reorganize your workspace as it grows.

Operations
Feature Request

Share Workspaces Across Organizations (Enterprise)

We’re making it easier to collaborate with agencies, partners and clients by letting an organization share a specific workspace with another organization. The sharing organization chooses which people from the receiving organization get access. To connect, the receiving organization shares its organization ID, and the sharing organization sends a request that the receiver accepts. The workspace then appears in their organization. This is available to Enterprise organizations, and the receiving organization needs a paid plan.

Operations

Done

Recently shipped

No Done issues