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.
KOSMA keeps two copies of your work: one on **your machine** and one on the **server**. The two do not update at the same instant. Knowing the gap between them explains most surprises around saving and sharing.
KOSMA does not save your changes as you make them. Until you save, your changes exist only in the open window. They cannot reach the server, and nobody you share the dataset with can see them.
When you save, KOSMA first writes the change to your machine, then sends it to the server. Only that second step makes your work visible on your other devices and to anyone the project is shared with.
If you close one project window with unsaved changes, KOSMA asks **Close project**: **Save**, **Don't Save** or **Cancel**, about that project alone. Seeing this dialog when you meant to quit KOSMA means you closed a window. You did not quit the whole application.
Quitting KOSMA asks once for every open project. The **Unsaved changes** dialog lists each project that still has unsaved work, and your answer applies to all of them at once. Read the list before you answer, so you see exactly what you would lose. When in doubt about a project on the list, click **Cancel**.
If you choose **Don't Save**, KOSMA discards your changes and returns the project to its last saved state. The screen can take a moment to catch up, so a cell may briefly still show the discarded value. This is not an error. Wait a moment and the correct value appears.
Every module's manager has a **Server** column with a small cloud icon in each row. Hover the icon to see a tooltip with the exact state. You can already read most of what you need from the icon alone: its shape and its colour.
The shape of the icon shows which direction data needs to move. The colour shows how urgent that is.
| Colour | Means | | --------- | ------------------------------------------------------------------------------ | | **Grey** | Nothing for you to do. Either everything is in sync, or KOSMA is working on it | | **Amber** | You have something here that has not reached the server | | **Blue** | The server has something that has not reached you yet | | **Red** | Both copies changed. You need to resolve this |
| Icon | Colour | Tooltip | Meaning | | ------------------------------------------------------- | ------ | ---------------------------------------------------------- | ---------------------------------------------------------------------- | |  | grey | **Up to date** | Your machine and the server hold the same version. | |  | grey | **Uploading** | KOSMA is sending your change to the server now. It finishes by itself. | |  | amber | **Not on the server yet** | You saved this on your machine, and the upload has not started. | |  | amber | **Upload failed** | The upload did not reach the server. KOSMA retries once you reconnect. | |  | amber | **Never uploaded — this copy exists only on this machine** | This dataset has never left your machine, so you cannot share it yet. | |  | grey | **Offline — edits stay on this machine** | You have no connection. Keep working, KOSMA queues your changes. | |  | blue | **Update available** | A newer version of this dataset is on the server. | |  | blue | **Update available — you also have local changes** | Both copies changed. Updating guides you through merging them. | |  | red | **Version conflict** | Both copies changed the same part, and you must resolve it by hand. |
The three amber tooltips describe the same underlying situation: your work is on your machine and not yet on the server. Hover the icon to find out which of the three applies.
Before you share a dataset, check its Server column. A recipient only gets what has reached the server. An amber icon means they would get less than what you currently see.
You can keep working while offline. KOSMA keeps your edits on your machine and uploads them once your connection returns, shown as the plain grey cloud above. Actions that need the server, such as sharing, updating a shared dataset or inviting someone, are unavailable until you reconnect.
A second state looks almost the same: **local-only mode**. It happens when your account is unreachable, not your network. Unlike offline mode, local-only mode does not clear on its own. See [work offline or in local-only mode](/kb/article/work-offline-or-in-local-only-mode) for how to tell them apart.
Signing in on another machine ends your session on this one. KOSMA only ever treats one machine as the live one, so your work never splits into two diverging copies.
Before you switch to another computer, save your work and check that its Server column has turned grey. Anything that only reached your machine stays there and is not available when you sign in elsewhere.
Markdown