Security & Governance

Everything is yours until you share it. Your data, your projects, your analyses are private by default. No admin, no central team, no governance committee sees your work unless you choose to share it.

At the same time, anyone and everyone can be data-driven. Data analysis shouldn’t require SQL fluency or a weeks-long wait for the data team. When a marketing manager has a question about campaign performance, the answer should be minutes away.

These two principles aren’t in conflict — they work together. Privacy enables trust. Trust enables sharing. Sharing enables organization-wide data literacy.

Start simple, add layers

Querri’s security is progressive. You opt in to each layer as your needs grow:

1. Just you and your data — everything is private by default
2. Share with your team — sharing controls who can access your projects, dashboards, and data
3. Filter what they see — access policies control which rows and columns each person sees within shared data
4. Your team grows — groups make sharing and policy management easier
5. Departments need boundaries — workspaces create governance perimeters with view/edit controls
6. External tools need access — API keys provide governed, auditable data access

You never have to use more security than you need. A team of three doesn’t need the same governance as a 500-person organization — and Querri doesn’t force it.

How it works: natural filtering

Think of Querri’s security like a lowcountry waterway system. Salt marshes don’t block water — they filter it naturally as it flows. Sediment settles, salinity adjusts, nutrients are processed. In the same way, Querri’s access policies don’t block data — they filter it naturally as it flows to each person.

• Marshes are your access policies — filtering data automatically as it reaches each user
• Barrier islands are workspaces — hard boundaries between organizational domains
• Controlled outlets are API keys — deliberate, auditable channels to the outside world

The key insight: security should be structural, not administrative. The right data reaches the right people because the system is designed that way — not because someone remembered to check a box.

What’s in this section

• Sharing — The foundation: who can access your data
• Access Policies — Control what data each person sees
  • Row-Level Security — Filter which rows each user can see
  • Column Security — Hide or mask sensitive columns
• Groups — Assign sharing and policies to teams instead of individuals
• API Keys — Give external tools governed access to your data
• Dashboard Security — How shared dashboards respect each viewer’s access
• Filters — Admin-defined table filters and interactive dashboard filters
• Workspaces — Governance boundaries between departments
• Audit Log — Track every security-relevant action
• Admin Controls — Organization-wide feature flags and settings