Authentication plugins for Payload CMS 76

Add OAuth and SSO sign-in, two-factor codes and passkeys to Payload CMS. Other plugins connect Better Auth or keep roles in the database.

Birth month and year check at sign-up that flags minors by country and region

Lets one Payload admin panel manage content for many separate tenants

Linked accounts and role hats, with a second factor before switching to a sensitive role

Sells digital products with signed download links that expire and stop on refund

Adds passkey sign-in and passkey management to the Payload login and account screens

Lets AI assistants read and edit Payload content over MCP with scoped API keys

Lets guardians suggest or approve changes to a minor's records and requests

Finds access control and security holes in a Payload site, with severity-ranked alerts

Logs Payload users in from cookies set by an external SSO system

Adds OpenID Connect sign-in to the admin, with roles synced from provider groups

Sign-up with open, approval, invite-only or closed modes, switchable in the admin

Per-site role ladders with add-on and platform roles for multi-tenant access checks

Adds two-step sign-in to Payload with authenticator, email and recovery codes

Lets admins sign in as another user to see exactly what that user sees

Lets administrators switch to any user account from the admin panel without a password

Adds passkey sign-in to the admin login alongside email and password

WordPress-style back-office for Payload with a block editor, media library and OIDC sign-in

Role-based access grants compiled into Payload collection and global access functions

Gives each auth collection its own session cookie so admin and frontend logins coexist

Signs Payload users in through Zitadel with OIDC and API bearer tokens

About these packages

Payload already handles email and password login for any collection with auth enabled. It also issues JWT cookies and optional API keys. Auth plugins add the rest through the plugins array. Some connect outside identity providers over OAuth or SAML. Others add a second login factor, passkeys or roles for Payload's access control.

What these plugins cover

  • OAuth2 and Auth.js sign-in with Google, GitHub, Apple and other providers
  • Better Auth integrations, including Payload Auth for the admin login
  • TOTP two-factor codes and passkey sign-in
  • Single sign-on over OpenID Connect and SAML 2.0
  • RBAC, Gatekeeper and Authorization for roles and collection permissions
  • Impersonation and Masquerade for signing in as another user

Choosing an auth plugin

First decide whether Payload stays in charge of user accounts. If it does, OAuth2, Auth.js and TOTP add sign-in methods to your existing auth collection. If your app already uses Better Auth, Payload Auth replaces the admin login and shares one session with the app. For roles, you can write access functions yourself, because Payload supports them without a plugin. A plugin such as RBAC helps when roles must live in the database and change without a deploy. These packages guard your login, so check the last release and the supported Payload version on each card.

Frequently asked questions

How do I add SSO to Payload CMS?

Install a plugin that speaks your identity provider's protocol. The package named Auth supports OAuth, OpenID Connect and SAML 2.0 for Payload logins. OAuth2 connects providers such as Google and Apple.

How do I add two-factor authentication to Payload?

The TOTP plugin adds authenticator app codes as a second step to the login of an auth collection. The Passkey plugin lets users sign in with passkeys and manage them on the login and account screens.

Does Payload CMS have role-based access control?

Payload has access control functions on collections, globals and fields. Many projects keep a roles field on the users collection and check it in those functions. The RBAC plugin stores roles in the database with a permission matrix per collection, so you can change permissions without a deploy.