Basedash SCIM - Your org changes. Access keeps up.
Basedash SCIM keeps workspace identity aligned with the directory your company already manages. As people join, change teams, or leave, users, groups, and organization memberships stay current—reducing app-by-app cleanup and helping leaders answer who still has access. Together with SSO, RBAC, and RLS, it gives enterprise teams more confidence to roll Basedash out without turning identity administration into a bottleneck. Your org changes. Access keeps up.
Replies
How does the AI handle more complex queries that need joins across multiple tables, and is that included in the standard plan or gated behind a higher tier?
Connected my Postgres and asked it to show weekly active users by plan and it just built the chart in seconds. Way easier than setting up another dashboard tool from scratch.
Connected my Postgres and asked for a chart of weekly active users, and it nailed it on the first try without me touching SQL. The natural language piece feels surprisingly smooth compared to other BI tools I've poked at.
Curious how this handles complex joins across multiple tables when you ask in natural language, does it figure out the relationships on its own or do you need to set up the schema first?
Love that the AI actually generates the chart, not just suggests it. Most tools here give you queries you still have to wrangle yourself, so this feels like a real step forward for non-technical folks on the team.
Hooked up our Postgres and asked it to chart weekly churn by plan, had a clean visualization in seconds. The natural language piece actually understands follow-ups like "now split it by region" without losing context.
The natural language to chart flow feels really polished, you can just describe what you want and it actually nails the visualization without weird defaults. Nice execution on something that's easy to overpromise and underdeliver on.
how does it handle messy or unstructured data sources, like CSVs with inconsistent columns? curious if the AI can clean things up on the fly or if you still need to prep the data beforehand.
How does it actually figure out which tables and columns to pull from when you ask in plain English?
Connected a sample Postgres database and asked for a chart of weekly active users by plan tier. It built the visualization in about 10 seconds and the query it generated looked reasonable. The natural language to chart flow feels surprisingly smooth.