Data exports

Decide whether anyone in your organization may download data as a file, and see every download and refused attempt.

Sometimes a teammate wants a dataset on their own computer, to open in a spreadsheet or hand to someone else. Once a file leaves BumbleB, though, your organization’s access controls no longer cover it. So downloading data is something your organization decides on, and every download is written down where the owner and admins can see it.

Data export is off for every organization until the owner or an admin turns it on. “Export” here means downloading a dataset, a table or a sheet as a file (CSV, JSON or Parquet). A chart, story or dashboard you share as a PDF isn’t an export, and this setting doesn’t affect it.

What you’ll need

To be the owner or an admin. Members don’t see the setting or the log, even if they have been given the right to manage users. See Roles.
No particular plan. Data exports is in the sidebar on every plan. The switch itself sits on the Organization page, which shows in the sidebar on plans that include it — currently Team (see pricing).

Turn export on or off

Open Organization in the hub and find the Data export panel.
Tick Allow dataset export. It saves as soon as you click, and shows On or Off next to it.
Under Who may export, choose Owners, Admins and Members. Owners are always included once export is on, so the owner can always turn it off again.
In Most rows in one export, enter the largest file you want anyone to download, as a number of rows. The most you can set is 100,000.

When export is off, nobody in your organization sees a download option, and BumbleB refuses any export request. A change reaches every part of BumbleB within about a minute.

Heads up: a dataset bigger than your row limit is refused, never cut short. Nobody ends up with a file that quietly holds only part of the data.

See who downloaded what

Open Data exports in the hub’s sidebar. It lists every export from your organization, newest first, 50 to a page, including attempts that were refused. Each row shows:

When it happened and Who asked (their email);
the Dataset, the Format, and the number of Rows and the Size of the file;
the Result — Downloaded, Refused or Failed — with the reason when it wasn’t downloaded, such as “export is off”, “not allowed for their role” or “over the row limit”;
From, the part of BumbleB the export was asked for in.

Use Person, From and To to narrow the list to one teammate or a range of days. Use Older and Newer to move between pages.

Download this log (CSV) saves the list, with the same filters, as a spreadsheet you can keep or pass to whoever reviews access. It holds at most 10,000 rows, so narrow the dates for a longer period. The file is the log only — who exported what, and when — never the exported data itself.

How to tell it worked

Back on Organization, the Data export panel’s History lists every change to the setting: When it was made, Who made it, and the Change (for example, Off → On for owners, admins, up to 100,000 rows). If nobody has changed it, it says “Never changed. Export is off by default.”

Good to know

The hub never receives your exported data. It keeps only the record of each export.
The log isn’t deleted on a schedule. Every export your organization has made stays listed.
Turning export off doesn’t sign anyone out. It simply stops the next download from starting.

Your organization — the page where the Data export panel lives.
Roles and what each can do — who counts as the owner, an admin and a member.
Closing your account — what happens to your data if you leave.