# Role management

**URL:** <https://community.weweb.io/t/role-management/19008>\
**Category:** Ask us anything\
**Tags:** authentication, supabase\
**Created:** [June 29, 2025, 5:48pm UTC](https://community.weweb.io/t/role-management/19008 "2025-06-29T17:48:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Agustin\_Carozo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agustin_carozo/32/13231_2.png) [@Agustin\_Carozo](https://community.weweb.io/u/Agustin_Carozo)\
**Post date:** [June 30, 2025, 2:21pm UTC](https://community.weweb.io/t/role-management/19008/2 "2025-06-30T14:21:08Z")

</div>

Hi Kappa 👋

You need to activate RLS in both tables for it to work.

I went through the same issues when I tried working with roles:

> [@Supabase roles, creating a client portal](https://community.weweb.io/t/supabase-roles-creating-a-client-portal/18531):
>
> Hello everyone waving_hand I just recorded a long video going through how to create a client portal with role base visibility and blocking pages for specific roles like admin and user. Most of the work is based on the docs: [Supabase authentication | Documentation](https://docs.weweb.io/plugins/auth-systems/supabase-auth.html#user-roles-permissions) But there is a lot of troubleshooting that will be super important for those trying to attempt this. Things like: Paying attention to your RLS policies in supabase tables. when creating the new tables: roles and userRoles you can…

---

_[View the full topic](https://community.weweb.io/t/role-management/19008)._