# Share a Databricks Notebook — Results Without a Workspace Seat

Canonical: https://commareports.com/share-databricks-notebook
Published: 2026-08-23

> Export a Databricks notebook to HTML and publish it to Comma: stakeholders read the charts and tables at a URL, comment on the number they question, and never touch your workspace.

# Share a Databricks notebook

Databricks solves compute and access control, and both solutions get in the
way at the last mile. The analysis is done, the tables are right, and the
person who needs to see it — a finance lead, a partner, an exec — does not
have a workspace seat and is not getting one for a single number.

So the result gets screenshotted into a deck, which is where analysis goes to
lose its context.

## Publish the export

From the UI: **File → Export → HTML**. From a job or a script, use the
workspace export API with `format=HTML`, then publish the file:

```bash
databricks workspace export /Users/me/weekly-revenue \
  --format HTML --file weekly.html

curl -fsS -X PATCH \
  "https://commareports.com/api/v1/reports/$COMMA_REPORT_ID" \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile html weekly.html \
        --arg title "Weekly revenue — $(date +%F)" \
        '{title: $title, html: $html}')"
```

One report id per recurring analysis. Each run PATCHes the same URL, so
stakeholders bookmark it once and every refresh lands as a revision they can
diff against last week.

## Publish results, not the whole notebook

An export includes your code. That is right for a peer review and wrong for a
business audience, who will read the first `import` and stop. For stakeholder
reporting, render the final DataFrames into a small HTML document — headings,
tables, two charts, the conclusion in a sentence — and publish that. It reads
better and it gives reviewers prose to anchor comments to. See
[commenting on HTML](/comment-on-html).

## Limits

- **HTML body: 5 MB.** A notebook with many large output cells exceeds it
  quickly; trim outputs or publish a digest.
- **A snapshot, not a live notebook.** Nothing re-executes. Use a
  [routine](/docs/routines) or a Databricks job to refresh it on a schedule.
- **Scripts run, sandboxed:** `allow-scripts`, no `allow-same-origin`.

## Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision
history.

**[Publish a notebook →](https://commareports.com/)**

### Related

- [Jupyter](/with/jupyter) · [Colab](/with/colab) · [Quarto](/with/quarto)
- [Share an EDA report](/share-eda-report) · [dbt docs](/share-dbt-docs)
- [Scheduled reports](/features/routines/scheduled-html-reports)