# Get row level sec' error when uploading images to supabase from weweb

**URL:** <https://community.weweb.io/t/get-row-level-sec-error-when-uploading-images-to-supabase-from-weweb/14062>\
**Category:** Ask us anything\
**Tags:** workflows, authentication, supabase, weweb\
**Created:** [October 22, 2024, 4:03am UTC](https://community.weweb.io/t/get-row-level-sec-error-when-uploading-images-to-supabase-from-weweb/14062 "2024-10-22T04:03:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![metalsteve81](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@metalsteve81](https://community.weweb.io/u/metalsteve81)\
**Post date:** [October 22, 2024, 4:03am UTC](https://community.weweb.io/t/get-row-level-sec-error-when-uploading-images-to-supabase-from-weweb/14062/1 "2024-10-22T04:03:43Z")

</div>

following this doc [https://docs.weweb.io/workflows/actions/supabase/storage-upload-file.html](https://docs.weweb.io/workflows/actions/supabase/storage-upload-file.html)

but when I test my workflow I get an error message:  
“new row violates row-level security policy”  
cause  
statusCode: “403”  
error: “Unauthorized”  
message: “new row violates row-level security policy”

But I did the policy just like in the docs so I am not sure what I am doing wrong.

is the doc out of date or is it me?

 ![rowlev2](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/e/e70ffdeeb98b445ffcac4d98ffca1984e1216fc0.png)  
 ![rowlev1](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/5/589161c01c108a38c75b66fb6ac2292a8d0e7609.png)

---

<div class="post-metadata">

**Author:** ![metalsteve81](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@metalsteve81](https://community.weweb.io/u/metalsteve81)\
**Post date:** [October 23, 2024, 10:13pm UTC](https://community.weweb.io/t/get-row-level-sec-error-when-uploading-images-to-supabase-from-weweb/14062/2 "2024-10-23T22:13:56Z")

</div>

On the supabase upload I had “upsert” switched on.  
That was the problem. Supabase needs a different policy if thats on.  
Switched it off and now it works
