Notebook sessions
Start, use, and stop your notebook server.
An interactive Python environment for the lakehouse; querying data covers what to do once you are inside.
Prerequisite
You need the can_use_notebooks permission, checked at sign-in — see the note below.
Open your notebook server
Open Notebooks. Your first launch in a while spins up a private server just for you — about a minute — and JupyterLab opens when it is ready; later visits the same day open straight away. It is yours alone.
The image bundles everything for the lakehouse — marimo, DuckDB, pyiceberg, the JupyterLab Git
panel, and the databaas_auth helper — with nothing to install.
Choose marimo or Jupyter
Both run Python and reach the lakehouse through the same helpers, so pick either:
- A standard Jupyter notebook or the JupyterLab interface. See the JupyterLab documentation.
- A marimo notebook, reactive: cells re-run when their inputs change. See the marimo documentation.
Stop and restart
Your files persist when the server stops, so stopping is safe — see notebook storage. Stop it explicitly from the JupyterHub control panel (File → Hub Control Panel → Stop My Server); reopening Notebooks starts a fresh server, with the same one-minute wait. Restart if a session gets into a bad state — a stuck kernel, or a package you want gone.
A grant applies at your next sign-in
Notebooks is the one feature whose permission is read at sign-in, not on every request. A grant applies at your next sign-in; a revoke does not stop a server already running. See how access works.