First Steps
You know how to tell offline from local-only mode, what each one still allows and how each one ends.
KOSMA greys out some controls in two states: offline (the server cannot be reached) and local-only mode (the server can be reached, but your sign-in is no longer valid). In both, the Project Manager stays open.
When the connection to the KOSMA server drops, KOSMA briefly shows this message:
You're offline — showing local data
You stay signed in. In a budget that is not shared, you can edit, calculate and save as usual. KOSMA then saves only on your computer. The exception: you cannot change the name or comment of a budget that is already on the server. KOSMA restores the previous text and shows one of these messages:
The budget could not be renamed on the server, so its previous name has been restored.
The comment could not be saved on the server, so the previous comment has been restored.
Status and plan names of an unshared budget do save offline.
KOSMA greys out  **Project**, so you cannot create a project. The other actions that need the server are greyed out too:  **Account Admin**, **Upgrade License** and  **Log Out**. Pointing at one of them shows this tooltip:
Unavailable while offline
**Project Settings** opens read-only, and **Ok** is greyed out. Pointing at **Ok** or at a button in a guest row shows this tooltip:
You cannot edit project attributes offline
You cannot change a shared budget offline, no matter who shared it. In managers such as the **Budgets Manager**, this also covers the budget's name, comment and status and those of its plans. If you open a cell, KOSMA closes it again. Other changes, such as pasting or deleting rows, are not applied. If KOSMA is still connecting to the project, you see the first message; otherwise, the second:
Still connecting to the project — try editing this row again in a moment.
This row could not be locked for editing. Check your connection and try again.
Still, in a shared budget, a change you had already started when the connection dropped stays on your computer. KOSMA uploads it when you reconnect and shows:
Saved locally — offline, will sync when reconnected.
For what the **Budgets Manager** shows for a shared budget offline, see [manage budgets in a project](/kb/article/manage-budgets-in-a-project).
When the connection returns, the offline state ends by itself. The exception: if the server no longer supports your version of KOSMA, KOSMA stays offline even with a working connection. See [keep KOSMA up to date](/kb/article/keep-kosma-up-to-date).
You can be signed in on only one computer at a time. If you sign in on a second computer, your sign-in on the first one ends. It also ends when an administrator ends it, when you have not used KOSMA for about 30 days, or when your account is deactivated. KOSMA then saves every open project on your computer, signs you out and shows the login screen. Once you sign in again, KOSMA uploads the changes when you open the project. If you signed in on another computer or an administrator ended your sign-in, KOSMA shows:
Your session was ended (signed in elsewhere or ended by an administrator). Your work was saved on this machine and you have been signed out.
If the sign-in ended after about 30 days, or your account was deactivated, KOSMA shows one of these messages instead:
Your session expired. Your work was saved on this machine and you have been signed out.
Your KOSMA account has been deactivated. Your work was saved on this machine and you have been signed out.
If KOSMA cannot save your work, it does not sign you out. It switches to local-only mode (next section), keeps your work open and shows, for example:
Your session was ended (signed in elsewhere or ended by an administrator), but your work could not be saved. Your work is still open here — log in again, then save it.
Click **Log In Again**, sign in and then save your work.
In local-only mode, KOSMA reaches the server, but your sign-in on this computer is no longer valid. This happens for one of two reasons: your sign-in ended and KOSMA could not save your work, or the server rejects your sign-in for another reason. KOSMA then shows the  **Log In Again** button in the left panel. If the server rejected your sign-in, KOSMA also shows this message:
Your session ended (signed in elsewhere, ended by an administrator, or expired). Local projects stay open for reading and export; log in again to keep editing.
While local-only mode lasts, you can read, print and export the open project. You cannot edit anything. KOSMA greys out  **Project** here too. KOSMA also greys out  **Account Admin** and **Upgrade License**. Pointing at one of them shows this tooltip:
Unavailable until you log in again
**Project Settings** also opens read-only, with the same tooltip on **Ok** and on the buttons in a guest row.
**Log Out** now reads  **Clear local session** and stays available. Clicking it removes only your sign-in on this computer. Your projects do not change.
Local-only mode does not end by itself. To end it, click  **Log In Again** and sign in. For the sign-in itself, see [log in to KOSMA](/kb/article/log-in-to-kosma). If someone removed your account or your seat, the sign-in fails. KOSMA then shows this message:
Your account is unavailable — logging in was refused. Local projects stay open for reading and export; contact your team admin to restore access.
In both states, you cannot open a project that you have never opened on this computer. There is no local file for it. Open the project once KOSMA is connected again and you are signed in. See [open a project](/kb/article/open-a-project).
Markdown