Permissions and Role feature

It’s a really huge step between the starter and scale plan to get access the role and permission feature.

Every software these day include role and permission and I don’t really understand why not to make it available for a lower tier plan or even as an extra payable feature.

Is there any plan to make a change in your price structure pretty soon ?

Do you really need permissions and roles feature ?

If you already have your data protected you can use workflow on page load to restrict access to private page, based on permissions and roles of your loaded users.

This feature is really required when you have static page with sensitive data inside, and you dont want the page to be returned so we perform server side check. If your data are dynamic and protected behind an authentication system (Xano Auth, Supabase Auth, JWT, …) there is no real security risk not using this permission and role management feature.

1 Like

Yes, it’s something we’re looking into but:

  1. we don’t have an exact timeline yet, and
  2. we haven’t yet decided how the roles and permissions feature will be handled.

In the meantime, as @Alexis mentioned, if you are using dynamic data, you can build a secure web-app with roles and permissions without using our private page feature because the security happens at backend level in any case. The roles and permissions feature you have in WeWeb is more designed to help you with the UX of private pages.

You can learn more about this here in the WeWeb Academy level 2 course handbook.

1 Like

Great thanks you very much for your help.

Hi Joyce - and others,

I have a similar question, but I’m not sure if I understand the explanation.

Can you please clarify if the “Starter” license has the ability of conditional hiding of elements on webpages? This of course is for UX - not security.

Regards,
Thijs

Yes it does :slight_smile: