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.

Add a comment

Replies

Best

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.

 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.

Pulled it up to poke around and the natural language chart builder actually understood my messy request on the first try, which surprised me. Setup to connected data was quick and the dashboard looked clean without any fiddling.

 awesome to hear, let me know if you have any questions getting started!

Connected my postgres database and asked for a weekly active users chart - got a clean visualization in like 30 seconds without touching any SQL. The natural language piece actually works better than I expected.

How does the AI handle more complex joins across multiple data sources, and is that included in the base plan or does it require a higher tier?

 all plans include our AI data analyst with its full capabilities including being able to do complex joins and analysis.

The bit that decides a rollout for me is deprovisioning latency: when someone leaves or switches teams in the directory, does Basedash cut their access on the next SCIM sync cycle, or is there a near-real-time path? For a team standing up dashboards on live customer data, the gap between 'left the company' and 'can still open the dashboard' is the whole risk. Also curious whether group-to-role mapping is 1:1 or if you can express nested/combined groups.

 it's near-real-time on our end. As soon as your IdP pushes the membership change to Basedash we remove their access immediately so they can no longer read dashboards or ask questions to the AI.

That makes sense, so the real-world latency lives entirely on the IdP's push cadence rather than anything on your side. The edge case I'd want to confirm: when access comes from a nested/group membership and someone is removed from a parent group rather than deprovisioned directly, does that propagate and revoke as cleanly, or does it depend on the IdP flattening group changes into an explicit SCIM update?

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.

connected my postgres db and asked it to chart weekly active users and the chart actually matched what i'd write by hand. the natural language piece feels less gimmicky than i expected.

how does the pricing scale as the dataset grows, and are there any limits on the number of rows or sources you can connect before the AI starts getting sluggish on the queries?

I really like how Basedash turns a plain sentence into a working chart, that no-SQL magic trick feels impressively smooth and actually useful.