Workflow buttons that open a form can now link the actions created by a submission as dependencies. The action containing the button stays blocked until all of those prerequisite actions are completed.

A new dropdown lets you choose whether submitted actions become subactions, dependencies, or remain unlinked. Existing configurations keep their current behavior, and new ones default to subactions.

In the workflow builder, configure a button’s Open form operation and choose how to link submitted actions.

Teams using forms to collect prerequisite work can keep the next action blocked until that work is complete.

Agents using Hive MCP can now change Custom App sharing and upload local files to the File Library without switching to the Hive web interface. Uploaded files can then be used when building Custom Apps.

App owners can set sharing to themselves, selected people, or everyone through MCP.

These capabilities are available through Hive MCP’s Custom App sharing and File Library upload tools.

People using agents to build and manage Custom Apps can handle file uploads and app sharing in the same MCP workflow, rather than completing those steps in the web interface.

Keep large volumes of proofing feedback organized with workspace-defined comment categories, such as Design or Development. Give each category a name and color, then apply it when creating or editing a comment. Category chips appear on comment threads, and reviewers can filter the comments panel by category to focus on relevant feedback.

Categories work across PDF, video, and live-site proofs. Existing comments remain unchanged, and uncategorized comments stay visible when no category filter is applied.

In the native proofing editor, set, change, or clear a category when creating or editing a comment or annotation. Use the category filter in the comments panel to narrow the feedback shown.

Reviewers and teams handling feedback across departments can separate comments by category rather than relying only on individual mentions. External reviewers who can already create or edit comments can also categorize their feedback.

Bring your Wrike work into Hive with a guided project import. Import projects, tasks, subtasks, descriptions, dates, statuses and assignments, with a preview before importing and supported-field limitations shown along the way.

Connect Wrike through a shared, read-only OAuth connection that can be reused for imports.

Connect Wrike in Settings → Connections or start from the guided project import.

Teams moving work from Wrike to Hive can bring over project structure and task details without recreating them manually.

The resource estimates planner now gives more space to your planning grid, with compact project controls and an inline readiness summary. Fill, Copy, Paste, and Repeat appear when you select rows, with range controls opening only when needed.

A single grid scroll area keeps dates visible and resource names and totals pinned on desktop. On narrow screens, columns unpin so you can reach every period. Direct cell edits still save automatically, while bulk changes retain Save and Discard controls.

People planning resource estimates who need more room to review resource rows, navigate periods, and make individual or bulk updates.

Attachments in Hive Mail are now easier to spot and recognize, with cards showing image and PDF thumbnails, filenames, file sizes, and download buttons.

Click a card to preview images, PDFs, and videos; other file types download directly. Collapsed messages keep a compact attachment row.

Open an email in Hive Mail to see attachment cards below the expanded message body.

Anyone reviewing files in email who wants to identify attachments more easily and quickly preview or download them.

Unfinished workflow drafts now reopen with your original question and Buzz conversation, so you can continue building without starting over. Saved configurations also retain the original conversation, and edits to existing workflows update them in place.

Completed AI workflows save automatically and stay disabled. When a workflow needs an external connection, setup is guided in the workflow’s workspace with read-only verification that prevents live writes during authoring.

People building or refining workflows with Buzz, especially when setup takes more than one session or involves an external connection.

Choose which feedback to include when downloading native proofs with annotations. When open AI suggestions are present, you can export human comments only (the default), AI comments only, or both, so the downloaded proof includes the feedback you want to share.

AI suggestions saved as comments or annotations count as human comments; open suggestions count as AI comments. Downloading does not remove comments or suggestions from Hive.

In the native proofing download options when downloading with annotations and open AI suggestions are present.

Proof reviewers and anyone sharing annotated proofs who wants to separate saved feedback from open AI suggestions—or include both in one export.

You can now group your Roadmap timeline by project, alongside the existing Label and Section options. Selected projects appear as bands with their corresponding actions, making it easier to see work organized by project.

In the Roadmap timeline layout, choose Project from the Group by dropdown.

Teams planning work across multiple projects can use project bands to review each project's actions in the timeline.

Action and project custom fields can now appear only when conditions on other custom fields match. For example, show a “Rollback plan” field only when Environment is set to Production.

Fields hide when their conditions don’t match and reappear when they do, keeping action cards and project overviews focused on relevant information. Combine conditions with AND/OR logic and nested groups for more specific rules.

Open the create or edit custom field dialog, then go to Advanced settings → Conditional visibility. Rules apply to fields shown on action cards and in the project overview.

Teams using custom fields for different types of work can collect the right details without showing every field on every action or project.