Skip to content

Setting up Site Security Settings

Understand Wappler Security Providers, provider types, and the shared settings that power login and access control across a project.

Back to Security Provider fundamentals
Setting up Site Security Settings

Understand Wappler Security Providers, provider types, and the shared settings that power login and access control across a project.

Use this bridge to understand Security Providers the way Wappler is structured now: define the provider once in Globals, then reuse it for login, logout, protected API actions, and protected pages.

There are still different provider types for different needs. Single User is the simplest. Static List works for small fixed user sets. Database is the common production path, and that is what Demo Projects HQ uses: a security provider backed by the users table, with passwordVerify enabled and an admin permission mapped from the user’s role.

Treat Demo Projects HQ as the docs-ready reference path: shared provider in Globals, login form on /login, protected main layout, and admin-only routes layered on top.

Start here
Apply it in Demo Projects HQ
Go to