> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get-hive.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Share and reuse workflows

> Share a Hive workflow with named teammates as Can view, Can run or Can edit, run a shared workflow with your own accounts, and copy, export or template it.

A workflow is private to the member who created it until they share it. Sharing and templates are
two ways to let teammates use your work: sharing gives them access to this workflow, and a
[template](/workflows/templates) gives them a starting point for their own copy.

## Share a workflow

<Steps>
  <Step title="Open Share">
    Open the workflow in the builder and select **Share**.
  </Step>

  <Step title="Add people">
    Choose an active member of your workspace and a permission. Hive saves the change and confirms
    with **Access updated.**
  </Step>
</Steps>

| Permission | What the member can do |
| - | - |
| **Can view** | Open the workflow and read its steps, releases and runs. |
| **Can run** | Also run the live release with their own connected accounts. |
| **Can edit** | Also edit the draft, test it and deploy it. |

You can share with up to 100 members. Sharing is always person by person: there is no
workspace-wide or public sharing of a workflow.

<Note>
  Workspace Admins and Owners can read every workflow in the workspace, but that does not let them
  edit, run or reshare someone else's. Copying a link does not grant access, and removing access
  cannot recall a copy someone already exported.
</Note>

Running any workflow — even with **Can run** — also needs the workspace **Operator** role or higher.
See [Roles and permissions](/admin/roles-and-permissions).

## Run a workflow shared with you

When a workflow is shared with you, the builder shows **Your accounts for this run** above the
canvas. Choose your own connected account for each step that needs one, then select **Run with my
accounts**. This starts a production run of the live release; your choices apply only to your run
and never use the creator's accounts. The workflow must be deployed first.

## Copy, export and import

* **Duplicate workflow** creates a private draft copy you own.
* **Export workflow** downloads the workflow as JSON. Connected accounts that belong to other
  members are removed, so those steps name only the app they need. Any account of your own that
  you chose for a step, and that is still connected, stays in the file.
* **Import workflow** (in the workflow menu or on **All workflows**) creates a new private draft
  from an exported file and lists what still needs attention.

See the [workflow export format](/developers/workflow-export-format) for what the file contains.

## Templates

**Save as template** publishes a copy for everyone in the workspace to start from, without giving
anyone access to your workflow or its runs. See [Templates](/workflows/templates).

## Related

<CardGroup cols={2}>
  <Card title="Templates" icon="copy" href="/workflows/templates">
    Built-in and workspace templates.
  </Card>

  <Card title="Accounts and autonomy" icon="user-shield" href="/integrations/accounts-and-autonomy">
    Personal connected accounts and what Hive may do with them.
  </Card>

  <Card title="Roles and permissions" icon="id-badge" href="/admin/roles-and-permissions">
    Workspace roles and what they allow.
  </Card>

  <Card title="Export format" icon="file-code" href="/developers/workflow-export-format">
    The JSON a workflow exports to.
  </Card>
</CardGroup>