# Supabase - Authentication roles are not available in your current plan **URL:** \ **Category:** Ask us anything\ **Created:** [July 15, 2024, 2:33pm UTC](https://community.weweb.io/t/supabase-authentication-roles-are-not-available-in-your-current-plan/9736 "2024-07-15T14:33:31Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mdi](https://avatars.discourse-cdn.com/v4/letter/m/5daacb/32.png) [@mdi](https://community.weweb.io/u/mdi)\ **Post date:** [July 15, 2024, 2:33pm UTC](https://community.weweb.io/t/supabase-authentication-roles-are-not-available-in-your-current-plan/9736/1 "2024-07-15T14:33:31Z")
I have been with Weweb for a month or so and have been on the Starter Plan. I didn’t notice that auth is not included, so I activated the supa auth plugin and built a few pages for users to offer some CRUD. When ready, I hit publish and receive the mssg: > Authentication roles are not available in your current plan. Disappointment… Change of plans… - Removed the auth from the project - Removed pages using anything about supa auth Nope… cannot publish… still there: > Authentication roles are not available in your current plan. Already been through similar threads. No obvious solution was there for me. Upgrading is not really an option for me at this point. Any ideas? ---
**Author:** ![Corner](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@Corner](https://community.weweb.io/u/Corner)\ **Post date:** [July 15, 2024, 3:19pm UTC](https://community.weweb.io/t/supabase-authentication-roles-are-not-available-in-your-current-plan/9736/2 "2024-07-15T15:19:36Z")
I didn’t know that, thanks for sharing it. Can’t you “just” upgrade your Supabase plan ? ---
**Author:** ![Alexis](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/alexis/32/13248_2.png) [@Alexis](https://community.weweb.io/u/Alexis)\ **Post date:** [July 15, 2024, 3:25pm UTC](https://community.weweb.io/t/supabase-authentication-roles-are-not-available-in-your-current-plan/9736/3 "2024-07-15T15:25:23Z")
Hi, you can use Auth plugins with any plan. But for now you cannot use our built-in roles system to restrict the access to a page without an higher plan yes. That said, since the summer update you can easily do it yourself through a workflow on page load, you can check the roles of your user and redirect him to another page if he doesn’t has the permission to access it. Your issue could be you still have one page with a role access rule, check if all your pages are public or authenticated, some may be bugged, you can try to turn them public and private again so it will clear possible invisible roles. If you still have the issue please open a ticket on [support.weweb.io](http://support.weweb.io) and we will help you 🙂 ---
**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\ **Post date:** [July 15, 2024, 3:44pm UTC](https://community.weweb.io/t/supabase-authentication-roles-are-not-available-in-your-current-plan/9736/4 "2024-07-15T15:44:37Z")
> [@Alexis](#): > > That said, since the summer updat What has changed regarding this? ---
**Author:** ![Alexis](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/alexis/32/13248_2.png) [@Alexis](https://community.weweb.io/u/Alexis)\ **Post date:** [July 15, 2024, 3:54pm UTC](https://community.weweb.io/t/supabase-authentication-roles-are-not-available-in-your-current-plan/9736/5 "2024-07-15T15:54:59Z")
Previously the roles based system was implemented in the backend side, now it’s on the front end, so doing it manually through workflow on page load is closer than before in term of flow, it’s what I meant. (unrelated: Happy birthday 😁) ---
**Author:** ![mdi](https://avatars.discourse-cdn.com/v4/letter/m/5daacb/32.png) [@mdi](https://community.weweb.io/u/mdi)\ **Post date:** [July 15, 2024, 4:26pm UTC](https://community.weweb.io/t/supabase-authentication-roles-are-not-available-in-your-current-plan/9736/6 "2024-07-15T16:26:50Z")
> [@Alexis](#): > > me may be bugged, yo You’re right. It looks like the page is bugged. Even when I define access as public, this won’t change. It is still marked as private; check the screenshot. ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/0/0eb26a864b329adca1447591b9408f3a882f402a.png) I even tried to re-install the Supa auth plugin, but it won’t work. I will open a support request. Cheers ---
**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\ **Post date:** [July 15, 2024, 4:52pm UTC](https://community.weweb.io/t/supabase-authentication-roles-are-not-available-in-your-current-plan/9736/7 "2024-07-15T16:52:53Z")
Thanks for the wishes! 🙏🏻 So it’s at the router level?