Skip to content
Log inStart free

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.