Skip to main content

Authentication Setup

Control who can access your deployed chatbot by requiring authentication.

Overview​

By default, chatbots are open to anyone with the link. You can require users to log in before chatting.

Enable Authentication​

  1. Open your chatbot
  2. Go to "Settings" > "Users"
  3. Toggle "Require Authentication"
  4. Click "Save"

Authentication Methods​

MethodDescription
Email/PasswordUsers create accounts with email
GoogleSign in with Google account
MicrosoftSign in with Microsoft account

Configure available methods in "Settings" > "Users" > "Auth Methods".

How It Works​

When authentication is required:

  1. User visits your chatbot URL
  2. Login screen appears
  3. User signs in or creates account
  4. After authentication, chat is accessible
graph LR
    A[Visit Chatbot] --> B{Authenticated?}
    B -->|No| C[Show Login]
    C --> D[User Logs In]
    D --> E[Access Granted]
    B -->|Yes| E
    E --> F[Chat Interface]

Firebase Authentication​

WizChat uses Firebase for authentication. Your chatbot gets:

  • Secure user management
  • Multiple auth providers
  • Session management
  • Password recovery

Session Management​

Session Duration​

Sessions last until:

  • User logs out
  • Browser is closed (optional)
  • Session expires (configurable)

Configure in "Settings" > "Users" > "Session Settings".

Session Tokens​

  • Tokens are securely stored
  • Refresh automatically
  • Can be revoked

Customizing the Login Page​

Customize the login experience:

  1. Go to "Settings" > "Users" > "Login Page"
  2. Add your logo
  3. Customize welcome message
  4. Choose color scheme

Testing Authentication​

  1. Deploy your chatbot
  2. Open in incognito/private window
  3. Verify login screen appears
  4. Test sign-in flow

Troubleshooting​

Users Can't Log In​

  • Verify authentication is properly configured
  • Check Firebase console for errors
  • Ensure email verification settings are correct

Session Issues​

  • Clear browser cookies
  • Check session duration settings
  • Verify token configuration