Skip to content

November 6, 2026

Verified dashboards

Admins can now mark a dashboard as verified, the same way they verify models, so everyone knows which numbers to trust. Open the more (…) menu in a dashboard’s header and choose Verify dashboard. A green Verified chip appears next to its name, and hovering it shows who verified it and when.

Verification stays put as the dashboard is edited, and a duplicated dashboard starts out unverified. Models now use the same header menu and chip, so verifying works the same way everywhere. Read more in Introducing verified dashboards.

Choose who can manage models, context, and data sources

On Enterprise, admins can now decide which members and groups hold eight workspace permissions from the new Settings → Permissions page. You can let a data team create and verify models, verify dashboards, manage workspace-wide AI context and skills, manage data source context, add and configure data sources, manage groups, and invite members, without making everyone an admin.

Nothing changes until you configure it. Every permission starts with today’s defaults, and admins always keep every permission.

More control over API keys and connected apps

API key settings are rebuilt around a table that shows each key’s status, prefix, creation date, expiry, and last use, with search and a status filter. New keys get an expiration date (90 days by default, with 1, 7, and 30 days, a custom length, or never also available), you can rename keys, and revoking a key keeps it in the list for your records. The secret is shown once, in a dialog that won’t close until you copy it.

You’ll also get an email whenever a new API key is created on your account or an app connects through MCP. Sign out everywhere can now revoke your API keys and connected apps in the same step. Creating a key, connecting an MCP app, and sensitive admin actions like inviting members, raising roles, or changing SSO now ask you to sign in again if you haven’t signed in within the last 10 minutes. The MCP consent screen also shows where an app will send you, and warns when Basedash doesn’t recognize the app.

Find audit log events faster

Audit logs have a new filter toolbar. Search applies as you type, and you can filter by date (the last hour up to 90 days, or a custom range), actor, category, and source. Filters show up as pills you can clear one at a time, and they’re saved in the URL so you can share a filtered view. Export CSV now lives in the page header and exports exactly what you’ve filtered to.

The Members, API keys, and Audit logs pages also share a cleaner table layout. Members and API keys can be sorted by column.

Fixes and improvements

  • Added a single rename dialog for charts, dashboards, tabs, folders, chats, automations, data sources, tables, and columns, with an optional description field.
  • Stopped the quick acknowledgment at the start of a chat from guessing at an answer before Basedash has looked at your data.
  • Fixed long Slack automation responses with several charts failing to send.
  • Kept data change automations running when a different automation’s data source can’t connect. Manual runs now show a clear error when the trigger’s data source is unreachable.
October 30, 2026

Sign out of every device at once

If you think your account was used somewhere it shouldn’t have been, you can now end every session in one step. Go to Profile → Security and choose Sign out everywhere to sign out of every browser, the desktop app, and any embeds you’ve opened, including the session you’re using now.

API keys and MCP connections keep working, so the integrations that rely on them don’t break. Each sign-out is recorded in your audit log.

AI answers go further

Basedash’s AI now reasons more deeply by default in chat, the dashboard and chart editors, automation setup, and scheduled reports and alerts. Broad questions like “search all of our data for…” now get complete answers more often, instead of stopping after the first few results.

The AI is also better at adding dashboard filters. When you ask for a region or time period filter on a dashboard that already has charts, it connects the new filter to every chart it can meaningfully filter, tells you which ones it skipped, and uses your existing filters when it builds new charts.

Configure every chart setting through the API

The public API now covers everything in the chart settings panel. When you create or update a chart, you can set number format and currency, full numbers, metric labels and values, legends, goal lines, axis bounds, stacked or grouped bars, color by category, series and segment colors, image, text, and map options, and table column widths and pins.

Chart responses include these settings too, so you can read a chart’s full configuration, copy it, or keep it in sync from your own code. Existing requests behave exactly as before, since every new field is optional.

Clearer names across the app

We cleaned up some confusing labels. The toggle above chart results now reads Data and Visualization, instead of “Response” and “Chart”. Database connections now say Update schema and show when the schema was last updated, while connectors say Sync data, so a database no longer looks like it copies data the way a connector does.

Filters are called filters everywhere now, and the {{token}} you write in SQL is called a SQL variable. The Data section’s URLs moved from /tables to /data to match its name, and old links redirect automatically. The dashboard chart menu also drops its duplicate Edit item. SQL editor is still there, and clicking a card still selects it for AI editing.

