> ## Documentation Index
> Fetch the complete documentation index at: https://mintlify.com/warpdotdev/warp/llms.txt
> Use this file to discover all available pages before exploring further.

# Share terminal sessions and workflows in Warp

> Share individual command blocks as permalinks, invite teammates into live terminal sessions, and distribute Drive objects with fine-grained access control.

Warp has multiple sharing surfaces: you can share a single command block as a permanent link, invite teammates into a live terminal session, or share an entire Drive object (workflow, notebook, etc.) using an ACL-based permission model. All three flows are accessible from the sharing dialog, which can be opened from any block's toolbar, from the Drive panel, or from the session context menu.

## Sharing individual blocks

Every command block in Warp can be turned into a shareable permalink. Select the block and choose **Share block** from its toolbar to generate a link. Recipients can view the block's output in a browser without installing Warp.

<Note>
  Block permalinks are public links — anyone with the URL can view the output.
  Do not share blocks that contain secrets or private data.
</Note>

When the `SharedBlockTitleGeneration` feature flag is enabled, Warp automatically generates a descriptive title for the block using AI before producing the link.

## Sharing terminal sessions

Live session sharing lets you invite teammates into an active terminal session so they can see your output in real time.

### Creating a shared session

Creating shared sessions is gated by the `CreatingSharedSessions` feature flag, which is enabled for paying team plans and for users in the session-sharing experiment. When the flag is active, a **Share session** button appears in the terminal header.

<Steps>
  <Step title="Open the sharing dialog">
    Click **Share** in the active terminal's header, or open the command palette
    and search for **Share session**.
  </Step>

  <Step title="Configure access">
    Choose who can join:

    * **Anyone with the link** — anyone who has the URL can view the session.
    * **Team members** — only members of your Warp team can join.
    * **Specific people** — add individual email addresses.

    You can also set the access level to **View** or, when
    `SharedSessionWriteToLongRunningCommands` is enabled, **Write** for
    long-running commands.
  </Step>

  <Step title="Copy and send the link">
    Click **Copy link** and send it to your teammates. The link is a
    `join_link` generated from the session ID and is immediately joinable.
  </Step>
</Steps>

### Viewing a shared session

Viewing shared sessions is controlled by the `ViewingSharedSessions` feature flag (separate from `CreatingSharedSessions`). This separation allows Warp to enable viewing for a wider audience independently of creation.

When a teammate opens a session link, Warp joins them as a participant identified by their display name and, if available, avatar. Anonymous participants are shown with a generated display name.

### Session ACLs

When the `SessionSharingAcls` feature flag is enabled, sessions use the same ACL model as Drive objects. The ACL model tracks subjects (individual users, teams, or anyone-with-link) and their access levels:

| Subject type     | Description                                                     |
| ---------------- | --------------------------------------------------------------- |
| `User`           | A specific Warp account, identified by UID.                     |
| `PendingUser`    | An invited user who has not yet accepted (identified by email). |
| `Team`           | All members of a Warp team.                                     |
| `AnyoneWithLink` | Public access — no authentication required to join.             |

You can revoke access for any subject by removing them from the ACL in the sharing dialog. The `SessionSharingAcls` flag can be toggled independently of the session-sharing server's `use_acls` flag, which acts as a kill-switch.

## Sharing Drive objects

Workflows, notebooks, AI facts, and other Drive objects use the same ACL model as sessions. Open the sharing dialog for any Drive object from the Drive panel's context menu.

<CardGroup cols={2}>
  <Card title="Share a workflow" icon="bolt">
    Right-click a workflow in the Drive panel and select **Share**. Set the
    access level and copy the generated link. Recipients who open the link can
    view and fork the workflow into their own Drive.
  </Card>

  <Card title="Share a notebook" icon="notebook">
    Open the sharing dialog from the notebook's title bar. Notebooks support
    view and edit permissions — grant **Edit** to let teammates contribute
    directly.
  </Card>
</CardGroup>

The shareable link for any Drive object is derived from the object's `ServerId` and resolved through the `CloudModel`. If an object has not been synced to the server yet, the link will not be available until the sync completes.

### SharedWithMe

When the `SharedWithMe` feature flag is enabled, a **Shared with me** section appears in the Drive panel showing Drive objects that other users or teams have shared with you. Objects in this section behave like regular Drive objects — you can open, run, or fork them into your personal or team space.

## Exporting and importing Drive objects

You can export any Drive object (or a folder of objects) to a local file and import it on another account or share it outside of Warp.

<Steps>
  <Step title="Export">
    Right-click an object or folder in the Drive panel and select **Export**.
    Warp writes a JSON file containing the object's content and metadata.
  </Step>

  <Step title="Import">
    Open the Drive panel menu and select **Import**. Choose the exported JSON
    file. You can import into your personal space or directly into a team folder.
  </Step>
</Steps>

<Tip>
  Exporting is a good way to contribute team workflows to a version-controlled
  repository and import them into a fresh Warp installation via CI or onboarding
  scripts.
</Tip>