First Steps
You can tell KOSMA's two degraded states apart, know what each one still lets you do, and know which one clears by itself.
Two different things can grey out the buttons in KOSMA, and they look almost identical — a message, and disabled controls. They are not the same problem, and only one of them clears on its own.
Your machine has lost the connection. Nothing is wrong with your account.
You stay signed in, your projects stay open, and **you can keep working normally** — editing, calculating, saving. Only the things that genuinely need the server go quiet. When the connection comes back KOSMA says so (*You're back online*) and everything returns by itself. There is nothing for you to do.
Here KOSMA reaches the server fine; the server no longer accepts the sign-in this machine is holding. Three things cause it, and the app cannot tell them apart, because they arrive looking identical:
- **You signed in on another machine.** A KOSMA licence allows one active sign-in at a time, so signing in elsewhere ends this one. This is the everyday cause and it is completely normal. - **The sign-in expired** after about a month without using the app. - **Your account or team seat was removed.** Rare.
Because the first two are by far the most common, KOSMA says *your session ended* and offers **Log In Again**. If that sign-in is then refused, it says your account is unavailable — that message only appears once KOSMA has actually tried and been turned away, so it is a real answer rather than a guess.
**In local-only mode your projects are read-only.** You can open them, read them, print and export them — but not change them. Nothing you have already saved is lost or at risk; the lock is simply KOSMA declining to write new work into a project under a sign-in the server will not confirm. Log in again and editing returns.
| | **Offline** | **Local-only mode** | | ----------------------- | ------------------------------------ | ------------------------------------ | | what happened | no connection to the server | the server rejected your sign-in | | can you still edit? | **yes**, normally | **no** — read and export only | | clears by itself | **yes**, when the connection returns | **no** | | what fixes it | reconnecting | **Log In Again** | | a disabled control says | *Unavailable while offline* | *Unavailable until you log in again* |
The tooltip is the quickest tell: hover any greyed-out control and it names which of the two you are in.
Anything that has to reach the server:
- Creating a project, and renaming, archiving or deleting one. - Opening a project you have **never** opened on this machine — there is nothing local to open. - Anything to do with your account or licence.
**Log Out is greyed out while you are offline.** That is protective, not broken: the session KOSMA is holding is the only thing keeping you in the app, and dropping it would strand you on a sign-in screen that cannot complete without the network. The tooltip reads *Unavailable while offline*. It comes back when the connection does.
**In local-only mode the control changes to Clear local session**, and it stays available. There is nothing to log out of — the server already rejected the stored sign-in — so what is left is the local copy of it, and clearing that lets the next sign-in start from scratch. **Your projects are not touched.** Use it if *Log In Again* has not resolved things.
When you are signed in normally, **Log Out** simply drops the stored session and returns you to the sign-in screen. Save your open projects first: signing out does not delete anything, and it does not save for you either.
You do not need to log out before signing in on another machine — see [what your licence includes](/kb/article/what-your-licence-includes).
In the dataset lists, a dataset can carry a status whose tooltip reads *"Never uploaded — this copy exists only on this machine"*. That is about **one dataset's** backup state, not about your session, and it has nothing to do with the mode described here. You can be fully signed in and online and still have datasets that are local only, simply because they have not been uploaded yet.
Markdown