---
title: "Shared Workflows | Langdock Changelog"
description: "You can now share a workflow with individual users or entire groups so they can run it with their own connections, while you, as the workflow owner, stay in…"
url: "https://langdock.com/changelog/shared-workflows"
language: "en"
---

[Changelog](https://langdock.com/changelog)

Nov 16, 2026

# Shared Workflows

**You can now share a workflow** **with individual users or entire groups** **so they can run it with their own connections,** **while you, as the workflow owner, stay in control of** **every step.** You build the workflow once, and all users you share it with benefit without building their own.

To share a workflow, click **Share** on its **Workflow overview** and add individual users or groups with the **User** permission, just like you share an agent. Workspace members with the User permission for that workflow can set up and run the workflow, but can't edit it.

#### Choose which connection each step uses

For each step in the workflow using an integration, users run it with their own connection. For example, a sales team's workflow can draft replies to customer emails in **each user's own Outlook inbox**, based on product documentation and sales materials from a SharePoint folder. Just like with agents, you can also pre-select a connection for a step, so all users run that step **through the same connection**.

Workflow runs by users you share the workflow with are private: owners and editors can't see the results of these workflow runs.

#### Updates in one place

When you publish a new version of the workflow, all users you share it with get it automatically, as long as they don't need to set up a new connection for it. If a change needs a new connection, users see an update banner and can update the workflow to the new version themselves. Connections they already set up are kept.

#### A new overview page for every workflow

Each workflow now has its own **Workflow overview**, separate from the workflow editor. For a workflow shared with you, this is where you can setup connections, turn workflows on or off for yourself, start manual workflows with **Run now**, and see your private runs. You'll find the published workflows shared with you on the new **Discover** page in Workflows.

For more details, watch the detailed [product walkthrough](https://youtu.be/PVNfvBkYMOY?si=tsQsVAb4ejoJ-udn).

Improvements

- Workflows

  **Workflow analytics**: Owners and editors of a workflow can open the Analytics tab on its Workflow overview to see runs, active users, success rate, average run time and cost for a date range, plus usage and failure statistics per node.
- Workflows

  **Workflows overview**: Switch between All, Created by you and Shared with you, sort workflows by name, and see each workflow's run trend for the last 30 days and its budget usage this month.
- Workflows

  **Auto in Workflow Chat**: Workflow Chat supports Auto, which picks and remembers the right model for your conversation, just like in chat and the agent builder.
- Workflows

  **Automatic node retries**: In a node's Error handling, choose Retry node and set how often it retries and how long it waits in between, so a workflow can recover on its own when a step fails.
- Workflows

  **Knowledge files in agent nodes**: Files you upload to an agent node's Knowledge field belong to the workflow, so every run can use them, no matter who starts it.
- Workflows

  **Synced knowledge in agent nodes**: Agent nodes that use an existing agent can search that agent's synced folders, including SharePoint and Confluence files.
- Workflows

  **New triggers**: Start workflows when a SharePoint list or list item changes, when a file is added to a folder, or when someone is invited to, joins or requests access to your workspace.
- Workflows

  **GitHub triggers**: Start workflows in real time on pull request activity, such as comments, reviews and CI results, or on deployments filtered by environment, branch or status.
- Workflows

  **User input node**: A workflow can pause to collect answers or to let a user approve or reject a request, then continue on the matching path.
- Workflows · **20 form fields**: Form triggers support up to 20 input fields, up from 10.

[OlderGemini 4 Carbon](https://langdock.com/changelog/gemini-4-carbon) [NewerLangdock Apps](https://langdock.com/changelog/langdock-apps)
