It's weird that a user cannot INSERT a new record if it does not satisfy my SELECT policy! I don't know what went wrong, need someone to check it out if you've been working with policies a lot

sql
ALTER TABLE conversations ENABLE ROW LEVEL SECURITY;

DROP POLICY IF EXISTS "Allow read access only to involved participants" ON public.conversations;

CREATE POLICY "Allow read access only to involved participants" 
ON public.conversations 
FOR SELECT USING ( 
  auth.uid() IN (
    SELECT user_id 
    FROM conversation_participants 
    WHERE conversation_id = id
  ) 
);

DROP POLICY IF EXISTS "Allow create access to conversations" ON public.conversations;

CREATE POLICY "Allow create access to conversations"
ON public.conversations
FOR INSERT WITH CHECK ( true );

DROP POLICY IF EXISTS "Allow update access to conversations" ON public.conversations;

CREATE POLICY "Allow update access to conversations"
ON public.conversations
FOR UPDATE WITH CHECK ( true );

DROP POLICY IF EXISTS "Allow delete access to conversations" ON public.conversations;

CREATE POLICY "Allow delete access to conversations"
ON public.conversations
FOR DELETE USING ( true );

Can you run just this query inside of the SQL editor and make sure the results are correct first

sql
SELECT user_id 
    FROM conversation_participants 
    WHERE conversation_id = id

Ok I am going to try that @User

So your policies above should be working unless there is a delay in when a new participant is added to when the select policy get read

Oh wow.. Hmmm

That shouldn't happen, but thats the only logic reason I can think of

In my query, I create a record for a conversation, then right after it I will create records for conversation_participants But it's always failing when I attempt to create a new record for a conversation with that policy

I just read this in the docs and think you should try it

By default, every time you run insert(), the client library will make a select to return the full record. This is convenient, but it can also cause problems if your Policies are not configured to allow the select operation. If you are using Row Level Security and you are encountering problems, try setting the returning param to minimal.

Good find! Thanks for looking for this man I might have to think of another solution or policy