WBert WBert
Login Start free
Feature

Authentication & Roles

Back to home
Authentication Auth Providers
EmailPassword, confirmation and reset flows
Enabled
G
GoogleOAuth client ID, secret and callback URL
Enabled
AppleService ID, Team ID, Key ID and private key
Disabled
GGoogle provider
client-id.apps.googleusercontent.com
https://wbert.com/account/oauth/callback
OAuth Authentication

Authentication that connects users, organizations and client applications.

WBert centralizes sign-in providers, user sessions and organization creation, so your client application can use secure authentication without rebuilding the same backend flow every time.

Email sign-in Google OAuth Apple OAuth User sessions Organization onboarding

From client sign-in to a secured backend session

The client starts the login flow, the provider verifies identity, and WBert creates or reuses the platform account. New users can automatically receive a Free organization, while existing users continue with their current organization and plan.

  • One login entry point for web clients, mobile clients and internal tools.
  • OAuth users are matched by email and provider identity.
  • New sign-ups can create an account, organization and Free subscription automatically.
ClientWeb / Mobile AppStarts login or register
OAuthProviderGoogle, Apple or email
WBertAccount LayerUser, session and organization
GatewaySecured APIsPermissions and roles
OrgOrganizationPlan, limits and owner
JWTSessionUsed by endpoints

Configuration stays inside Special Admin

Provider settings are managed from the administration area, not hardcoded in the client. You can enable or disable Google and Apple login, configure callback URLs, and hide disabled providers from login and registration pages.

  • Store Google client ID and client secret from one controlled screen.
  • Configure Apple Service ID, Team ID, Key ID and private key.
  • Show only enabled providers to public users.
Google Enabled OAuth web sign-in using configured client credentials.
Apple Optional Apple sign-in using service ID and private key configuration.
Email Always available Email/password registration, reset and confirmation templates.

Authentication is connected to permissions and backend access

A successful sign-in is only the beginning. WBert keeps the user linked to an organization, then the gateway and API endpoints can apply roles, permissions, plan limits and security checks before backend actions run.

  • User identity and organization context are available to endpoints.
  • Roles and ACL checks can protect database operations and business logic.
  • Special Admin remains unrestricted while organization users follow permissions and plan limits.
UserEmail or OAuth identity
OrganizationOwner, plan and limits
RolesAdmin, user and application permissions
EndpointsAllowed API actions
BackendDatabase and process execution
Upcoming providers

More sign-in providers in future releases.

WBert starts with the essential providers, but the authentication area is designed to grow. Future releases can include the most used providers for business and developer workflows.

Microsoft GitHub LinkedIn Discord Enterprise SSO SAML / OIDC

Authentication becomes part of the backend platform, not a separate rebuild for each client.

With provider configuration, user sessions, organization onboarding and endpoint permissions in one place, WBert lets the client focus on the user experience while the backend controls identity and access.