See the complete route index at https://docs.crusible.dev/llms.txt before following links.

# Share a preview

Expose a port in your Sandbox through a tunnel, share its link, and revoke the tunnel when you finish.

<!-- https://docs.crusible.dev/guides/share-a-preview/ · doctype: how-to · role: member · reviewed: pending human review -->


A preview reaches a port in your Sandbox through a tunnel. Crusible offers the tunnel when a
program in the Sandbox starts serving web pages on a port. You decide whether to expose it.

![A live tunnel card for port 5173 with its address, a Copy link control, Open and Revoke.](/docs-illustrations/share-a-preview-paper.svg)



1. <p>Start your app&rsquo;s development server in your Sandbox. Only the person who created the Sandbox sees the card.</p>
 (Result: The channel shows a card such as **Expose port 5173 (vite)?** with **Yes**, **Not now** and **Never for this port**.)

1. <p>Read the warning “Anyone who has the link. No sign-in.” Then choose <strong>Yes</strong>.</p>
 (Result: The card becomes **Tunnel to port 5173** and shows **Live** with the tunnel's address.)

1. <p>Select <strong>Copy link</strong> beside the address and send the link to the people who need the preview.
Anyone who has the link opens the preview without signing in. Select <strong>Open</strong> to check it yourself.</p>
 (Result: The card shows **Address copied**.)

1. <p>Crusible pins the card to the channel when the tunnel goes live. If the card shows <strong>Pin it</strong>,
the automatic pin failed. Select <strong>Pin it</strong> to try again.</p>
 (Result: The channel's pinned list shows the tunnel card.)

1. <p>When you finish, select <strong>Revoke</strong> on the card. Confirm with <strong>Revoke tunnel</strong>.</p>
 (Result: The card marks the tunnel revoked, and the address stops answering within 30 seconds.)

- **If this doesn't work:** <p>Choose <strong>Not now</strong> to skip the tunnel. Crusible asks again in a later Sandbox session.
Choose <strong>Never for this port</strong> to stop the question for that port.
If the card says Crusible can&rsquo;t expose the port, make the server listen on localhost or on all interfaces.
If you see “Tunnels are turned off by an administrator.”, ask an owner or administrator.
If <strong>Revoke</strong> fails, the address still answers. Select <strong>Revoke</strong> again.</p>





The tunnel ends at the time the card shows, or when the Sandbox stops. **Extend** adds 1 day.
A revoked or ended tunnel doesn't come back. Its card unpins from the channel.

## Who can do what

- **Access.** Every tunnel opens for anyone who has the link, with no sign-in. The card offers
  no members-only option and no other access level. Treat everything the port serves as published.
- **Creating.** Only the person who created the Sandbox answers the card and creates its tunnels.
  An agent can't create a tunnel.
- **Revoking.** The tunnel's creator or the Sandbox's owner revokes it.
- **Everyone else** in the channel sees the tunnel's address, state and end time, with no controls.
  The link itself goes only to the tunnel's creator.

Select **Details** on the card to open the **Tunnel** pane. It lists the address, state, target port,
end time and the other live tunnels in the Sandbox.

- [Terminal](https://docs.crusible.dev/reference/surfaces/terminal/) — Shells, machine selection, terminal tabs, file uploads and connection controls.- [Set a sandbox environment](https://docs.crusible.dev/admin/set-a-sandbox-environment/) — Set the environment variables and secrets every Sandbox starts with, for your organisation or for yourself.- [Review a pull request](https://docs.crusible.dev/guides/review-a-pr/) — Read a pull request, inspect its files and checks, and continue review actions on GitHub.