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

Basedash Access Controls - Control exactly who can access your company data

by•
Basedash now has groups and access controls. Bundle users into groups — internal teams, external clients, leadership — and give each one access to exactly what it needs: data sources, MCP servers, dashboards, chats, and automations. Set a group's AI context so the assistant answers differently per audience, and row-level security applies to every question. The right people see the right data.

Add a comment

Replies

Best
Maker
📌
Hey everyone, Max here from Basedash. Today we're launching groups and access controls. Basedash is a BI tool the whole company touches, so who can see what really matters, and now you control it precisely. You create groups for the way your company actually works: your data team, growth, leadership, an external client, and grant each group access to exactly what it needs: specific data sources, MCP servers, dashboards, chats, and automations. Nothing more. The part I'm most excited about: each group gets its own AI context. Tell the assistant "you're talking to an external client, only reference their own data, keep it non-technical" and every answer for that group follows it automatically. Same product, different behavior per audience, on top of the row-level security that already applies to every question. We run Basedash on this ourselves: our team has full access, and the clients we share dashboards with only ever see their own numbers. Happy to answer anything.
Maker
Very excited for this launch! Group-level context is quickly becoming one of the biggest things you need to offer for team-wide AI deployments so it’s pretty cool for us to be leading the charge here. Give it a spin today and see what results your sales team gets versus, say, engineering based on each group’s respective context. Let us know what you find!

Congrats on the launch. The audience-specific AI context part is interesting.

Most access control tools make me think about who can see which data, but changing how the assistant responds depending on the team seems like the part that could matter a lot once more departments are using the same BI tool.

Do teams usually need that separation from the start, or does it become more important as usage spreads across the company?

Maker

Thanks ! Usually depends on the size of company. Once customers start onboarding multiple teams, they can benefit from group-level AI context. Especially when users have varying levels of technical experience.

Nice launch. The group-level AI context is the part I’d pressure test.

Access says what data someone can see, but the assistant also needs to know what it is allowed to do with that context. Do automations inherit the same group boundary, including MCP server and tool access?

For an admin setting up groups for the first time - how long does it actually take to configure access controls for a team of 50 people or more ?