Workspaces (co-work)
Persistent, shareable Databasin One sessions for teams.
A workspace is a named, persistent, shareable Databasin One session. Normal chat is ephemeral — close the tab and the context is gone. Workspaces fix that: they live in Databasin One, save themselves as you work, and can be handed to a teammate.
What a workspace is
Think of a workspace as a save file for an analysis. It keeps the conversation — every question and every answer — and the context you were working in, so you can reopen it later and pick up exactly where you left off. Share it, and a teammate can continue the same thread instead of starting over.
Why this matters
Two common frustrations disappear:
- "I'll just save the answer." People paste Databasin One answers into docs because the chat is throwaway. A workspace makes the whole session the thing you save — not just the conclusion, but the path you took to reach it.
- "Let's continue this tomorrow." Closing the tab and coming back is the most common workflow there is. With a workspace it just works.
Starting one
You can create a workspace from scratch, or convert an active chat into one — handy when a quick question turns into something worth keeping. Give it a name and a description, and it's yours.
Auto-save
Workspaces save themselves. About two seconds after the agent finishes responding, the workspace persists in the background — there's no save button. A small indicator shifts from Saving… to Saved so you know the state is safe.
Roles
Shared workspaces have two roles:
- Viewer — can open and read the session and download artifacts, but not change the conversation.
- Editor — full access: ask new questions, refine charts, generate documents.
Both roles run under their own data permissions. Sharing a workspace never escalates what someone can query — if a teammate can't see a table, opening your workspace won't change that.
Sharing and housekeeping
- Share a workspace with specific people in your org.
- List everything you own or have been shared into.
- Browse long sessions — message history is append-only and pages in as you scroll back, so even a sprawling analysis stays quick to load.
- Archive or delete when a workspace has run its course.