Fixes and improvements

  • Formatted model SQL when you open the model editor, so queries saved as one long line are easy to read. Opening a model doesn’t mark it as changed.
  • Signed existing members and viewers into their own accounts when they open your embedded Basedash, instead of creating a second user with the same email. People who already have a duplicate get their own account back on their next embedded sign-in.
  • Supported more kinds of SQL on data sources with access rules, so AI answers no longer fall back to narrower queries.
  • Fixed the quick acknowledgment in chat occasionally showing two sentences run together.
  • Made “contains” and “does not contain” filters treat % and _ as plain characters instead of wildcards.
  • Fixed browsing Postgres, Supabase, Redshift, and MotherDuck schemas and columns named with reserved SQL words like order or user.
  • Fixed SQL Server filters on values with non-Latin characters, like Japanese or Cyrillic text, which could match nothing.
  • Read allowed values from SQL Server CHECK constraints, so those columns show their options.
  • Made Insights more reliable: digest emails no longer get dropped, and insight runs retry through temporary AI provider errors.
  • Added chart query saves, automation changes, and subscription changes to audit logs.
  • Required access to every data source a dashboard uses before its public link can be turned on.
  • Restored the light-mode loading screen’s colors and sharpened full-screen visuals on high-resolution displays.
October 23, 2026

Database connections can verify their certificates

Postgres, Supabase, Redshift, MySQL, and PlanetScale connections now have a “Verify server certificate” setting. With SSL on and verification on, Basedash checks that the database it connects to really is your database before sending credentials or reading results, not just that the connection is encrypted. Verification also checks the hostname, including on connections that go through an SSH tunnel.

New connections verify by default. AWS RDS and Supabase work out of the box, and if your provider signs certificates with its own CA, like DigitalOcean or Google Cloud SQL, paste it into the new “CA certificate” field. If a connection test fails on the certificate, Basedash tells you to add your provider’s CA or turn verification off. Existing connections keep working exactly as before until you turn verification on. Connections created through the public API also verify by default unless the request turns it off.

Sharing works inside full app embeds

The Share button is back on dashboards, folders, and chats in full app embeds. Embedded users can see who has access, and people with full access can change it, all without leaving your app.

Anything that would send someone outside the embed stays hidden. The “Copy link” button, public link, and embedding controls don’t appear in embedded share menus, and the remaining “Copy link” items on chats, automations, chart pages, models, and insights are hidden in embeds too.

Fixes and improvements

  • Showed inline charts in finished automation runs right in the collapsed preview, instead of a loader that waited for “Show more”. Charts load as they scroll into view.
  • Fixed changes like deleting a chat that could fail when the server was briefly slow. They now go through once it catches up.
  • Made app updates wait for in-progress changes to finish saving before reloading, so you no longer get a “Leave site?” prompt.
  • Required access to a data source to point a dashboard filter at it, change the filter’s query, or make the filter public.
  • Redrew the key and shield icons in settings so they’re easier to read at small sizes.
October 16, 2026

View-only members are here

You can now invite people to your organization as View-only. View-only members can open the dashboards, saved charts, automations, and chat history that are shared with them, run saved charts, use dashboard filters and drilldowns, and export results. They can’t create or edit anything, run automations, or chat, so it’s a safe way to give stakeholders, clients, or a whole department access to your numbers.

The role works as a ceiling on top of your existing sharing: anything a View-only member could edit or manage becomes view access, and anything they couldn’t see stays hidden. Their grants are kept, so promoting someone back to Member restores exactly what they had. Pick View-only in the invite dialog or the role menu in member settings, set it through the public API, or pass it as the role in an embed’s sign-in token.

Manage access from your own app

The public API can now read and set who can view, edit, or manage a dashboard, automation, or chat. Each one has its own access endpoint, so you can restrict an item to specific groups or members, open it to everyone, or let a dashboard inherit its folder’s access. The data source access endpoint now covers schema, table, and column rules too, so rules like “billing tables are only visible to the billing group” can be provisioned from your own systems.

Embedded analytics can sync groups as well. When an embed’s sign-in token includes a list of groups, Basedash adds the user to the matching groups in your organization on each login and removes them when a group is no longer listed. Memberships you set in Basedash, through the API, or through SCIM are never touched. To keep that matching unambiguous, group names are now unique within an organization regardless of capitalization, and any existing duplicates were renamed with a number, like “billing 2”.

Every change you make saves more reliably

We rebuilt how Basedash saves your work. Every edit, from renaming a dashboard to changing a chart setting, sharing a data source, or running an automation, is now saved and checked by the server, one change at a time. If a save fails, you’ll see a “Couldn’t save change” message instead of your edit quietly disappearing.

Bigger actions are sturdier too. Duplicating a dashboard or tab now happens in one step, so the copy includes every chart and filter, never ends up half-finished, and tells you if any charts were left out because you can’t query their data source. Quick back-to-back chart setting changes no longer overwrite each other, moving a chart to another dashboard brings its filters along in one go, and dragging or resizing charts holds its position until it’s saved.

