ABAC

Attribute-based access control that limits Payload documents by user attributes

Community 182 4/wk MIT v0.0.4

Installation

pnpm add @shefing/abac

About

ABAC lets you restrict who can read, change, or delete documents based on attributes of the signed-in user, such as their tenant or role. Rules compile into the query filters Payload already uses, so a user only gets back the documents they are allowed to see, and the database filters them before any results are returned. Tenant and role attributes come built in, and you can define your own for things like region or clearance level. Attributes are carried in the login token, so checking them adds no extra database lookups per request.

Package info

Package name
@shefing/abac
Latest version
0.0.4
Unpacked size
123 kB
License
MIT
Weekly downloads
4
Last publish
May 26, 2026

More from shefing

View profile

Role-based permissions per collection and global, with field-level access

Records who created, edited and published each document in collections and globals

Adds row-based quick filters above collection lists in the admin panel

Adds a Changes button that diffs unsaved or draft edits against the published version

Adds updated-at and updated-by details to the Payload version history view

Similar plugins

More in Auth

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