Security

·

6 min read

Row-level security without a second copy

Row-level security without a second copy

Row-level security without a second copy

Each person sees only the rows they should, enforced in your warehouse. No extracts, no copies to keep in sync.

Each person sees only the rows they should, enforced in your warehouse. No extracts, no copies to keep in sync.

Tomás Ferreira

Security Engineer

The usual way to limit what someone sees is to give them their own extract. It works until there are forty extracts and nobody knows which one feeds which dashboard.

Rules where the data lives

Tessel passes each person’s identity to your warehouse and applies row rules there. A sales lead in Lisbon sees Iberian accounts; the finance team sees everything. Nothing is copied out.

Rules from your identity provider

Groups come from Okta, Google or Microsoft Entra through SCIM. When someone changes teams, their access changes with the group, not with a ticket.

Every query, export and shared link is written to the audit log with the rules that applied to it.

Ask your first question today.

Connect a warehouse in ten minutes. Free for up to three seats.

Ask your first question today.

Connect a warehouse in ten minutes. Free for up to three seats.

Ask your first question today.

Connect a warehouse in ten minutes. Free for up to three seats.

Create a free website with Framer, the website builder loved by startups, designers and agencies.