Guides
Adding data later
Three ways to add data to an existing workspace (from the screen, through Claude, from a colleague's release), and why added data cannot be taken out.
App in development
On this page
The portal screens are in development. Their words and layout may still change; the commands behind the buttons are already built.
Work often turns up a need for more data, and you can add it to a workspace you already have. Before you do, look at how it changes who can see the workspace's results. IDs, paths and numbers here are examples.
From the screen
-
Step 1: Press [Add data]
On the workspace, press [Add data]. The same “Data this workspace uses” tree as for a new workspace opens: “Data already in this workspace is shown in gray.”
-
Step 2: Choose what to add
Tick what you want to add. Each tick updates “Who can see this workspace's results” at once, and each item shows its visible files, such as “4 if added”.
-
Step 3: Press [Add data]
Press [Add data] at the bottom. You see “Added data: /tables/labs”.
ws add-data ws-0012 /tables/labs Added data: /tables/labs (1,256 visible files)Who can see this workspace's results: 2 of 31 people. Admins can always see.Condition: ehr_full and one of ct_research or imaging_all In a running workspace the data appears in /data at once, without a restart. Adding a table also rebuilds the DuckDB file.
[My data] and a colleague's share page also offer [Add to workspace], which adds that item straight to one of your workspaces.
Through Claude
Tell Claude what data you need, and it:
- looks for data it could add, seeing names only: it cannot read the files before you approve;
- checks how adding it would change who can see the results, and tells you;
- makes a request to add it and gives you an approval link.
The data appears in /data only after you approve. The tools Claude uses, in that order: list_data, preview_add_data, request_add_data.
From a workspace terminal
A workspace terminal can make the same request. It is only a request: nothing changes until you approve it.
In a workspace terminal
synapse ws request add-data /tables/labs Output (example)
Requested approval: a-0031Data to add: /tables/labsVisible files: from 1,252 to 1,256Who can see this workspace's results: from 4 to 2 of 31 people. Admins can always see.It runs after the researcher approves it in the portal: https://app.example.org/approve/a-0031 A colleague's release as data
You can add a release a colleague made, as long as you may see it.
- Paste the share link to Claude. It becomes a request to add that release to the workspace.
- From the share page. Open the link, press [Add to workspace] and choose the workspace.
- As a command. Use the release ID or the share link where a data path would go:
ws add-data ws-0012 r-0137The release appears read-only in /data/releases/, in a folder named after its ID. Whatever you release from this workspace later lists it among its sources.
Added data cannot be taken out
A workspace remembers every piece of data it could ever see, because something made from that data may still sit in the work folder. So added data cannot be removed, and the narrower audience it brings stays. To work without it, create a new workspace.
If an admin later revokes access and the files disappear from /data, the workspace's record that it used them remains.
If it does not work
| What the screen says | What it means and what to do |
|---|---|
| This data is already in the workspace. | Only new data can be added. |
| The same request is already waiting: a-0031 | Approve or reject that request. |
| The waiting request limit is reached. | A workspace keeps at most 10 waiting requests by default. Deal with the waiting ones first. |
| The workspace is archived: ws-0012 | Restore it, then add the data. |
| The owner cannot see this release: r-0137 | Only releases the workspace owner may see can be added. |