# Working offline

This page is for the person who writes the notes. It states what still works
when your device has no connection.

Your notes live on your device as well as on your server, so the application
opens and works offline.

## What works

- Opening the application, the note tree, and any note.
- Writing, and **Save**. The version is made on your device and queued.
- Creating, renaming, moving, and deleting a note or a folder.
- Trash, and **Needs attention**.
- Search, over the notes on this device.
- Changing the theme.

## What needs a connection

History, Restore, **Delete permanently**, Export, and attaching an image. Each
of these reads from or writes to your server.

## What you see

The bottom of the sidebar carries one sentence about your saves. Offline it
reads "No connection. Notes stay on this device." When the connection returns
it changes to "Sending your save to the server." and then "Everything is saved
to the server." A save that waits in **Needs attention** does not go when the
connection returns, so the sentence then reads "1 save needs attention."

There is no separate queue list and no retry button: the queue sends itself in
order as soon as it can. If another device changed the same note meanwhile, the
work of both goes into the note, and the note offers Review. See
[Saving and history](https://docs.tidynotebook.com/saving-and-history.md).

The command palette adds a line saying that its results come from this device.

## Two things to know

**Persistent storage.** After your first save the browser is asked to keep your
data. If it refuses, it can remove the data of this device when the device
needs space. Notes on your server stay safe, so a quiet notice says this once,
and **Close** removes it from that device. When changes are only on this
device and cannot go to your server, a stronger notice shows until they do.
Keep the tab open until then.

**Updates.** When a new version of the application has downloaded, a notice
offers **Update now**. The update waits for you, so a running tab is never
replaced while you write. When your server needs a newer version, saving to
the server waits, and the same notice asks you to update. Your work stays on
this device until then.

When you select **Update now**, every open tab of the application stores its
text and closes, then reloads with the new version. If a tab cannot store its
text, the update stops and every tab stays as it was.

## Signing out with queued saves

If saves have not reached your server yet, **Settings** offers two buttons:
**Sign out and keep them**, which leaves them on this device for your next
sign-in, and **Sign out and remove them**, which does not.