Basedash is the AI-native Business Intelligence platform that lets you create dashboards and understand your customers using natural language. Connect your data, describe the chart you want, and let AI generate the visualization. No SQL required.
This is the 24th launch from Basedash: AI data analyst. View more
Basedash SCIM
Launching today
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.
Free Options
Launch Team
The place access always rots for us is offboarding, not onboarding. A contractor leaves and three tools still have them active two months later. Does the SCIM here cover clean deprovisioning across downstream apps, or is it mostly about pushing new users out? Curious how it handles the half-connected tools that don't speak SCIM properly.
the SCIM + RBAC/RLS separation is a clean call. a lot of tools conflate identity provisioning with access control and it creates a mess when someone departs mid-project. curious how you handle partial deprovisioning for contractors who are tied to active dashboards, any edge cases there? congrats on #6, 24 launches in is impressive staying power.
the RBAC/RLS-separate-from-org-membership design raises a reconciliation question for me: if someone gets a locally-created custom role or a one-off data-source grant inside Basedash directly (not through their IdP group), does a SCIM deprovisioning event catch that too, or does it only clean up what SCIM itself provisioned? that seams like the gap auditors would actually poke at - permissions that exist outside the synced path.
Connected a postgres db and asked it to show weekly active users segmented by plan tier. The chart it generated was accurate and the breakdown matched what I get in metabase. The natural language editing is surprisingly responsive, it understood when I asked to filter out internal users without me restating the whole query.
Interesting to see a natural language interface paired with enterprise provisioning. It makes me wonder how the learning curve differs for new team members versus seasoned analysts when they first use it.
Basedash: AI data analyst
@voltagegpu we’re building largely for enterprises, but UX and ease of use are a huge priority for us! Doesn’t matter how big your company is, natural language is the easiest way for business users to ask questions and get answers.
The natural language chart builder actually worked on the first try with a messy Postgres schema, which caught me off guard. Wish the dashboard sharing was a bit more polished though.
Basedash: AI data analyst
@hamdisdan2s3o glad to hear! Any specific feedback about how you’d want dashboard sharing to work better? We’re looking to improve it.
@maxmusing @kris_lachance The offboarding path is the part most teams underestimate, that's where access quietly rots. Auto-syncing group and org membership on every change, not just provisioning new users, is the hard part done right. That's exactly what makes "who still has access" answerable. Nice work.
Basedash: AI data analyst
@kris_lachance @nishant_06 thanks, totally agree. We want to make this totally seamless.
@maxmusing Seamless is the right bar. The tell is when "remove them in Okta" just propagates everywhere in seconds and the access audit is always current, so no one has to remember to clean up. Good problem to be nailing.