Share & Print
You can read the Server column's icon and colour at a glance, and know when your work has actually reached the server.
Your work lives in two places, and they are not updated at the same moment: the copy on **your machine**, and the copy on the **server**. Most confusion about sharing comes from the gap between them.
KOSMA does not save as you type. You save, and until you do, your changes exist only in the open window. Nothing is lost by accident — you are asked before work is allowed to go — but the moment matters, because **an unsaved change cannot reach the server, and cannot reach anyone you share with**.
A save writes to your machine and *then* pushes to the server. That second step is what makes the work available on your other devices and to anyone the project is shared with.
Close a single project window with unsaved changes and you get **Close project**, asking about that one project: Save, Don't Save, or Cancel. So if you meant to quit and were asked about *closing a project*, you closed a window rather than the app.
Quitting is the other prompt. It asks **once**, not per window: **Unsaved changes** lists every project that has unsaved work, and one answer covers all of them. That list is the point — you can see what is about to be lost before you answer. Cancel is always the safe reply if a project on it is one you did not realise you had changed.
**Discarding rolls a project back to your last save.** The screen can take a moment to catch up — a cell may still show the discarded value for a second before it returns to what was saved. Nothing is wrong; the rollback is being applied.
Every module's manager has a **Server** column, and each row carries a small cloud icon. **Hover it and a tooltip names the exact state.** The icon alone gets you most of the way, because it is built from two things you can read at a glance.
**The shape tells you which way data has to move. The colour tells you whether it needs you.**
| Colour | Means | | --------- | -------------------------------------------------------- | | **Grey** | Nothing to do — either you are in sync, or KOSMA is busy | | **Amber** | Something is here that is not on the server yet | | **Blue** | Something is on the server that is not here yet | | **Red** | Both sides changed. It needs you |
| Icon | Colour | Tooltip | What it means | | ------------------------------------------------------- | ------ | ---------------------------------------------------------- | --------------------------------------------------------------- | |  | grey | **Up to date** | The server has what you have. Nothing to do. | |  | grey | **Uploading** | The push is in progress. It will finish on its own. | |  | amber | **Not on the server yet** | Saved on this machine; the upload has not happened. | |  | amber | **Upload failed** | It tried and did not get there. Reconnecting retries by itself. | |  | amber | **Never uploaded — this copy exists only on this machine** | It has never left this computer. Nobody else can be given it. | |  | grey | **Offline — edits stay on this machine** | No connection. Keep working; it queues. | |  | blue | **Update available** | Someone else's newer version is on the server. | |  | blue | **Update available — you also have local changes** | Both sides moved. Updating walks you through it. | |  | red | **Version conflict** | Both sides changed the same thing and it has to be resolved. |
**Three states share the amber up-arrow**, because the remedy is the same for all three: the work is here and not there. If you need to know which one, hover it — that is what the tooltip is for.
**Check this column before you share.** What a recipient gets is what reached the server, not what is on your screen. An amber arrow means they would get less than you can see.
You can keep working offline. Edits stay on the machine and go up when the connection returns — the plain grey cloud above. What you cannot do offline is anything that needs the server: sharing, updating, inviting.
There is a second, similar-looking state — **local-only mode**, when your *account* is unavailable rather than your network. The two look almost identical and only one clears on its own; the difference is set out in [work offline or in local-only mode](/kb/article/work-offline-or-in-local-only-mode).
Signing in on another machine **ends the session on this one**. That is deliberate, and it is why your work does not silently diverge into two copies: only one machine is ever the live one.
The practical rule follows from everything above — **save before you move to the other computer**, and check that the Server column has gone grey. Anything that only reached your machine is not there when you sign in elsewhere.
Markdown