All Features/Protect/Verified Multi-Tenant Isolation

Verified Multi-Tenant Isolation

Someone on the call asks whether another agency on this tool could ever see their unpublished post. Everyone turns to look at you.

Plans
  • Pro included
  • Agency included
Tested on a real database

What It Does

Every table has row rules switched on in Postgres. When you’re signed in, the database itself decides which rows you can see, row by row, whatever the screen asked for.

Reading and writing are checked separately, so a Viewer on your team can’t change anything either.

How It Works

1

Asked Every Time

A row belongs to one account. Each read and each write is checked against it.

2

Tried With Two People

Our database tests replay every change on a real Postgres, sign in as two people and a signed-out visitor, and check what each can see and write.

3

Checked Where the Rules Stop

Nightly jobs, review links, and the free tools run with no one signed in. That connection skips row rules, so each path checks whose work it is first.

Read How the Rules Are BuiltThe tests, and the one place they aren’t the only thing standing

Worth Knowing

Verified by whomBy our own tests, the ones described here. It doesn’t mean an outside firm has audited us.
Inside your accountThis separates agencies. Everyone on your team sees the same clients, so use roles for who can change what.
Keys to your toolsA client’s Slack address and webhook details are stored sealed with AES-256-GCM, under a key of their own.

Your Clients Stay in Your Drawer

Free for 14 daysNo credit card needed