<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Try the Door</title>
    <description>The latest articles on DEV Community by Try the Door (@trythedoor).</description>
    <link>https://dev.to/trythedoor</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4242260%2F1d1d30a9-b653-4d56-b404-befbde5e8f59.png</url>
      <title>DEV Community: Try the Door</title>
      <link>https://dev.to/trythedoor</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/trythedoor"/>
    <language>en</language>
    <item>
      <title>The two-account test: one check to run on your Supabase app before launch</title>
      <dc:creator>Try the Door</dc:creator>
      <pubDate>Sat, 14 Nov 2026 04:53:38 +0000</pubDate>
      <link>https://dev.to/trythedoor/the-two-account-test-one-check-to-run-on-your-supabase-app-before-launch-3apf</link>
      <guid>https://dev.to/trythedoor/the-two-account-test-one-check-to-run-on-your-supabase-app-before-launch-3apf</guid>
      <description>&lt;p&gt;This post was drafted with AI assistance. It comes from Try the Door, which sells kits for builders shipping apps made with AI tools. The whole check is below, free; one paragraph at the end names the kits.&lt;/p&gt;

&lt;p&gt;If you built your app with Cursor, Lovable, Bolt or Replit on Supabase, run this before launch: can one signed-in user read another user's rows?&lt;/p&gt;

&lt;p&gt;It hides for a simple reason. While you build, you are signed in as yourself. Every query returns your data, and that looks right. But "I can see my rows" and "only I can see my rows" are two different claims, and the happy path only tests the first.&lt;/p&gt;

&lt;p&gt;Run this only on an app you own or are authorized to test.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1. Make two accounts
&lt;/h2&gt;

&lt;p&gt;In your own app, make two accounts, A and B. A second browser or a private window keeps both signed in.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2. Give A a real row first
&lt;/h2&gt;

&lt;p&gt;Sign in as A and create something real: a note, an order, a profile field. An empty result also comes back when A owns nothing, so an empty result alone proves nothing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3. As B, reach for A's data
&lt;/h2&gt;

&lt;p&gt;Sign in as B and try each road to A's row:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;open A's record by its URL;&lt;/li&gt;
&lt;li&gt;look at any list or feed that could include it;&lt;/li&gt;
&lt;li&gt;in your browser's network tab, repeat a request that loaded A's row, with A's id in it.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 4. Read the result
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Pass: with A's row in place, B gets nothing of A's.&lt;/li&gt;
&lt;li&gt;Fail: B sees A's row. Your row-level rules are not per-user on that table.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why apps ship failing
&lt;/h2&gt;

&lt;p&gt;Two common causes: row-level security (RLS) is off on the table, or a policy says, in effect, "any signed-in user can read". Both look fine when you only ever test as yourself.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fix on Supabase
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Turn RLS on for each table that holds user data.&lt;/li&gt;
&lt;li&gt;Add policies where the owner column equals auth.uid().&lt;/li&gt;
&lt;li&gt;Re-test with A's row still in place. If B still sees it, check that the owner column is set on insert, and that it is the column your policy compares.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  A Firebase note
&lt;/h2&gt;

&lt;p&gt;Firestore rules do the same scoping job, and the same two-account test applies.&lt;/p&gt;

&lt;h2&gt;
  
  
  Your turn
&lt;/h2&gt;

&lt;p&gt;What do you check before you launch? Tell us in the comments.&lt;/p&gt;




&lt;p&gt;Try the Door sells two kits for this. Lock Down ($19, &lt;a href="https://oebose.gumroad.com/l/fnribw" rel="noopener noreferrer"&gt;https://oebose.gumroad.com/l/fnribw&lt;/a&gt;) is a pre-launch test you run yourself on your own Supabase app. The RLS Policy Pack ($15, &lt;a href="https://oebose.gumroad.com/l/xwoyrm" rel="noopener noreferrer"&gt;https://oebose.gumroad.com/l/xwoyrm&lt;/a&gt;) is copy-paste SQL policies for 12 table shapes; its 188 pgTAP checks all passed in a lab re-run on 2026-11-13, on PostgreSQL 16 with the pack's stand-in for Supabase, not on a live Supabase project. Run only on apps you own or are authorized to test. 30-day refunds. Not affiliated with Supabase.&lt;/p&gt;

</description>
      <category>supabase</category>
      <category>postgres</category>
      <category>security</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
