November 20, 2026
Ask for an Excel file and get one
Basedash’s AI used to export results only as CSVs. Now you can ask for an Excel file instead. Ask for “an Excel file”, “an .xlsx”, “a workbook”, or “a spreadsheet” in chat or in an automation’s instructions, and you’ll get a real .xlsx that opens straight into Excel, Numbers, or Google Sheets, with no import step.
Excel files work everywhere CSVs already did. You can download them from the chat, they’re uploaded as files in Slack, they’re attached to automation emails, and MCP clients can fetch them. The file card in chat now shows which format you got, so it’s easy to tell an Excel file from a CSV.
Send automation emails to whole groups
Automation email recipients can now include groups. Pick a group, and everyone in it gets each run, without you adding people one by one or keeping the list up to date as your team changes. If someone is in two selected groups, or is in a group and was also picked by name, they still get just one email. The recipient picker shows each group’s member count, plus a running total of the people who will receive the email.
You can also type in addresses of people who aren’t members yet, as long as they’re at your organization’s own domain: your work email domain or a domain you’ve verified under Settings → Security. Addresses already saved on an automation keep receiving it, and the same domain rule applies when you create or update automations through the public API.
Restrict access to your organization by IP address
Admins can now limit their organization to trusted networks, like your office or VPN. Under Settings → Security → Network access, add IP addresses or ranges (IPv4 or IPv6), or click Add my IP, then turn the allowlist on. Requests from anywhere else are blocked in the web app and also for API keys and MCP clients, so your data can only be reached from places you trust. Public links and embeds keep working.
Basedash also helps keep you from locking yourself out: you can’t turn the allowlist on unless your own address is on it. If someone’s laptop drops off the VPN mid-session, they see a clear message explaining why, along with any of their other organizations they can still open from that network.
There’s also a new Allow embedding setting under Settings → Dashboards. Turn it off to hide public links and embedding from the share menus and take every existing public link and embed offline at once. Turn it back on, and the same links work again.
Chart axes label every period cleanly
We rebuilt how chart x-axes pick their labels. Time axes now label whole calendar periods at the bar or point where each one starts: days, Mondays, months, quarters, or years. Basedash picks the finest level that fits without crowding, and the most recent data always gets a label. The year shows where it changes, so a long axis reads like a calendar instead of a scattering of dates.
This fixes several issues. Yearly charts no longer drop the label under their first or last bar. Tooltips no longer show the evening before a bucket for viewers outside UTC, and drill-downs from those charts open the right day. Category labels like “Item 1” or “Plan 2” are no longer mistaken for dates. When category labels don’t fit side by side, they now tilt just enough to fit and get trimmed before they crowd the chart.
Fixes and improvements
- Let chat consult a more capable AI model when it’s working through a particularly difficult analysis, for more reliable answers to hard questions.
- Brought back creating and managing automations and subscriptions from embedded Basedash, including from chat.
- Fixed drill-downs that could show records from a previous filter selection after you changed a dashboard’s date filter.
- Made dashboards scroll normally on tablets instead of dragging charts around. Charts can still be rearranged and resized with a mouse or trackpad.
- Fixed schema syncs for some Postgres-compatible databases that finished without showing any tables or columns.
- Made Insights more reliable. Temporary AI provider errors are now retried, and a data source Basedash can’t connect to no longer stops insight posts from your other sources.
- Showed a clear error message when an MCP connector’s server URL redirects to a different site.
- Let the AI recover when it tries to create or edit a filter without a dashboard or chart, instead of failing the whole MCP request.
- Showed an access-denied page instead of an error page for public dashboards whose creator has left the organization.
- Changed the public API to require a
Content-Type: application/jsonheader on requests with a body. Requests with any other content type now get a 415 error.