---
title: "Share full workspace via URL service"
description: "Current state and target design for full workspace sharing"
---

This tutorial maps the desired "share full workspace as URL" flow.

## Current state

- You can export workspace config (`.opencode/` + `opencode.json`) as a bundle.
- You can share worker URL + token (or invite link) for runtime access.
- Full config sharing is file-based, not URL-based.

## Target state

Share full workspace as a URL that:

1. Stores an encrypted workspace bundle in share service.
2. Produces a short-lived import URL.
3. Opens OpenWork and imports into a selected local folder.
4. Applies worker URL/token defaults if provided.

## Proposed flow

1. User clicks **Share workspace URL**.
2. OpenWork exports workspace config payload.
3. Payload uploads to share service with TTL + access scope.
4. OpenWork returns URL like `/share/workspace/<id>?sig=...`.
5. Recipient opens link and confirms import target.

## Operational requirements

- Token redaction in UI logs.
- Expiring URLs and revocation.
- Audit event for share create/open/import.
- Size limits and checksum validation.

## Recommendation

Ship this as a dedicated share-service feature after invite-link adoption is stable.
