Importing Jupyter notebooks (.ipynb) into the Workbench
The Workbench imports Jupyter notebook (.ipynb) files. Upload a notebook and it appears in your workspace alongside datasets and recipes. The Workbench does not host a Jupyter server, does not provide kernels (Python, R, or SQL), and does not open datasets as notebooks for interactive editing. The notebook integration is import-only.
Upload a .ipynb file from the workspace. The Workbench parses the notebook structure — cells, outputs, metadata — and stores it as a workspace item. Imported notebooks can be viewed, renamed, tagged, and shared like any other resource. They serve as documentation, analysis records, and reusable templates that you can download and run in your own Jupyter environment.
Notebooks are a common format for sharing analysis workflows. Importing them into the Workbench lets you: keep notebooks alongside the datasets and recipes they reference, share notebooks with your group, use notebooks as documentation for how a dataset was analysed, and build a library of reusable analysis templates. The notebook lives in the Workbench's sharing and discovery system — group members can find it, preview it, and download it.
The Workbench does not: execute notebook cells, provide a Python or R kernel, host an interactive notebook editor, or convert datasets into notebooks for editing. Imported notebooks are static — they store the code, output, and narrative exactly as uploaded. To edit or run a notebook, download it and open it in JupyterLab, VS Code, or any standard notebook environment.
.ipynb files is a core feature — not gated behind a commercial licence. The Workbench treats notebooks as workspace documents, not as an execution environment.