Looking for quick help on a technical bug or limitation?
Opening a support chat is the fastest way to get a direct answer.
(Chat widget is in bottom left corner)
The community is best used for:
• discovering tips and tricks
• exploring how others solved similar project challenges
• sharing feedback and feature ideas
Delete this text and write your post below ![]()
Hi WeWeb team,
We’re building a production SaaS using WeWeb, Xano, and the Xano Auth plugin under Settings → Plugins.
Our authentication is working correctly:
-
Login:
/auth/login -
Current user:
/auth/me -
Sessions persist after browser refresh.
-
An app-level workflow runs On app load (before fetching collections), calls Xano Auth → Fetch User, and restores our global
currentUservariable. -
Xano endpoints enforce authentication and user ownership.
The issue:
On our Listing Audit page, we changed Private access → Authenticated users.
When an authenticated user refreshes the page in Preview, everything works.
However, when an unauthenticated visitor opens Listing Audit in Preview, the page does not redirect to Login. It remains on Listing Audit without account data.
Our questions:
-
Does Private access → Authenticated users automatically redirect unauthenticated visitors, or does it only restrict access?
-
Where is the unauthorized-user redirect configured in the current Xano Auth plugin interface?
-
Does this private-access behavior differ between WeWeb Preview and published production?
-
Does Private access use the Xano Auth plugin’s authenticated state independently of a custom global
currentUservariable? -
Can an app-level On app load (before fetching collections) workflow restore authentication before private-page access is evaluated?
We want to implement this correctly without replacing our working Xano Auth plugin or disrupting production login and billing.
Could you provide the recommended configuration for the current WeWeb editor?
Thank you!