Workspaces

Keep the data, connections, notes and agents for one area of work together, and ask about them in one place.

If you keep coming back to the same work, such as the weekly sales review for your shop, you end up picking the same datasets, attaching the same connections and re-explaining the same things every time. A workspace holds all of that in one place: the data, the databases, MCP servers and APIs you read, the notes that say what they mean, and the agents that work on them. Open a chat in a workspace and Crunch starts out knowing what you know.

What you’ll need

At least one dataset or connection worth keeping together. You can start with an empty workspace and add to it.
Your organization may let only its owners and admins make workspaces. If so, the Workspaces page says “Your organization lets its owners and admins make workspaces.” and New workspace isn’t offered.

Make a workspace

Click New workspace on the Workspaces page, under Data and connections in the left sidebar. In a message box you can also click + and choose New workspace.
Give it a Name, and under What it’s for say what the work is, for example “weekly sales review for the shop”.
Under Datasets, click Add datasets and pick up to 40.
Click Create workspace.

Once it is saved, the rest of its page fills in below the datasets.

What’s on a workspace page

Ask box. At the top is a message box of its own, “Ask” followed by the workspace’s name. Type a question, or /dashboard, /report or /plan, and click Ask; with nothing typed the button says Open a chat. Either way a new chat starts with this workspace in use.
Datasets. The data the workspace is about. Change datasets reopens the picker.
Semantic notes. Short docs that tell Crunch what your data means. Write opens a blank one; Draft from this asks Crunch to draft one from a dataset or an API. See Semantic notes.
Agents. The saved jobs a chat in this workspace can use. Check an agent to include it, or type a name and click New agent to make a draft that already uses this workspace’s data and connections. See Agents.
Connections. The databases, MCP servers and APIs it reads. Check the ones to include; if you have none yet, Add one takes you to the Connections page.
Chats. The chats started in this workspace, so you can pick one up again.
Pieces. The dashboards and reports made in it. See Pieces.
Share. Who else can use it (below).

When you change anything, click Save. A message beside the button says “Saved.”

Use a workspace in a chat

There are three ways in:

Click Use in a new chat on the workspace’s row, or on its page.
Use its own message box at the top of its page.
In any message box, click + and choose the workspace under Use a workspace. It shows as a chip beside the data chip, with an x to take it off, and takes effect from your next message. You can also type /workspace- and its name. See The + and / menus.

On a workspace you made, open Share:

Type an email address in the box (it shows name@example.com) and choose Use or Edit. Use lets them ask about it in a chat; Edit lets them change it too.
Click Add, then Save sharing.

The person you share with gets a copy, in the same way a shared dashboard is a copy: it holds your datasets, agents and notes as they were, not a live link to your account. The page tells you when the copy was made and what it holds. If something couldn’t be included, it says “Not shared:” with the thing and the reason. When your data changes, click Update shared copy; it can take a while.

The workspace appears for them under Shared with you on their Workspaces page. They can read it and use it in a chat. Only the Edit role can change it, and only its owner can delete it.

A shared workspace can include connections that need a sign-in. You decide how they work:

Tick Let them use my sign-ins for this workspace’s connections to let them call your MCP servers with your credentials. They never see the credentials.
Otherwise, each person connects their own. On the workspace, under Connections of this workspace, they click Connect your account, pick one of their own saved credentials and click Connect. Disconnect removes it again.

How to tell it worked

The workspace is listed on the Workspaces page with its counts, and a chat that uses it shows its name as a chip beside the data chip.

Good to know

Delete removes the workspace after asking, and Keep it backs out.
Your organization can turn off MCP servers or API connections, or allow only tools that read. Where that applies, the Connections page says so.
Save a new workspace before you add an agent to it: the Agents section says “Save the workspace, then add an agent.” until you do.

The + and / menus: attach a workspace from the message box.
Semantic notes: tell Crunch what the workspace’s data means.
Agents: save a job and run it again.
Connections: add the databases, MCP servers and APIs it uses.