Publish a share link.

Take any notebook or dashboard from your desktop and put it on the web at a clean URL — no Orchid install required to view.

What you'll build

A read-only published version of a notebook at https://<slug>.orchidide.com, configured with a refresh schedule so the numbers stay current. We'll also walk through the visibility modes and what the view looks like to a colleague without an Orchid account.

Prerequisites

A signed-in account (the first time you publish, Orchid will prompt you to sign in or create one) and any notebook or dashboard you want to share. The tutorial assumes you finished Build a revenue dashboard but any notebook works.

1. Open the publish dialog

Open the notebook you want to share, then click Publish in the top-right of the notebook header. The dialog shows three visibility modes:

  • Team — only signed-in members of your team can view. Best for internal dashboards.
  • Link-only — anyone with the URL can view, no sign-in. The link is long and unguessable; treat it like a secret.
  • Public — discoverable and indexable. For genuinely public content like a blog-post notebook or a portfolio piece.
The publish dialog showing the three visibility modes with Team selected by default, slug field, and refresh schedule dropdown./docs-images/tutorials/publish-share-link/01-publish-dialog.png
The publish dialog. Slug is editable; refresh schedule is optional.

2. Pick a slug

Orchid suggests a slug derived from the project title. You can edit it. The full URL preview updates live underneath.

https://revenue.orchidide.com

Slugs are globally unique — first publisher owns the cloud row for that project. If revenue is taken, Orchid suggests revenue-2 or you can pick something descriptive like revenue-q3.

First publisher owns the slug

Slugs are project-level and global. Once you publish, the slug is yours until you unpublish. See Publishing for the full ownership model.

3. Set a refresh schedule

By default, the published copy is a frozen snapshot — it shows the data that was in your notebook when you hit Publish. For dashboards, you usually want fresh numbers. Pick a schedule from the dropdown:

  • Manual — re-runs only when you click Republish.
  • Hourly — top of every hour.
  • Daily — at a time you choose, in your account's timezone.
  • Weekly — pick a day and time.

Scheduled refreshes run on Orchid's cloud runners against your configured integrations. Your local app does not need to be open.

4. Publish

Click Publish. Orchid uploads the notebook, runs the cells in the cloud, renders the outputs, and returns the URL. A toast appears with a Copy link button.

A success toast showing the published URL and a Copy link button, with the publish dialog dismissed./docs-images/tutorials/publish-share-link/02-publish-success.png
Published. Copy the link or open it directly in the browser.

5. View as a non-Orchid colleague

Open the URL in a private browser window (so you're not signed in). For Link-only or Public notebooks, the page loads straight to the rendered view — no sign-in wall, no app download nag. The viewer is a lightweight React app that renders the same charts and tables your colleague would see in Orchid.

A browser tab at revenue.orchidide.com showing the rendered dashboard with the Orchid wordmark in the corner./docs-images/tutorials/publish-share-link/03-viewer.png
The web viewer is read-only. Filters work; cells don't execute on demand — they show the last refreshed result.

For Team visibility, the same URL prompts for sign-in. Team members go straight through; non-members see a friendly "Ask the owner for access" page.

6. Update the published copy

Edits to the local notebook do not auto-propagate. Hit Republish from the publish menu to push the latest version. The URL stays stable — only the contents change. If you want to retract a publication entirely, click Unpublish and the URL begins 404-ing immediately.

First publisher owns the cloud row

Slugs are project-level and global. The first person to publish a project owns the cloud row for it; a second publisher with the same slug gets a collision warning. See Publishing for the full ownership model.

Where to go next