Fixes and improvements

  • Fixed scheduled automations that showed as finished but didn’t send their email or Slack delivery.
  • Fixed adding a chat chart to a new dashboard, so the chart lands on the dashboard and the new dashboard opens without a “Dashboard not found” screen.
  • Added a “Blocked by access controls” state for charts whose SQL access controls can’t verify, with a shortcut to edit the query, instead of a “Failed to run query” error.
  • Fixed “Permanently delete” in Recently deleted, which now removes the chart for good.
  • Made dashboard right-click menus show only the actions you can take. Deleting a dashboard you can edit but not manage is greyed out with a “Manage only” hint, so you know what to ask for.
  • Fixed “Select all” on Fivetran synced tables failing when two source columns map to the same destination column. If Fivetran rejects a selection, the error now shows Fivetran’s reason.
  • Clarified data source access entries in the audit log, which now read like “Gave view access to a data source” or “Replaced table and column rules on a data source”.
  • Showed a clear error when a group name is already taken, instead of the rename silently failing.
  • Limited Slack thread replies from people without a Basedash account to the data sources the person who started the thread can access.
October 9, 2026

Message Basedash directly in Slack

You can now chat with Basedash one-on-one in Slack. Open the Basedash app’s Messages tab, pick a suggested prompt or type your own question, and get the same answers, charts, and analysis you’d get in a channel thread, without @mentioning the bot in front of everyone.

CSV files now come through as real Slack files. When you ask Basedash for a CSV in a Slack thread, the file is attached right in the conversation, ready to open or forward. Workspace admins will see a “Slack update available” prompt in Basedash; approve the new permissions to turn on file uploads. Until then, replies keep their download link.

Automations can deliver CSV files

Scheduled automations can now create downloadable CSV exports, the same way chat can. Ask for a CSV in an automation’s instructions, like “send a CSV of last week’s new signups every Monday”, and each run builds the file from your data.

Every delivery includes the file. Slack messages attach the CSV in the message’s thread, and emails and the automation’s run history include a Download CSV link. If a run builds the CSV but stops before writing its summary, the file is still delivered. Downloads go through Basedash, so recipients still need access to the automation to open them.

Stopping a response keeps what’s already done

Pressing Stop in chat no longer erases the turn. Your question and the partial answer stay in the conversation with a “Stopped” label, so you can read what the assistant found before you redirected it. On your next message, the assistant knows the previous answer was cut short and that any charts or edits it started may be half-finished, so it picks up from there instead of starting over.

Long analyses also end more gracefully. Chat can now take up to 50 steps on a single question, up from 30, and when it gets close to the limit it wraps up on its own: it summarizes what it found and lists what’s still unfinished, instead of ending with a bare “Continue” button.

Insights reads like a newspaper

The Insights feed has a new borderless, editorial layout. The top story leads the page, the rest flow in two columns separated by thin rules, charts sit flush with their captions, and each preview shows as much text as fits beside its chart. When you open the sidebar or chat panel, the feed switches to one column instead of cramping the stories. Insight pages get larger headlines and more readable body text, on desktop and mobile.

Large Insights feeds now load in pages with a Show more button, so the page opens quickly no matter how many insights you have. Scheduled insights also work across all of your data again: organizations with several data sources get findings from every connection the insight’s creator can access, not just one.

Fixes and improvements

  • Clarified chat error messages when a data source is down. Chat now names the data source it couldn’t connect to, instead of showing a generic error or blaming the AI model.
  • Added a Retry button to charts that fail with “Unable to connect to database”, so you can recover without reloading the page.
  • Fixed long chats and automations failing with “Your input exceeds the context window”.
  • Fixed chats failing with “Invalid time value” when a table contained dates far in the future.
  • Fixed insights that could go missing when they were being generated during a Basedash update. They now retry and finish.
  • Applied schema, table, and column access rules to organization admins too, so a “no access” rule now covers everyone. Admins can still see every object in the access settings to change its rules.
  • Improved AI-written SQL for MotherDuck databases connected through the PostgreSQL connector, so queries use DuckDB syntax instead of failing on Postgres-only functions.
  • Made new charts open the dashboard chat with your cursor in the message box, so you can describe the chart right away.
  • Added a “This dashboard has been deleted” state for dashboards shown in chat, instead of a blank preview.
  • Fixed new dashboard headers and blocks that could appear and then disappear until you reloaded.
  • Fixed public dashboards embedded on other websites failing to load charts in Safari.
  • Fixed record dropdown filters on public dashboards showing “No values found”.
  • Polished the mobile experience: the Back button works after redirects, chart menus are reachable on touch screens, and menu items no longer need two taps on iOS.
  • Restyled the sign-in pages for connecting MCP clients to match Basedash, with light and dark mode and translations.
  • Refreshed icons across the app, with clearer symbols, filled radio buttons, and evenly spaced keyboard shortcut keys.