# Notebook storage (/notebooks/storage)

Where your notebook files live, who can see them, and what survives a restart.

Your notebook server has a private home, a shared team folder, and scratch space. This page says
which to use for what, and what survives a restart.

## The three locations

| Path | Who can use it | Persists? | Use for |
| ---- | -------------- | --------- | ------- |
| `/home/jovyan` | Only you | Yes, across restarts | Your code, git clones, working files |
| `/home/jovyan/shared` | Everyone with Notebooks | Yes, across restarts | Files you want colleagues to open |
| `/tmp` | Only you | No, cleared on restart | Scratch |

<Files>
  <Folder name="home/jovyan" defaultOpen>
    <Folder name="shared" defaultOpen>
      <File name="team files" />
    </Folder>
    <File name="your notebooks and files" />
  </Folder>
</Files>

## Your private home

`/home/jovyan` is yours alone and is what the JupyterLab file browser opens on. By default it holds
10 GiB; if you need more, ask your platform administrator.

<Callout type="warn">
  Your home is **not backed up**. Treat the git remote as the source of truth for code: commit and
  push often. See [working with Git](/notebooks/git).
</Callout>

## The shared folder

`/home/jovyan/shared` is one folder for your whole team. Everyone with the Notebooks permission can
read, change and delete everything in it, so do not put anything there that only some colleagues may
see. It persists across restarts.

Use it to hand a file to a colleague. For code, a git remote is still the better place: it keeps
history and review. For data that belongs in the lakehouse, write a table instead — see [write a
table](/notebooks/querying-data#write-a-table) — so it is governed by catalog grants rather than by
who has Notebooks.

## Scratch space

`/tmp` is cleared every time your server restarts. Use it for intermediate files you can recreate.