@bison-lab/payload-core 3.13.0 → 3.14.0

package/README.md

@@ -261,10 +261,13 @@ has its accessible name. Then `payload migrate:create`.
 ## Roles
 
 Settings → Roles is an Admin-editable array. Rank is drag-to-reorder.
-Ticks are Content, Brand, Publish, and Users. Defaults ship in the
-package (Brand on Designer only; Admin + Designer both store; Developer
-is exclusive). A site may pass `extras` into `createRoles` — each extra
-is a slug, a display label, and default ticks — and an Admin can add
+Ticks are the catalogue rows released on Features. Developer is
+implicit — every catalogue feature, including ones not released. That
+row is visible only to a Developer, with every tick on and locked.
+Defaults ship in the package (Theme
+screens on Designer; Designer also has Users and Roles; Admin + Designer
+both store). A site may pass `extras` into `createRoles` — each extra
+is a slug, a display label, and default `grants` — and an Admin can add
 further custom rows and edit any row’s name. Seed slugs stay read-only.
 `canManageBrand` and the other predicates read the saved Global and fall
 back to that seed (plus extras). The package never writes `developer`
@@ -272,26 +275,30 @@ onto a user row.
 
 ```ts
 createRoles({
-  extras: [{ role: "editor", label: "Editor", content: true, brand: false, publish: false, users: false }],
+  extras: [{ role: "editor", label: "Editor", grants: ["content"] }],
 });
 ```
 
 ## Features
 
-Settings → Features is a feature × role grid. The catalogue is code:
-Pages, Media, Theme, Brand assets, Users, Roles, and Features. A site
-may pass `extras` into `createFeatures` — those rows appear only there.
-`canUseFeature(slug)` reads the saved grid and falls back to Content →
-Pages/Media and Brand → Theme/Brand assets when the Global is empty.
-Users, Roles, and Features cannot be turned off; Developer is always
-allowed. `createPages` / `createMedia` use `canUseFeature` for create
-and update (and `admin.hidden`). Theme and brand-assets still take
-`access` arguments — pass `canUseFeature("theme")` /
-`canUseFeature("brand-assets")` as `update`.
+Settings → Features is a Developer-only release valve: one switch per
+catalogue row. Off hides the tick on Roles; Developer still has the
+feature. The catalogue is code, grouped for the UI: Pages (Content,
+Publish, API tab), Media, Theme (Colors, Typography, Appearance,
+Identity, Brand assets), and Users (Users, Roles). Features itself is
+not a row. A site may pass `extras` into `createFeatures` — those rows
+appear only there. `canUseFeature(slug)` is true when the row is
+released and a held role is granted it, or when the login is Developer.
+An empty Global falls back to the catalogue defaults. Group slugs
+`pages` and `theme` are true when any child is. `createPages` /
+`createMedia` use `canUseFeature` for create and update (and
+`admin.hidden`). Theme and brand-assets still take `access` arguments —
+pass `canUseFeature("theme")` / `canUseFeature("brand-assets")` as
+`update`.
 
 ```ts
 createFeatures({
-  extras: [{ slug: "doctors", label: "Doctor search" }],
+  extras: [{ slug: "doctors", label: "Doctor search", group: "users" }],
 });
 ```