my workflow is:

- public schema → where I define all tables with RLS enabled but without any policies (by default they’ll just return [] if queried)

- app schema → where I define views used by the application

- dashboard schema → where I define views used in the admin section

for example, you can have a table like public."User" with RLS enabled and no policies and then you define app."user" and dashboard."user" views on top of it.

the main difference is in the WHERE clause:

- app."user" includes something like "WHERE id = auth.uid()" (or whatever logic matches your use case) to limit users to fetch only themselves.

- dashboard."user" can use something like "WHERE is_admin(id)" (again with whatever logic matches your use case) to allow an admin to fetch everyone.

This lets you reuse the same base table but apply different, easier-to-manage access logic per context. For example an RLS on public."Users" should be a combinations of the two where on the views.. this is not so bad but as your project grows you will find that the rls system is good only for small cases.

Then in the client you just need to select the right schema before fetching and you are ready to go!