Authentication
ChatBotKit gives you flexible, secure authentication for the people who manage your AI and the users who interact with it. Sign in to the platform without passwords, with your existing identity provider, or through social login - and authenticate your own end users with the same infrastructure that powers ChatBotKit.
Authentication spans account access, end-user identity, and the credentials your agents use to reach connected services, so you can secure every layer of an AI application from one platform.
What You Can Do
- Sign in without passwords: Passwordless email login removes the need to manage credentials.
- Use social and SSO login: Sign in with GitHub, Google, or a Microsoft account.
- Authenticate your end users: The contact-based NextAuth adapter supports single-account, multi-user authentication, so each of your users signs in as a contact. See Contact-Based Auth.
- Add auth to your app: The NextAuth SDK wires ChatBotKit authentication into your own application.
- Secure agent credentials: Connect and OAuth secrets manage the OAuth tokens and secrets your agents use to call external services.
How It Works
Account login supports passwordless email and social providers, so your team gets in securely without password sprawl. For end users, the contact-based NextAuth adapter maps authenticated users to contacts under a single account, giving you multi-user experiences without provisioning separate accounts for everyone. For agents acting on external systems, OAuth-based credentials are stored securely and injected at call time, so secrets never live in prompts or code.
Getting Started
Choose how your team signs in - passwordless email, GitHub, Google, or Microsoft - from your account settings. To authenticate your own users, add the NextAuth SDK with the contact-based adapter to your application. To let agents act on connected services, set up the credentials through Connect.
Practical Uses
Authentication underpins secure deployments of every size: passwordless and social login for fast, safe team access; contact-based authentication for multi-user products built on a single ChatBotKit account; and managed OAuth credentials so agents can act on external systems without exposing secrets.