Skip to main content
User Authentication lets visitors create an account on your published site and sign in with Sign in with Webstorio — Webstorio’s platform OAuth flow. Signed-in users get a site session scoped to your project. Use it for member areas, order history, signed-in-only App Data writes, and personalized pages. Available on: Growth plan and above.

​
When to use it

​
How sign-in works

Each visitor who signs in becomes a site user in your project. You can view and manage them under Auth → Users in the dashboard.

​
Step 1 — Enable User Authentication

  1. Open your project dashboard.
  2. Go to Features and enable User Authentication.
  3. Open Auth in the project sidebar.

​
Step 2 — Create auth pages

Webstorio scaffolds default sign-in and account pages.
  1. Go to Auth → Settings.
  2. Click Create auth pages (or equivalent scaffold action).
  3. Webstorio adds:
    • Sign-in page — default path /auth/sign-in
    • Account page — profile and sign-out for signed-in visitors
Customize layout and copy in the page editor like any other page.
Ask the AI: “Style the sign-in page to match my brand colors” after scaffolding.

​
Step 3 — Configure auth settings

Under Auth → Settings:
After adding a custom domain, open Auth settings and confirm callback URLs are listed and verified. Add any extra redirect URIs your pages need.

​
Step 4 — Manage site users

Auth → Users lists everyone who has signed in to your site.
  • See email, name, status, and sign-up date
  • Disable users to block sign-in without deleting history
  • Remove users when appropriate
  • Monitor usage against your plan’s site user limit

​
Step 5 — Use sessions on your site

The fastest way to wire up sign-in is to ask the AI builder (see the prompts below). Editing page code yourself? Pages manage sessions with window.webstorio auth methods — start sign-in with signInWithWebstorio, read the visitor with getSession, and end the session with signOut. On sign-in pages, if getSession() already returns a user, redirect them onward instead of showing the button again. → Methods, parameters, and examples: Auth SDK reference

​
Works with other website features

​
Online store

  • Checkout can prefill customer email from getSession()
  • Orders link to the signed-in site user when authentication is enabled
  • My orders pages use getMyOrders() and getMyOrderById()
→ Online store

​
App Data

API presets like Signed-in users (read only) or Public read, signed-in write require an active site session. → App Data

​
Example AI prompts

  • “Add a Sign in button in the header that calls signInWithWebstorio”
  • “Account page showing the current user’s name and email from getSession, with a sign out button”
  • “Protect this page — redirect to /auth/sign-in if getSession returns null”
  • “Checkout page that prefills email from getSession when the user is signed in”

​
Tips

Publish auth pages before linking to them from your header or store checkout.
Use disable instead of delete when you need to block access but keep order or submission history tied to a user.

​
For developers

Page code uses window.webstorio auth methods. → Auth SDK