---
title: "Comment by Mohan on \"How to Check if Supabase RLS Is Enabled (and Actually Working)\" | Hashnode"
description: "Step 6 is the one I'd tell every solo builder to actually do. I run a React + Supabase app where the browser talks to Postgres directly, and the two-account tes"
url: "https://hashnode.com/posts/how-to-check-if-supabase-rls-is-enabled-and-actually-working/6af3e2b0db88ad0285e076f2/comment/6af593e1e8f8c57730561408"
---

[Discussion](https://hashnode.com/posts/how-to-check-if-supabase-rls-is-enabled-and-actually-working/6af3e2b0db88ad0285e076f2)

Comment [How to Check if Supabase RLS Is Enabled (and Actually Working)](https://hashnode.com/posts/how-to-check-if-supabase-rls-is-enabled-and-actually-working/6af3e2b0db88ad0285e076f2)

[Mohan](https://hashnode.com/@resumeorbitz)

[6d ago](https://hashnode.com/posts/how-to-check-if-supabase-rls-is-enabled-and-actually-working/6af3e2b0db88ad0285e076f2/comment/6af593e1e8f8c57730561408)

Step 6 is the one I'd tell every solo builder to actually do. I run a React + Supabase app where the browser talks to Postgres directly, and the two-account test caught more than staring at policies ever did. The point about UPDATE policies needing WITH CHECK is easy to miss too. Without it, a user can reassign a row to someone else even though USING looks fine. Thanks for flagging the October 30 grants change, I hadn't caught that yet.

[VibeVigil](https://hashnode.com/@vibevigil)

[5d ago](https://hashnode.com/posts/how-to-check-if-supabase-rls-is-enabled-and-actually-working/6af3e2b0db88ad0285e076f2/comment/6af593e1e8f8c57730561408#reply-6af6944e7b6f2c603b94df49)

Glad the two-account test helped. That's the check that still catches gaps after the policies look fine on paper. The WITH CHECK detail and the Oct 30 grants change are easy to miss when you're shipping solo. Appreciate you sharing what showed up in your app.
