liveknowledge always works without signing in. You can land on a new knowledgebase , build something real, and only later decide whether you want an account. To make that possible, liveknowledge gives every guest a quiet identity, kept per browser, that owns whatever you put on the server.
Your per-browser id
The first time you visit, your browser takes a quick trip to the liveworkspace accounts site and comes back with a guest token, which it keeps in localStorage. The token names your guest id and lasts 45 days, renewed when you visit in its last 15 days. Everything of yours on the server as a guest (knowledgebases you share or sync, folders, images) is owned by that id, which is how the app knows which content to show you when you come back. The editor sends the token with each request; you never see or type it.
The trip to liveworkspace.app is a redirect you may glimpse for a moment, with nothing to fill in. liveworkspace.app remembers which guest this browser is, so a fresh token names the same guest, and a guest who comes back now and then keeps their identity.
Your guest id is liveworkspace's, so the other liveworkspace apps you use in the same browser know you as the same guest: a knowledgebase you make in liveknowledge and one you make in another liveworkspace app belong to the same guest, and both appear in the Explorer when you choose All Apps.
New knowledgebases you make as a guest start offline, saved only in this browser, so nothing you try out is sent to our servers until you choose to. To share one, open Share and press Sync Knowledgebase: it uploads under your guest id and the Share options appear. A knowledgebase you create inside a folder goes to the server straight away.
Two things follow from this:
- It is per browser, not per person. The id lives in one browser on one device. Open liveknowledge in a different browser or on another device and you get a fresh guest id, so your earlier knowledgebases will not appear there.
- It is not cross-device. Guest content does not sync between devices, because there is no account tying them together yet.
As a guest you still get the core of liveknowledge: saving, share links and real-time collaboration all work, once a knowledgebase is synced. A few things need an address or an account to attach to, so they ask you to sign in: teams, API tokens, email notifications and the Google Drive mirror.
What this means for your data
Because your guest content is tied to a single browser, clearing that browser's storage, or using private browsing that discards it, deletes your knowledgebases kept Offline and means the app can no longer recognise you as the owner of the ones on the server. Those are still there, until they are deleted after 400 days, but nothing in a fresh browser can claim them back. Treat your guest knowledgebases as living in that browser.
Share links are the exception: anyone holding one, including you in another browser, can still open that knowledgebase with the link's role. They just won't be its owner there.
How long guest work is kept
Your guest id stays alive for as long as you keep using any liveworkspace app in this browser. If 400 days (about 13 months) go by without a visit, the id can never be handed back to you, so everything it owns on the server is deleted for good: your knowledgebases, your folders and your Trash. That includes knowledgebases you shared, so their links stop working too. Knowledgebases kept Offline are not touched, because they were never on the server.
To keep your work for longer, sign in. Your knowledgebases move into the account, and an account's knowledgebases are never deleted this way.
If you want your knowledgebases to follow you across browsers and devices, signing in is the answer. When you sign in, whether to a new account or an existing one, the knowledgebases of yours on the server move into it automatically, and we offer to move the ones kept Offline too, so you do not lose the work you have already done.
Doing serious work as a guest? Create an account before clearing your browser data, and move your knowledgebases kept Offline across when we offer, so nothing is left behind.
How this works in 5 other apps
Was this article helpful?
Still need help?
Try Troubleshooting, or tell us what you were trying to do.