brewDB Workspaces & Sharing

Every brewDB query lives in a named tab, and tabs are grouped into workspaces — server-persisted containers you can share with other users. The legacy application had no query interface at all, so there was nothing to organize or share; workspaces, tabs, and their autosave and sharing mechanics are entirely new.

Tabs & Autosave

Each query gets its own tab in the tab bar, and tabs can be renamed and dragged into whatever order you prefer. As you edit a query, brewDB debounces the change and autosaves it to the server roughly every 800 ms, with a live “Saved · Ns ago” indicator in the tab bar so you always know how current the saved copy is.

Alongside the server copy, brewDB keeps a per-user resume cache in your browser’s local storage, so reopening brewDB drops you back into the tabs you had open. If that cache ever points at a tab or workspace id that no longer exists on the server — for example after a workspace was deleted elsewhere — it self-heals rather than leaving you on a broken tab.

Workspaces & Sharing

Tabs are grouped into workspaces, and workspaces are the unit of persistence and sharing: each one is a server-persisted container for its set of tabs. brewDB gives you two views into your workspaces — “My” workspaces, which you own, and “Shared with me,” which lists workspaces others have shared with you.

Sharing a workspace goes through an ACL matrix, letting you control which users or groups can see or edit it — and everything inside it, since a workspace’s tabs and their queries travel with the workspace.