Supabase returns an empty list after logging in — check RLS
No records on a valid query need not mean an empty table. Row Level Security policy can hide poems from a specific user. Disabling RLS is not a permission amendment.
Step by step
1. Check that the query uses the current session and which user ID goes to the API. Compare request logged in and not logged on test data.
2 . Open table policies and analyze SELECT. The condition should reflect the owner or membership of the organization, not the fact that he has an account.
3 . Verify the type and value of the column identifying the owner. If you compare auth.uid() to another business identifier, the policy may never fit.
4 . Also check the tables combined in the query. Lack of access to the relationship can change the result or return the error depending on the way you connect.
5 . Test two organizations and user without permission. The service role key is stored only on the server; inserting it into the frontend bypasses the security instead of fixing the policy.
How to check whether the amendment works
The authorized user sees his records, and the other does not see others. The positive test without a refusal test is insufficient. Keep checking membership also in write operations.