Roles and access rules for Payload CMS 55

Plugins that write Payload access functions for you, from role matrices to tenant scoping, and features that check a user's permissions before they act.

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

Customer product reviews with verified purchase badges and moderated star ratings

Campaign link builder with live UTM URLs, presets and permission-checked CSV exports

Stores DNA reference panels and reviewed sample results in Payload collections

Pedigree fields, relatives and family-tree views for Payload collections

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

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

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

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

Keeps a docs page for every feature your site lists, with review and leak checks

Reads barcodes and QR codes by phone camera or USB scanner, answering by who is signed in

Gated step-by-step flows with Yes-to-continue questions and server-checked answers

Runs AI agents in the Payload admin that read and write content through access-controlled tools

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

Threaded messages on any Payload document with channels, mentions and unread state

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

Adds TOTP two-factor sign-in codes to a Payload auth collection

About these packages

Payload checks access with functions on each collection, global and field, and you can write those by hand with no plugin at all. The plugins here generate them for you in one of three ways:

  • A role matrix stored in the database and edited in the admin: the RBAC plugins, Access Control, Auth RBAC and RBAC Permissions UI
  • Rules kept in code: Gatekeeper with wildcard permissions, Zedkit Access with grants declared as data, Simple RBAC with an ordered list of roles
  • Scoping by tenant or attribute: Multi Tenant and Kreatika Multi-Tenant per tenant, ABAC by user attributes, Dynamic RBAC with row-level conditions

The tag also marks features that respect permissions on their own. AI Admin reads and edits content only within the signed-in user's permissions, Menu Plugin hides items per visitor, Admin Alerts targets an audience, and Ecommerce Digital Download releases files after purchase.

Supabase RLS works a layer lower and turns row-level security back on for Supabase tables after Payload pushes a schema. Sign-in methods are under the authentication tag, and the auth category lists both kinds.