Basedash: AI data analyst
AI-native Business Intelligence Platform
Start new thread

Basedash SCIM - Your org changes. Access keeps up.

by•
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
Maker
📌
Hey everyone, Max here from Basedash. Today we’re launching SCIM provisioning: a way to keep Basedash identity aligned with the directory your company already manages. As companies grow, joiners, team changes, and departures create identity work in every application. SCIM lets those changes flow into Basedash, keeping users, groups, and organization memberships current. A departure deactivates organization membership; resource access remains governed separately through controls such as RBAC and RLS. We built this to make enterprise rollout feel controlled without making identity administration the bottleneck. Happy to answer anything.
Maker
We spend a lot of time talking to enterprise customers, and SCIM is a recurring theme. As teams grow, manually managing users across tools doesn’t scale. Now Basedash automatically stays in sync with your identity provider, so onboarding and offboarding are largely handled for you. Happy to answer any other questions or hear what you’d like to see!

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.

Maker

 glad to hear! Any specific feedback about how you’d want dashboard sharing to work better? We’re looking to improve it.

the split between org membership and resource access via RBAC/RLS is the right seam. most SCIM implementations conflate the two and enterprises pay for it later.

real q: does the audit log preserve who was in the org at the moment a query ran or a dashboard was published? asking because compliance teams increasingly want "this insight was produced by this human on this date under these roles" as a first-class record and most tools reconstruct it after the fact.

Maker

 yup the audit log can trace who took what actions, like asking questions to the AI dat analyst, or creating a dashboard.

   Congrats Max — 24 launches in and you're still shipping the enterprise plumbing most teams put off. Question from the regulated side: I work with companies bidding on U.S. federal contracts, and their auditors never ask "who has access" — they ask "prove who had access on date X, under which role." Are SCIM provisioning/deprovisioning events exportable as audit evidence (API or CSV), or do they live only inside Basedash for now? That detail decides whether a tool survives a FedRAMP/CMMC assessment without a spreadsheet side-quest.

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.

Maker

   thanks, totally agree. We want to make this totally seamless.

 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.

Would love to see a way to save and share prompt templates for common chart types. Our team keeps asking similar questions each week, and being able to save a "weekly revenue by plan" prompt with preset filters would save a lot of time.

Maker

 love it. We built skills and definitions to support this kind of workflow!

Hooked up our Postgres and asked it to chart weekly active users by plan, got a clean visualization back in seconds without touching SQL. Impressed it actually understood the relationships between tables without me hand-holding it.

Maker

 glad to hear! Let me know if you have any other feedback.

One thing I've noticed with enterprise features like SCIM is that the technical implementation is often the easy part compared to getting companies to prioritize identity management before it becomes painful.

Have you found SCIM to be something prospects actively ask for, or is it mostly a capability that helps remove blockers later in the sales process?

Congrats on the launch!

Maker

 it’s a common requirement for bigger enterprises. If they need it they usually let us know 😊

 That makes sense.

It also makes me wonder whether SCIM is less of a feature buyers choose and more of a milestone they eventually reach.

If that's true, the interesting challenge isn't just building SCIM—it's helping customers recognize they're approaching that milestone before it becomes a procurement blocker. That feels like a much harder problem than the implementation itself.

Maker

 yes agreed. I think traditionally this is handled by sales teams but feels like it could be better handled by CS.

 That's an interesting shift.

I have one observation about what happens strategically when a capability moves from Sales to Customer Success that I think is easier to explain than in a Product Hunt thread.

What's the best email to send it to?

How does it handle complex joins across multiple tables when you ask in natural language, does it just guess at the relationships or do you need to define them upfront?

Maker

 the AI builds its own context layer based on your schema to understand relations and context from raw data. Users can also create definitions to teach the AI how to deterministically calculate certain metrics or models.

Connected my postgres db and asked for a chart of weekly active users, got a clean visualization in seconds. The natural language piece feels polished, not just a wrapper.

123
•••
Next
Last