feat: types custom component props

There are cases when a storage plugin is disabled during development and
enabled in production. This will result in import maps that differ
depending on if they're generated during development or production.

In a lot of cases, those import maps are generated during
development-only. During production, we just re-use what was generated
locally. This will cause missing import map entries for those plugins
that are disabled during development.

This PR ensures the import map entries are added regardless of the
enabled state of those plugins. This is necessary for our
generate-templates script to not omit the vercel blob storage import map
entry.

.github/CODEOWNERS

@@ -1,37 +0,0 @@
-# Order matters. The last matching pattern takes precedence.
-
-### Package Exports
-
-**/exports/ @denolfe @jmikrut @DanRibbens
-
-### Packages
-
-/packages/plugin-cloud*/src/ @denolfe @jmikrut @DanRibbens
-/packages/email-*/src/ @denolfe @jmikrut @DanRibbens
-/packages/live-preview*/src/ @jacobsfletch
-/packages/plugin-stripe/src/ @jacobsfletch
-/packages/plugin-multi-tenant/src/ @JarrodMFlesch
-/packages/richtext-*/src/ @AlessioGr
-/packages/next/src/ @jmikrut @jacobsfletch @AlessioGr @JarrodMFlesch
-/packages/ui/src/ @jmikrut @jacobsfletch @AlessioGr @JarrodMFlesch
-/packages/storage-*/src/ @denolfe @jmikrut @DanRibbens
-/packages/create-payload-app/src/ @denolfe @jmikrut @DanRibbens
-/packages/eslint-*/ @denolfe @jmikrut @DanRibbens @AlessioGr
-
-### Templates
-
-/templates/_data/ @denolfe @jmikrut @DanRibbens
-/templates/_template/ @denolfe @jmikrut @DanRibbens
-
-### Build Files
-
-**/tsconfig*.json @denolfe @jmikrut @DanRibbens @AlessioGr
-**/jest.config.js @denolfe @jmikrut @DanRibbens @AlessioGr
-
-### Root
-
-/package.json @denolfe @jmikrut @DanRibbens
-/tools/ @denolfe @jmikrut @DanRibbens
-/.husky/ @denolfe @jmikrut @DanRibbens
-/.vscode/ @denolfe @jmikrut @DanRibbens @AlessioGr
-/.github/ @denolfe @jmikrut @DanRibbens

.github/ISSUE_TEMPLATE/1.bug_report_v3.yml

@@ -57,7 +57,7 @@ body:
   - type: textarea
     attributes:
       label: Environment Info
-      description: Paste output from `pnpm payload info` _or_ Payload, Node.js, and Next.js versions.
+      description: Paste output from `pnpm payload info` _or_ Payload, Node.js, and Next.js versions. Please avoid using "latest"—specific version numbers help us accurately diagnose and resolve issues.
       render: text
       placeholder: |
         Payload:

.github/ISSUE_TEMPLATE/2.design_issue.yml

@@ -20,7 +20,7 @@ body:
   - type: textarea
     attributes:
       label: Environment Info
-      description: Paste output from `pnpm payload info` _or_ Payload, Node.js, and Next.js versions.
+      description: Paste output from `pnpm payload info` _or_ Payload, Node.js, and Next.js versions. Please avoid using "latest"—specific version numbers help us accurately diagnose and resolve issues.
       render: text
       placeholder: |
         Payload:

.github/actions/release-commenter/LICENSE

@@ -0,0 +1,27 @@
+MIT License
+
+Copyright (c) 2020-2025 Cameron Little <cameron@camlittle.com>
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+'Software'), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+---
+
+Modifications made by Payload CMS, Inc. <info@payloadcms.com>, 2025
+Details in README.md

.github/actions/release-commenter/package.json

@@ -4,6 +4,7 @@
   "private": true,
   "description": "GitHub Action to automatically comment on PRs and Issues when a fix is released.",
   "license": "MIT",
+  "author": "Payload <dev@payloadcms.com> (https://payloadcms.com)",
   "main": "dist/index.js",
   "scripts": {
     "build": "pnpm build:typecheck && pnpm build:ncc",

.github/actions/release-commenter/tsconfig.json

@@ -1,6 +1,6 @@
 {
   "compilerOptions": {
-    "target": "ES2022",
+    "target": "es5",
     "lib": ["es2020.string"],
     "noEmit": true,
     "strict": true,

.github/actions/triage/tsconfig.json

@@ -1,6 +1,6 @@
 {
   "compilerOptions": {
-    "target": "ES2022",
+    "target": "es5",
     "lib": ["es2020.string"],
     "noEmit": true,
     "strict": true,

.github/comments/invalid-reproduction.md

@@ -4,7 +4,7 @@ Depending on the quality of reproduction steps, this issue may be closed if no r
 
 ### Why was this issue marked with the `invalid-reproduction` label?
 
-To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with `create-payload-app@beta -t blank` or a forked/branched version of this repository with tests added (more info in the [reproduction-guide](https://github.com/payloadcms/payload/blob/main/.github/reproduction-guide.md)).
+To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with `create-payload-app@latest -t blank` or a forked/branched version of this repository with tests added (more info in the [reproduction-guide](https://github.com/payloadcms/payload/blob/main/.github/reproduction-guide.md)).
 
 To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as **minimal** as possible. This means that you should **remove unnecessary code, files, and dependencies** that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.
 

.github/workflows/lock-issues.yml

@@ -2,8 +2,8 @@ name: lock-issues
 
 on:
   schedule:
-    # Run nightly at 12am EST
-    - cron: '0 4 * * *'
+    # Run nightly at 12am EST, staggered with stale workflow
+    - cron: '0 5 * * *'
   workflow_dispatch:
 
 permissions:

.github/workflows/main.yml

@@ -41,14 +41,14 @@ jobs:
         with:
           filters: |
             needs_build:
-              - '.github/workflows/**'
+              - '.github/workflows/main.yml'
               - 'packages/**'
               - 'test/**'
               - 'pnpm-lock.yaml'
               - 'package.json'
               - 'templates/**'
             needs_tests:
-              - '.github/workflows/**'
+              - '.github/workflows/main.yml'
               - 'packages/**'
               - 'test/**'
               - 'pnpm-lock.yaml'
@@ -275,9 +275,11 @@ jobs:
           - admin__e2e__general
           - admin__e2e__list-view
           - admin__e2e__document-view
+          - admin-bar
           - admin-root
           - auth
           - auth-basic
+          - bulk-edit
           - joins
           - field-error-states
           - fields-relationship
@@ -307,12 +309,15 @@ jobs:
           - fields__collections__Text
           - fields__collections__UI
           - fields__collections__Upload
+          - query-presets
+          - form-state
           - live-preview
           - localization
           - locked-documents
           - i18n
           - plugin-cloud-storage
           - plugin-form-builder
+          - plugin-import-export
           - plugin-nested-docs
           - plugin-seo
           - versions
@@ -417,6 +422,7 @@ jobs:
       POSTGRES_USER: postgres
       POSTGRES_PASSWORD: postgres
       POSTGRES_DB: payloadtests
+      MONGODB_VERSION: 6.0
 
     steps:
       - uses: actions/checkout@v4
@@ -456,8 +462,14 @@ jobs:
           echo "POSTGRES_URL=postgresql://$POSTGRES_USER:$POSTGRES_PASSWORD@localhost:5432/$POSTGRES_DB" >> $GITHUB_ENV
         if: matrix.database == 'postgres'
 
+      # Avoid dockerhub rate-limiting
+      - name: Cache Docker images
+        uses: ScribeMD/docker-cache@0.5.0
+        with:
+          key: docker-${{ runner.os }}-mongo-${{ env.MONGODB_VERSION }}
+
       - name: Start MongoDB
-        uses: supercharge/mongodb-github-action@1.11.0
+        uses: supercharge/mongodb-github-action@1.12.0
         with:
           mongodb-version: 6.0
         if: matrix.database == 'mongodb'

.github/workflows/pr-title.yml

@@ -53,6 +53,7 @@ jobs:
             plugin-cloud
             plugin-cloud-storage
             plugin-form-builder
+            plugin-import-export
             plugin-multi-tenant
             plugin-nested-docs
             plugin-redirects

.github/workflows/publish-prerelease.yml

@@ -1,6 +1,9 @@
-name: release-canary
+name: publish-prerelease
 
 on:
+  schedule:
+    # Run nightly at 10pm EST
+    - cron: '0 3 * * *'
   workflow_dispatch:
 
 env:
@@ -11,7 +14,7 @@ env:
 
 jobs:
   release:
-    name: release-canary-${{ github.ref_name }}-${{ github.sha }}
+    name: publish-prerelease-${{ github.ref_name }}-${{ github.sha }}
     permissions:
       id-token: write
     runs-on: ubuntu-24.04
@@ -27,8 +30,19 @@ jobs:
         run: echo "//registry.npmjs.org/:_authToken=$NPM_TOKEN" >> ~/.npmrc
         env:
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
-      - name: Canary release script
-        run: pnpm release:canary
+
+      - name: Determine release type
+        id: determine_release_type
+        # Use 'canary' for main branch, 'internal' for others
+        run: |
+          if [[ ${{ github.ref_name }} == "main" ]]; then
+            echo "release_type=canary" >> $GITHUB_OUTPUT
+          else
+            echo "release_type=internal" >> $GITHUB_OUTPUT
+          fi
+
+      - name: Release
+        run: pnpm publish-prerelease --tag ${{ steps.determine_release_type.outputs.release_type }}
         env:
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
           NPM_CONFIG_PROVENANCE: true

.github/workflows/stale.yml

@@ -2,8 +2,8 @@ name: stale
 
 on:
   schedule:
-    # Run nightly at 1am EST
-    - cron: '0 5 * * *'
+    # Run nightly at 1am EST, staggered with lock-issues workflow
+    - cron: '0 6 * * *'
 
   workflow_dispatch:
     inputs:

.gitignore

@@ -306,6 +306,8 @@ $RECYCLE.BIN/
 /build
 .swc
 app/(payload)/admin/importMap.js
+test/admin-bar/app/(payload)/admin/importMap.js
+/test/admin-bar/app/(payload)/admin/importMap.js
 test/live-preview/app/(payload)/admin/importMap.js
 /test/live-preview/app/(payload)/admin/importMap.js
 test/admin-root/app/(payload)/admin/importMap.js
@@ -318,3 +320,8 @@ test/databaseAdapter.js
 /media-with-relation-preview
 /media-without-relation-preview
 /media-without-cache-tags
+test/.localstack
+test/google-cloud-storage
+test/azurestoragedata/
+
+licenses.csv

.idea/payload.iml

@@ -80,8 +80,9 @@
       <excludeFolder url="file://$MODULE_DIR$/packages/drizzle/dist" />
       <excludeFolder url="file://$MODULE_DIR$/packages/db-sqlite/.turbo" />
       <excludeFolder url="file://$MODULE_DIR$/packages/db-sqlite/dist" />
+      <excludeFolder url="file://$MODULE_DIR$/packages/plugin-import-export/dist" />
     </content>
     <orderEntry type="inheritedJdk" />
     <orderEntry type="sourceFolder" forTests="false" />
   </component>
-</module>
+</module>

.prettierignore

@@ -8,7 +8,6 @@
 **/dist/**
 **/node_modules
 **/temp
-**/docs/**
 tsconfig.json
 packages/payload/*.js
 packages/payload/*.d.ts

docs/.prettierrc.json

@@ -0,0 +1,6 @@
+{
+  "singleQuote": true,
+  "trailingComma": "all",
+  "printWidth": 80,
+  "semi": false
+}

docs/access-control/collections.mdx

@@ -11,11 +11,12 @@ Collection Access Control is [Access Control](../access-control/overview) used t
 To add Access Control to a Collection, use the `access` property in your [Collection Config](../configuration/collections):
 
 ```ts
-import type { CollectionConfig } from 'payload';
+import type { CollectionConfig } from 'payload'
 
 export const CollectionWithAccessControl: CollectionConfig = {
   // ...
-  access: { // highlight-line
+  access: {
+    // highlight-line
     // ...
   },
 }
@@ -52,24 +53,24 @@ export const CollectionWithAccessControl: CollectionConfig = {
 
 The following options are available:
 
-| Function                | Allows/Denies Access                         |
-| ----------------------- | -------------------------------------------- |
-| **`create`** | Used in the `create` operation. [More details](#create). |
-| **`read`**     | Used in the `find` and `findByID` operations. [More details](#read). |
-| **`update`** | Used in the `update` operation. [More details](#update). |
-| **`delete`** | Used in the `delete` operation. [More details](#delete). |
+| Function     | Allows/Denies Access                                                 |
+| ------------ | -------------------------------------------------------------------- |
+| **`create`** | Used in the `create` operation. [More details](#create).             |
+| **`read`**   | Used in the `find` and `findByID` operations. [More details](#read). |
+| **`update`** | Used in the `update` operation. [More details](#update).             |
+| **`delete`** | Used in the `delete` operation. [More details](#delete).             |
 
 If a Collection supports [`Authentication`](../authentication/overview), the following additional options are available:
 
-| Function                | Allows/Denies Access                                           |
-| ----------------------- | -------------------------------------------------------------- |
-| **`admin`**   | Used to restrict access to the [Admin Panel](../admin/overview). [More details](#admin). |
+| Function     | Allows/Denies Access                                                                     |
+| ------------ | ---------------------------------------------------------------------------------------- |
+| **`admin`**  | Used to restrict access to the [Admin Panel](../admin/overview). [More details](#admin). |
 | **`unlock`** | Used to restrict which users can access the `unlock` operation. [More details](#unlock). |
 
 If a Collection supports [Versions](../versions/overview), the following additional options are available:
 
-| Function           | Allows/Denies Access                                                                                                   |
-| ------------------ | ---------------------------------------------------------------------------------------------------------------------- |
+| Function           | Allows/Denies Access                                                                                                                                   |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | **`readVersions`** | Used to control who can read versions, and who can't. Will automatically restrict the Admin UI version viewing access. [More details](#read-versions). |
 
 ### Create
@@ -95,10 +96,10 @@ export const CollectionWithCreateAccess: CollectionConfig = {
 
 The following arguments are provided to the `create` function:
 
-| Option     | Description                                                                                                                  |
-| ---------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| Option     | Description                                                                                                                   |
+| ---------- | ----------------------------------------------------------------------------------------------------------------------------- |
 | **`req`**  | The [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object containing the currently authenticated `user`. |
-| **`data`** | The data passed to create the document with.                                                                                 |
+| **`data`** | The data passed to create the document with.                                                                                  |
 
 ### Read
 
@@ -122,8 +123,9 @@ export const CollectionWithReadAccess: CollectionConfig = {
 ```
 
 <Banner type="success">
-  **Tip:**
-  Return a [Query](../queries/overview) to limit the Documents to only those that match the constraint. This can be helpful to restrict users' access to specific Documents. [More details](../queries/overview).
+  **Tip:** Return a [Query](../queries/overview) to limit the Documents to only
+  those that match the constraint. This can be helpful to restrict users' access
+  to specific Documents. [More details](../queries/overview).
 </Banner>
 
 As your application becomes more complex, you may want to define your function in a separate file and import them into your Collection Config:
@@ -149,10 +151,10 @@ export const canReadPage: Access = ({ req: { user } }) => {
 
 The following arguments are provided to the `read` function:
 
-| Option    | Description                                                                |
-| --------- | -------------------------------------------------------------------------- |
+| Option    | Description                                                                                                                   |
+| --------- | ----------------------------------------------------------------------------------------------------------------------------- |
 | **`req`** | The [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object containing the currently authenticated `user`. |
-| **`id`**  | `id` of document requested, if within `findByID`.                           |
+| **`id`**  | `id` of document requested, if within `findByID`.                                                                             |
 
 ### Update
 
@@ -167,7 +169,7 @@ export const CollectionWithUpdateAccess: CollectionConfig = {
   // ...
   access: {
     // highlight-start
-    update: ({ req: { user }}) => {
+    update: ({ req: { user } }) => {
       return Boolean(user)
     },
     // highlight-end
@@ -176,8 +178,9 @@ export const CollectionWithUpdateAccess: CollectionConfig = {
 ```
 
 <Banner type="success">
-  **Tip:**
-  Return a [Query](../queries/overview) to limit the Documents to only those that match the constraint. This can be helpful to restrict users' access to specific Documents. [More details](../queries/overview).
+  **Tip:** Return a [Query](../queries/overview) to limit the Documents to only
+  those that match the constraint. This can be helpful to restrict users' access
+  to specific Documents. [More details](../queries/overview).
 </Banner>
 
 As your application becomes more complex, you may want to define your function in a separate file and import them into your Collection Config:
@@ -198,11 +201,11 @@ export const canUpdateUser: Access = ({ req: { user }, id }) => {
 
 The following arguments are provided to the `update` function:
 
-| Option     | Description                                                                |
-| ---------- | -------------------------------------------------------------------------- |
+| Option     | Description                                                                                                                   |
+| ---------- | ----------------------------------------------------------------------------------------------------------------------------- |
 | **`req`**  | The [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object containing the currently authenticated `user`. |
-| **`id`**   | `id` of document requested to update.                                       |
-| **`data`** | The data passed to update the document with.                                |
+| **`id`**   | `id` of document requested to update.                                                                                         |
+| **`data`** | The data passed to update the document with.                                                                                  |
 
 ### Delete
 
@@ -217,7 +220,7 @@ export const CollectionWithDeleteAccess: CollectionConfig = {
   // ...
   access: {
     // highlight-start
-    delete: ({ req: { user }}) => {
+    delete: ({ req: { user } }) => {
       return Boolean(user)
     },
     // highlight-end
@@ -270,7 +273,7 @@ export const CollectionWithAdminAccess: CollectionConfig = {
   // ...
   access: {
     // highlight-start
-    admin: ({ req: { user }}) => {
+    admin: ({ req: { user } }) => {
       return Boolean(user)
     },
     // highlight-end
@@ -280,8 +283,8 @@ export const CollectionWithAdminAccess: CollectionConfig = {
 
 The following arguments are provided to the `admin` function:
 
-| Option    | Description                                                                |
-| --------- | -------------------------------------------------------------------------- |
+| Option    | Description                                                                                                                   |
+| --------- | ----------------------------------------------------------------------------------------------------------------------------- |
 | **`req`** | The [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object containing the currently authenticated `user`. |
 
 ### Unlock
@@ -297,7 +300,7 @@ export const CollectionWithUnlockAccess: CollectionConfig = {
   // ...
   access: {
     // highlight-start
-    unlock: ({ req: { user }}) => {
+    unlock: ({ req: { user } }) => {
       return Boolean(user)
     },
     // highlight-end
@@ -307,8 +310,8 @@ export const CollectionWithUnlockAccess: CollectionConfig = {
 
 The following arguments are provided to the `unlock` function:
 
-| Option    | Description                                                                |
-| --------- | -------------------------------------------------------------------------- |
+| Option    | Description                                                                                                                   |
+| --------- | ----------------------------------------------------------------------------------------------------------------------------- |
 | **`req`** | The [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object containing the currently authenticated `user`. |
 
 ### Read Versions
@@ -324,7 +327,7 @@ export const CollectionWithVersionsAccess: CollectionConfig = {
   // ...
   access: {
     // highlight-start
-    readVersions: ({ req: { user }}) => {
+    readVersions: ({ req: { user } }) => {
       return Boolean(user)
     },
     // highlight-end
@@ -334,6 +337,6 @@ export const CollectionWithVersionsAccess: CollectionConfig = {
 
 The following arguments are provided to the `readVersions` function:
 
-| Option    | Description                                                                |
-| --------- | -------------------------------------------------------------------------- |
+| Option    | Description                                                                                                                   |
+| --------- | ----------------------------------------------------------------------------------------------------------------------------- |
 | **`req`** | The [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object containing the currently authenticated `user`. |

docs/access-control/fields.mdx

@@ -11,19 +11,21 @@ Field Access Control is [Access Control](../access-control/overview) used to res
 To add Access Control to a Field, use the `access` property in your [Field Config](../fields/overview):
 
 ```ts
-import type { Field } from 'payload';
+import type { Field } from 'payload'
 
 export const FieldWithAccessControl: Field = {
   // ...
-  access: { // highlight-line
+  access: {
+    // highlight-line
     // ...
   },
 }
 ```
 
 <Banner type="warning">
-  **Note:**
-  Field Access Controls does not support returning [Query](../queries/overview) constraints like [Collection Access Control](./collections) does.
+  **Note:** Field Access Controls does not support returning
+  [Query](../queries/overview) constraints like [Collection Access
+  Control](./collections) does.
 </Banner>
 
 ## Config Options
@@ -55,11 +57,11 @@ export const Posts: CollectionConfig = {
 
 The following options are available:
 
-| Function                | Purpose                                                                          |
-| ----------------------- | -------------------------------------------------------------------------------- |
+| Function     | Purpose                                                                                                    |
+| ------------ | ---------------------------------------------------------------------------------------------------------- |
 | **`create`** | Allows or denies the ability to set a field's value when creating a new document. [More details](#create). |
-| **`read`**     | Allows or denies the ability to read a field's value. [More details](#read).       |
-| **`update`** | Allows or denies the ability to update a field's value [More details](#update).    |
+| **`read`**   | Allows or denies the ability to read a field's value. [More details](#read).                               |
+| **`update`** | Allows or denies the ability to update a field's value [More details](#update).                            |
 
 ### Create
 
@@ -67,11 +69,11 @@ Returns a boolean which allows or denies the ability to set a field's value when
 
 **Available argument properties:**
 
-| Option            | Description                                                                |
-| ----------------- | -------------------------------------------------------------------------- |
+| Option            | Description                                                                                                                  |
+| ----------------- | ---------------------------------------------------------------------------------------------------------------------------- |
 | **`req`**         | The [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object containing the currently authenticated `user` |
-| **`data`**        | The full data passed to create the document.                               |
-| **`siblingData`** | Immediately adjacent field data passed to create the document.             |
+| **`data`**        | The full data passed to create the document.                                                                                 |
+| **`siblingData`** | Immediately adjacent field data passed to create the document.                                                               |
 
 ### Read
 
@@ -79,12 +81,12 @@ Returns a boolean which allows or denies the ability to read a field's value. If
 
 **Available argument properties:**
 
-| Option            | Description                                                                |
-| ----------------- | -------------------------------------------------------------------------- |
+| Option            | Description                                                                                                                  |
+| ----------------- | ---------------------------------------------------------------------------------------------------------------------------- |
 | **`req`**         | The [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object containing the currently authenticated `user` |
-| **`id`**          | `id` of the document being read                                            |
-| **`doc`**         | The full document data.                                                    |
-| **`siblingData`** | Immediately adjacent field data of the document being read.                |
+| **`id`**          | `id` of the document being read                                                                                              |
+| **`doc`**         | The full document data.                                                                                                      |
+| **`siblingData`** | Immediately adjacent field data of the document being read.                                                                  |
 
 ### Update
 
@@ -94,10 +96,10 @@ If `false` is returned and you attempt to update the field's value, the operatio
 
 **Available argument properties:**
 
-| Option            | Description                                                                |
-| ----------------- | -------------------------------------------------------------------------- |
+| Option            | Description                                                                                                                  |
+| ----------------- | ---------------------------------------------------------------------------------------------------------------------------- |
 | **`req`**         | The [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object containing the currently authenticated `user` |
-| **`id`**          | `id` of the document being updated                                         |
-| **`data`**        | The full data passed to update the document.                               |
-| **`siblingData`** | Immediately adjacent field data passed to update the document with.        |
-| **`doc`**         | The full document data, before the update is applied.                      |
+| **`id`**          | `id` of the document being updated                                                                                           |
+| **`data`**        | The full data passed to update the document.                                                                                 |
+| **`siblingData`** | Immediately adjacent field data passed to update the document with.                                                          |
+| **`doc`**         | The full document data, before the update is applied.                                                                        |

docs/access-control/globals.mdx

@@ -11,11 +11,12 @@ Global Access Control is [Access Control](../access-control/overview) used to re
 To add Access Control to a Global, use the `access` property in your [Global Config](../configuration/globals):
 
 ```ts
-import type { GlobalConfig } from 'payload';
+import type { GlobalConfig } from 'payload'
 
 export const GlobalWithAccessControl: GlobalConfig = {
   // ...
-  access: { // highlight-line
+  access: {
+    // highlight-line
     // ...
   },
 }
@@ -48,15 +49,15 @@ export default Header
 
 The following options are available:
 
-| Function                | Allows/Denies Access                   |
-| ----------------------- | -------------------------------------- |
-| **`read`**     | Used in the `findOne` Global operation. [More details](#read). |
+| Function     | Allows/Denies Access                                            |
+| ------------ | --------------------------------------------------------------- |
+| **`read`**   | Used in the `findOne` Global operation. [More details](#read).  |
 | **`update`** | Used in the `update` Global operation. [More details](#update). |
 
 If a Global supports [Versions](../versions/overview), the following additional options are available:
 
-| Function           | Allows/Denies Access                                                                                                   |
-| ------------------ | ---------------------------------------------------------------------------------------------------------------------- |
+| Function           | Allows/Denies Access                                                                                                                                   |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | **`readVersions`** | Used to control who can read versions, and who can't. Will automatically restrict the Admin UI version viewing access. [More details](#read-versions). |
 
 ### Read
@@ -75,15 +76,15 @@ const Header: GlobalConfig = {
     read: ({ req: { user } }) => {
       return Boolean(user)
     },
-  }
+  },
   // highlight-end
 }
 ```
 
 The following arguments are provided to the `read` function:
 
-| Option    | Description                                                                |
-| --------- | -------------------------------------------------------------------------- |
+| Option    | Description                                                                                                                   |
+| --------- | ----------------------------------------------------------------------------------------------------------------------------- |
 | **`req`** | The [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object containing the currently authenticated `user`. |
 
 ### Update
@@ -102,17 +103,17 @@ const Header: GlobalConfig = {
     update: ({ req: { user }, data }) => {
       return Boolean(user)
     },
-  }
+  },
   // highlight-end
 }
 ```
 
 The following arguments are provided to the `update` function:
 
-| Option     | Description                                                                |
-| ---------- | -------------------------------------------------------------------------- |
+| Option     | Description                                                                                                                   |
+| ---------- | ----------------------------------------------------------------------------------------------------------------------------- |
 | **`req`**  | The [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object containing the currently authenticated `user`. |
-| **`data`** | The data passed to update the global with.                                 |
+| **`data`** | The data passed to update the global with.                                                                                    |
 
 ### Read Versions
 
@@ -127,7 +128,7 @@ export const GlobalWithVersionsAccess: GlobalConfig = {
   // ...
   access: {
     // highlight-start
-    readVersions: ({ req: { user }}) => {
+    readVersions: ({ req: { user } }) => {
       return Boolean(user)
     },
     // highlight-end
@@ -137,6 +138,6 @@ export const GlobalWithVersionsAccess: GlobalConfig = {
 
 The following arguments are provided to the `readVersions` function:
 
-| Option    | Description                                                                |
-| --------- | -------------------------------------------------------------------------- |
+| Option    | Description                                                                                                                   |
+| --------- | ----------------------------------------------------------------------------------------------------------------------------- |
 | **`req`** | The [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object containing the currently authenticated `user`. |

docs/access-control/overview.mdx

@@ -42,8 +42,10 @@ const defaultPayloadAccess = ({ req: { user } }) => {
 ```
 
 <Banner type="warning">
-  **Important:**
-  In the [Local API](../local-api/overview), all Access Control is _skipped_ by default. This allows your server to have full control over your application. To opt back in, you can set the `overrideAccess` option to `false` in your requests.
+  **Important:** In the [Local API](../local-api/overview), all Access Control
+  is _skipped_ by default. This allows your server to have full control over
+  your application. To opt back in, you can set the `overrideAccess` option to
+  `false` in your requests.
 </Banner>
 
 ## The Access Operation
@@ -53,13 +55,14 @@ The Admin Panel responds dynamically to your changes to Access Control. For exam
 To accomplish this, Payload exposes the [Access Operation](../authentication/operations#access). Upon login, Payload executes each Access Control function at the top level, across all Collections, Globals, and Fields, and returns a response that contains a reflection of what the currently authenticated user can do within your application.
 
 <Banner type="warning">
-  **Important:**
-  When your access control functions are executed via the [Access Operation](../authentication/operations#access),  the `id` and `data` arguments will be `undefined`. This is because Payload is executing your functions without referencing a specific Document.
+  **Important:** When your access control functions are executed via the [Access
+  Operation](../authentication/operations#access), the `id` and `data` arguments
+  will be `undefined`. This is because Payload is executing your functions
+  without referencing a specific Document.
 </Banner>
 
 If you use `id` or `data` within your access control functions, make sure to check that they are defined first. If they are not, then you can assume that your Access Control is being executed via the Access Operation to determine solely what the user can do within the Admin Panel.
 
-
 ## Locale Specific Access Control
 
 To implement locale-specific access control, you can use the `req.locale` argument in your access control functions. This argument allows you to evaluate the current locale of the request and determine access permissions accordingly.
@@ -70,10 +73,10 @@ Here is an example:
 const access = ({ req }) => {
   // Grant access if the locale is 'en'
   if (req.locale === 'en') {
-    return true;
+    return true
   }
 
   // Deny access for all other locales
-  return false;
+  return false
 }
 ```

docs/admin/customizing-css.mdx

@@ -29,8 +29,10 @@ Here is an example of how you might target the Dashboard View and change the bac
 ```
 
 <Banner type="warning">
-  **Note:**
-  If you are building [Custom Components](../custom-components/overview), it is best to import your own stylesheets directly into your components, rather than using the global stylesheet. You can continue to use the [CSS library](#css-library) as needed.
+  **Note:** If you are building [Custom
+  Components](../custom-components/overview), it is best to import your own
+  stylesheets directly into your components, rather than using the global
+  stylesheet. You can continue to use the [CSS library](#css-library) as needed.
 </Banner>
 
 ### Specificity rules
@@ -40,9 +42,10 @@ All Payload CSS is encapsulated inside CSS layers under `@layer payload-default`
 We have also provided a layer `@layer payload` if you want to use layers and ensure that your styles are applied after payload.
 
 To override existing styles in a way that the previous rules of specificity would be respected you can use the default layer like so
+
 ```css
 @layer payload-default {
-  // my styles within the payload specificity
+  // my styles within the Payload specificity
 }
 ```
 
@@ -77,8 +80,8 @@ The following variables are defined and can be overridden:
 For an up-to-date, comprehensive list of all available variables, please refer to the [Source Code](https://github.com/payloadcms/payload/blob/main/packages/ui/src/scss).
 
 <Banner type="warning">
-  **Warning:**
-  If you're overriding colors or theme elevations, make sure to consider how [your changes will affect dark mode](#dark-mode).
+  **Warning:** If you're overriding colors or theme elevations, make sure to
+  consider how [your changes will affect dark mode](#dark-mode).
 </Banner>
 
 #### Dark Mode

docs/admin/locked-documents.mdx

@@ -20,7 +20,12 @@ When a user starts editing a document, Payload locks it for that user. If anothe
 
 The lock will automatically expire after a set period of inactivity, configurable using the `duration` property in the `lockDocuments` configuration, after which others can resume editing.
 
-<Banner type="info"> **Note:** If your application does not require document locking, you can disable this feature for any collection or global by setting the `lockDocuments` property to `false`. </Banner>
+<Banner type="info">
+  {' '}
+  **Note:** If your application does not require document locking, you can
+  disable this feature for any collection or global by setting the
+  `lockDocuments` property to `false`.{' '}
+</Banner>
 
 ### Config Options
 

docs/admin/metadata.mdx

@@ -6,7 +6,11 @@ desc: Customize the metadata of your pages within the Admin Panel
 keywords: admin, components, custom, documentation, Content Management System, cms, headless, javascript, node, react, nextjs
 ---
 
-Every page within the Admin Panel automatically receives dynamic, auto-generated metadata derived from live document data, the user's current locale, and more, without any additional configuration. This includes the page title, description, og:image and everything in between. Metadata is fully configurable at the root level and cascades down to individual collections, documents, and custom views, allowing for the ability to control metadata on any page with high precision.
+Every page within the Admin Panel automatically receives dynamic, auto-generated metadata derived from live document data, the user's current locale, and more. This includes the page title, description, og:image, etc. and requires no additional configuration.
+
+Metadata is fully configurable at the root level and cascades down to individual collections, documents, and custom views. This allows for the ability to control metadata on any page with high precision, while also providing sensible defaults.
+
+All metadata is injected into Next.js' [`generateMetadata`](https://nextjs.org/docs/app/api-reference/functions/generate-metadata) function. This used to generate the `<head>` of pages within the Admin Panel. All metadata options that are available in Next.js are exposed by Payload.
 
 Within the Admin Panel, metadata can be customized at the following levels:
 
@@ -46,19 +50,17 @@ To customize Root Metadata, use the `admin.meta` key in your Payload Config:
 
 The following options are available for Root Metadata:
 
-| Key | Type | Description |
-| --- | --- | --- |
-| **`title`** | `string` | The title of the Admin Panel. |
-| **`description`** | `string` | The description of the Admin Panel. |
-| **`defaultOGImageType`** | `dynamic` (default), `static`, or `off` | The type of default OG image to use. If set to `dynamic`, Payload will use Next.js image generation to create an image with the title of the page. If set to `static`, Payload will use the `defaultOGImage` URL. If set to `off`, Payload will not generate an OG image. |
-| **`icons`** | `IconConfig[]` | An array of icon objects. [More details](#icons) |
-| **`keywords`** | `string` | A comma-separated list of keywords to include in the metadata of the Admin Panel. |
-| **`openGraph`** | `OpenGraphConfig` | An object containing Open Graph metadata. [More details](#open-graph) |
-| **`titleSuffix`** | `string` | A suffix to append to the end of the title of every page. Defaults to "- Payload". |
+| Key                  | Type                                    | Description                                                                                                                                                                                                                                                               |
+| -------------------- | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `defaultOGImageType` | `dynamic` (default), `static`, or `off` | The type of default OG image to use. If set to `dynamic`, Payload will use Next.js image generation to create an image with the title of the page. If set to `static`, Payload will use the `defaultOGImage` URL. If set to `off`, Payload will not generate an OG image. |
+| `titleSuffix`        | `string`                                | A suffix to append to the end of the title of every page. Defaults to "- Payload".                                                                                                                                                                                        |
+| `[keyof Metadata]`   | `unknown`                               | Any other properties that Next.js supports within the `generateMetadata` function. [More details](https://nextjs.org/docs/app/api-reference/functions/generate-metadata).                                                                                                 |
 
 <Banner type="success">
-  **Reminder:**
-  These are the _root-level_ options for the Admin Panel. You can also customize metadata on the [Collection](../configuration/collections), [Global](../configuration/globals), and Document levels through their respective configs.
+  **Reminder:** These are the _root-level_ options for the Admin Panel. You can
+  also customize metadata on the [Collection](../configuration/collections),
+  [Global](../configuration/globals), and Document levels through their
+  respective configs.
 </Banner>
 
 ### Icons
@@ -67,7 +69,7 @@ The Icons Config corresponds to the `<link>` tags that are used to specify icons
 
 The most common icon type is the favicon, which is displayed in the browser tab. This is specified by the `rel` attribute `icon`. Other common icon types include `apple-touch-icon`, which is used by Apple devices when the Admin Panel is saved to the home screen, and `mask-icon`, which is used by Safari to mask the Admin Panel icon.
 
-To customize icons, use the `icons` key within the `admin.meta` object in your Payload Config:
+To customize icons, use the `admin.meta.icons` property in your Payload Config:
 
 ```ts
 {
@@ -93,23 +95,13 @@ To customize icons, use the `icons` key within the `admin.meta` object in your P
 }
 ```
 
-The following options are available for Icons:
-
-| Key | Type | Description |
-| --- | --- | --- |
-| **`rel`** | `string` | The HTML `rel` attribute of the icon. |
-| **`type`** | `string` | The MIME type of the icon. |
-| **`color`** | `string` | The color of the icon. |
-| **`fetchPriority`** | `string` | The [fetch priority](https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/fetchPriority) of the icon. |
-| **`media`** | `string` | The [media query](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_media_queries/Using_media_queries) of the icon. |
-| **`sizes`** | `string` | The [sizes](https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/sizes) of the icon. |
-| **`url`** | `string` | The URL pointing the resource of the icon. |
+For a full list of all available Icon options, see the [Next.js documentation](https://nextjs.org/docs/app/api-reference/functions/generate-metadata#icons).
 
 ### Open Graph
 
 Open Graph metadata is a set of tags that are used to control how URLs are displayed when shared on social media platforms. Open Graph metadata is automatically generated by Payload, but can be customized at the Root level.
 
-To customize Open Graph metadata, use the `openGraph` key within the `admin.meta` object in your Payload Config:
+To customize Open Graph metadata, use the `admin.meta.openGraph` property in your Payload Config:
 
 ```ts
 {
@@ -135,14 +127,47 @@ To customize Open Graph metadata, use the `openGraph` key within the `admin.meta
 }
 ```
 
-The following options are available for Open Graph Metadata:
+For a full list of all available Open Graph options, see the [Next.js documentation](https://nextjs.org/docs/app/api-reference/functions/generate-metadata#opengraph).
 
-| Key | Type | Description |
-| --- | --- | --- |
-| **`description`** | `string` | The description of the Admin Panel. |
-| **`images`** | `OGImageConfig` or `OGImageConfig[]` | An array of image objects. |
-| **`siteName`** | `string` | The name of the site. |
-| **`title`** | `string` | The title of the Admin Panel. |
+### Robots
+
+Setting the `robots` property will allow you to control the `robots` meta tag that is rendered within the `<head>` of the Admin Panel. This can be used to control how search engines index pages and displays them in search results.
+
+By default, the Admin Panel is set to prevent search engines from indexing pages within the Admin Panel.
+
+To customize the Robots Config, use the `admin.meta.robots` property in your Payload Config:
+
+```ts
+{
+  // ...
+  admin: {
+    meta: {
+      // highlight-start
+      robots: 'noindex, nofollow',
+      // highlight-end
+    },
+  },
+}
+```
+
+For a full list of all available Robots options, see the [Next.js documentation](https://nextjs.org/docs/app/api-reference/functions/generate-metadata#robots).
+
+##### Prevent Crawling
+
+While setting meta tags via `admin.meta.robots` can prevent search engines from _indexing_ web pages, it does not prevent them from being _crawled_.
+
+To prevent your pages from being crawled altogether, add a `robots.txt` file to your root directory.
+
+```text
+User-agent: *
+Disallow: /admin/
+```
+
+<Banner type="info">
+  **Note:** If you've customized the path to your Admin Panel via
+  `config.routes`, be sure to update the `Disallow` directive to match your
+  custom path.
+</Banner>
 
 ## Collection Metadata
 
@@ -158,7 +183,7 @@ export const MyCollection: CollectionConfig = {
   admin: {
     // highlight-start
     meta: {
-    // highlight-end
+      // highlight-end
       title: 'My Collection',
       description: 'The best collection in the world',
     },
@@ -182,7 +207,7 @@ export const MyGlobal: GlobalConfig = {
   admin: {
     // highlight-start
     meta: {
-    // highlight-end
+      // highlight-end
       title: 'My Global',
       description: 'The best admin panel in the world',
     },
@@ -214,3 +239,4 @@ To customize View Metadata, use the `meta` key within your View Config:
     },
   },
 }
+```

docs/admin/overview.mdx

@@ -13,7 +13,9 @@ The Admin Panel is designed to [white-label your brand](https://payloadcms.com/b
 The Admin Panel is written in [TypeScript](https://www.typescriptlang.org) and built with [React](https://react.dev) using the [Next.js App Router](https://nextjs.org/docs/app). It supports [React Server Components](https://react.dev/reference/rsc/server-components), enabling the use of the [Local API](/docs/local-api/overview) on the front-end. You can install Payload into any [existing Next.js app in just one line](../getting-started/installation) and [deploy it anywhere](../production/deployment).
 
 <Banner type="success">
-  The Payload Admin Panel is designed to be as minimal and straightforward as possible to allow easy customization and control. [Learn more](../custom-components/overview).
+  The Payload Admin Panel is designed to be as minimal and straightforward as
+  possible to allow easy customization and control. [Learn
+  more](../custom-components/overview).
 </Banner>
 
 <LightDarkImage
@@ -48,7 +50,8 @@ app/
 ```
 
 <Banner type="info">
-  If you are not familiar with Next.js project structure, you can [learn more about it here](https://nextjs.org/docs/getting-started/project-structure).
+  If you are not familiar with Next.js project structure, you can [learn more
+  about it here](https://nextjs.org/docs/getting-started/project-structure).
 </Banner>
 
 As shown above, all Payload routes are nested within the `(payload)` route group. This creates a boundary between the Admin Panel and the rest of your application by scoping all layouts and styles. The `layout.tsx` file within this directory, for example, is where Payload manages the `html` tag of the document to set proper [`lang`](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/lang) and [`dir`](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/dir) attributes, etc.
@@ -56,8 +59,11 @@ As shown above, all Payload routes are nested within the `(payload)` route group
 The `admin` directory contains all the _pages_ related to the interface itself, whereas the `api` and `graphql` directories contains all the _routes_ related to the [REST API](../rest-api/overview) and [GraphQL API](../graphql/overview). All admin routes are [easily configurable](#customizing-routes) to meet your application's exact requirements.
 
 <Banner type="warning">
-  **Note:**
-  If you don't intend to use the Admin Panel, [REST API](../rest-api/overview), or [GraphQL API](../graphql/overview), you can opt-out by simply deleting their corresponding directories within your Next.js app. The overhead, however, is completely constrained to these routes, and will not slow down or affect Payload outside when not in use.
+  **Note:** If you don't intend to use the Admin Panel, [REST
+  API](../rest-api/overview), or [GraphQL API](../graphql/overview), you can
+  opt-out by simply deleting their corresponding directories within your Next.js
+  app. The overhead, however, is completely constrained to these routes, and
+  will not slow down or affect Payload outside when not in use.
 </Banner>
 
 Finally, the `custom.scss` file is where you can add or override globally-oriented styles in the Admin Panel, such as modify the color palette. Customizing the look and feel through CSS alone is a powerful feature of the Admin Panel, [more on that here](./customizing-css).
@@ -78,7 +84,8 @@ import { buildConfig } from 'payload'
 
 const config = buildConfig({
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 })
@@ -86,25 +93,28 @@ const config = buildConfig({
 
 The following options are available:
 
-| Option                         | Description                                                                                                                                                           |
-|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **`avatar`**                   | Set account profile picture. Options: `gravatar`, `default` or a custom React component.                                                                              |
-| **`autoLogin`**                | Used to automate log-in for dev and demonstration convenience. [More details](../authentication/overview).                                                            |
-| **`buildPath`**                | Specify an absolute path for where to store the built Admin bundle used in production. Defaults to `path.resolve(process.cwd(), 'build')`.                            |
-| **`components`**               | Component overrides that affect the entirety of the Admin Panel. [More details](../custom-components/overview).                                                                        |
-| **`custom`**                   | Any custom properties you wish to pass to the Admin Panel.                                                                                                            |
-| **`dateFormat`**               | The date format that will be used for all dates within the Admin Panel. Any valid [date-fns](https://date-fns.org/) format pattern can be used.                       |
-| **`livePreview`**              | Enable real-time editing for instant visual feedback of your front-end application. [More details](../live-preview/overview).                                         |
-| **`meta`**                     | Base metadata to use for the Admin Panel. [More details](./metadata).                                                                                                 |
-| **`routes`**                   | Replace built-in Admin Panel routes with your own custom routes. [More details](#customizing-routes).                                                                 |
-| **`suppressHydrationWarning`** | If set to `true`, suppresses React hydration mismatch warnings during the hydration of the root `<html>` tag. Defaults to `false`.                                      |
-| **`theme`**                    | Restrict the Admin Panel theme to use only one of your choice. Default is `all`.                                                                                      |
-| **`timezones`**                 | Configure the timezone settings for the admin panel. [More details](#timezones)                                                                                       |
-| **`user`**                     | The `slug` of the Collection that you want to allow to login to the Admin Panel. [More details](#the-admin-user-collection).                                          |
+| Option                         | Description                                                                                                                                     |
+| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`avatar`**                   | Set account profile picture. Options: `gravatar`, `default` or a custom React component.                                                        |
+| **`autoLogin`**                | Used to automate log-in for dev and demonstration convenience. [More details](../authentication/overview).                                      |
+| **`buildPath`**                | Specify an absolute path for where to store the built Admin bundle used in production. Defaults to `path.resolve(process.cwd(), 'build')`.      |
+| **`components`**               | Component overrides that affect the entirety of the Admin Panel. [More details](../custom-components/overview).                                 |
+| **`custom`**                   | Any custom properties you wish to pass to the Admin Panel.                                                                                      |
+| **`dateFormat`**               | The date format that will be used for all dates within the Admin Panel. Any valid [date-fns](https://date-fns.org/) format pattern can be used. |
+| **`livePreview`**              | Enable real-time editing for instant visual feedback of your front-end application. [More details](../live-preview/overview).                   |
+| **`meta`**                     | Base metadata to use for the Admin Panel. [More details](./metadata).                                                                           |
+| **`routes`**                   | Replace built-in Admin Panel routes with your own custom routes. [More details](#customizing-routes).                                           |
+| **`suppressHydrationWarning`** | If set to `true`, suppresses React hydration mismatch warnings during the hydration of the root `<html>` tag. Defaults to `false`.              |
+| **`theme`**                    | Restrict the Admin Panel theme to use only one of your choice. Default is `all`.                                                                |
+| **`timezones`**                | Configure the timezone settings for the admin panel. [More details](#timezones)                                                                 |
+| **`user`**                     | The `slug` of the Collection that you want to allow to login to the Admin Panel. [More details](#the-admin-user-collection).                    |
 
 <Banner type="success">
-  **Reminder:**
-  These are the _root-level_ options for the Admin Panel. You can also customize [Collection Admin Options](../configuration/collections#admin-options) and [Global Admin Options](../configuration/globals#admin-options) through their respective `admin` keys.
+  **Reminder:** These are the _root-level_ options for the Admin Panel. You can
+  also customize [Collection Admin
+  Options](../configuration/collections#admin-options) and [Global Admin
+  Options](../configuration/globals#admin-options) through their respective
+  `admin` keys.
 </Banner>
 
 ### The Admin User Collection
@@ -125,7 +135,8 @@ const config = buildConfig({
 <Banner type="warning">
   **Important:**
 
-  The Admin Panel can only be used by a single auth-enabled Collection. To enable authentication for a Collection, simply set `auth: true` in the Collection's configuration. See [Authentication](../authentication/overview) for more information.
+The Admin Panel can only be used by a single auth-enabled Collection. To enable authentication for a Collection, simply set `auth: true` in the Collection's configuration. See [Authentication](../authentication/overview) for more information.
+
 </Banner>
 
 By default, if you have not specified a Collection, Payload will automatically provide a `User` Collection with access to the Admin Panel. You can customize or override the fields and settings of the default `User` Collection by adding your own Collection with `slug: 'users'`. Doing this will force Payload to use your provided `User` Collection instead of its default version.
@@ -135,7 +146,7 @@ You can use whatever Collection you'd like to access the Admin Panel as long as
 - `admins` - meant to have a higher level of permissions to manage your data and access the Admin Panel
 - `customers` - meant for end users of your app that should not be allowed to log into the Admin Panel
 
-To do this, specify `admin: { user: 'admins' }` in your config. This will provide access to the Admin Panel to only `admins`. Any users authenticated as `customers` will be prevented from accessing the Admin Panel.  See [Access Control](/docs/access-control/overview) for full details.
+To do this, specify `admin: { user: 'admins' }` in your config. This will provide access to the Admin Panel to only `admins`. Any users authenticated as `customers` will be prevented from accessing the Admin Panel. See [Access Control](/docs/access-control/overview) for full details.
 
 ### Role-based Access Control
 
@@ -162,23 +173,24 @@ import { buildConfig } from 'payload'
 const config = buildConfig({
   // ...
   routes: {
-    admin: '/custom-admin-route' // highlight-line
-  }
+    admin: '/custom-admin-route', // highlight-line
+  },
 })
 ```
 
 The following options are available:
 
 | Option              | Default route         | Description                                       |
-|---------------------|-----------------------|---------------------------------------------------|
+| ------------------- | --------------------- | ------------------------------------------------- |
 | `admin`             | `/admin`              | The Admin Panel itself.                           |
 | `api`               | `/api`                | The [REST API](../rest-api/overview) base path.   |
 | `graphQL`           | `/graphql`            | The [GraphQL API](../graphql/overview) base path. |
 | `graphQLPlayground` | `/graphql-playground` | The GraphQL Playground.                           |
 
 <Banner type="success">
-  **Tip:**
-  You can easily add _new_ routes to the Admin Panel through [Custom Endpoints](../rest-api/overview#custom-endpoints) and [Custom Views](../custom-components/custom-views).
+  **Tip:** You can easily add _new_ routes to the Admin Panel through [Custom
+  Endpoints](../rest-api/overview#custom-endpoints) and [Custom
+  Views](../custom-components/custom-views).
 </Banner>
 
 #### Customizing Root-level Routes
@@ -195,8 +207,9 @@ app/
 ```
 
 <Banner type="warning">
-  **Note:**
-  If you set Root-level Routes _before_ auto-generating the Admin Panel via `create-payload-app`, your [Project Structure](#project-structure) will already be set up correctly.
+  **Note:** If you set Root-level Routes _before_ auto-generating the Admin
+  Panel via `create-payload-app`, your [Project Structure](#project-structure)
+  will already be set up correctly.
 </Banner>
 
 ### Admin-level Routes
@@ -212,28 +225,29 @@ const config = buildConfig({
   // ...
   admin: {
     routes: {
-      account: '/my-account' // highlight-line
-    }
+      account: '/my-account', // highlight-line
+    },
   },
 })
 ```
 
 The following options are available:
 
-| Option            | Default route           | Description                                     |
-| ----------------- | ----------------------- | ----------------------------------------------- |
-| `account`         | `/account`              | The user's account page.                        |
-| `createFirstUser` | `/create-first-user`    | The page to create the first user.              |
-| `forgot`          | `/forgot`               | The password reset page.                        |
-| `inactivity`      | `/logout-inactivity`    | The page to redirect to after inactivity.       |
-| `login`           | `/login`                | The login page.                                 |
-| `logout`          | `/logout`               | The logout page.                                |
-| `reset`           | `/reset`                | The password reset page.                        |
-| `unauthorized`    | `/unauthorized`         | The unauthorized page.                          |
+| Option            | Default route        | Description                               |
+| ----------------- | -------------------- | ----------------------------------------- |
+| `account`         | `/account`           | The user's account page.                  |
+| `createFirstUser` | `/create-first-user` | The page to create the first user.        |
+| `forgot`          | `/forgot`            | The password reset page.                  |
+| `inactivity`      | `/logout-inactivity` | The page to redirect to after inactivity. |
+| `login`           | `/login`             | The login page.                           |
+| `logout`          | `/logout`            | The logout page.                          |
+| `reset`           | `/reset`             | The password reset page.                  |
+| `unauthorized`    | `/unauthorized`      | The unauthorized page.                    |
 
 <Banner type="success">
-  **Note:**
-  You can also swap out entire _views_ out for your own, using the `admin.views` property of the Payload Config. See [Custom Views](../custom-components/custom-views) for more information.
+  **Note:** You can also swap out entire _views_ out for your own, using the
+  `admin.views` property of the Payload Config. See [Custom
+  Views](../custom-components/custom-views) for more information.
 </Banner>
 
 ## I18n
@@ -250,14 +264,15 @@ The `admin.timezones` configuration allows you to configure timezone settings fo
 
 The following options are available:
 
-| Option            | Description                                     |
-| ----------------- | ----------------------------------------------- |
-| `supportedTimezones`         | An array of label/value options for selectable timezones where the value is the IANA name eg. `America/Detroit`                        |
-| `defaultTimezone`               | The `value` of the default selected timezone. eg. `America/Los_Angeles`                        |
+| Option               | Description                                                                                                     |
+| -------------------- | --------------------------------------------------------------------------------------------------------------- |
+| `supportedTimezones` | An array of label/value options for selectable timezones where the value is the IANA name eg. `America/Detroit` |
+| `defaultTimezone`    | The `value` of the default selected timezone. eg. `America/Los_Angeles`                                         |
 
 We validate the supported timezones array by checking the value against the list of IANA timezones supported via the Intl API, specifically `Intl.supportedValuesOf('timeZone')`.
 
 <Banner type="info">
-  **Important**
-  You must enable timezones on each individual date field via `timezone: true`. See [Date Fields](../fields/overview#date) for more information.
+  **Important** You must enable timezones on each individual date field via
+  `timezone: true`. See [Date Fields](../fields/overview#date) for more
+  information.
 </Banner>

docs/admin/preferences.mdx

@@ -18,8 +18,9 @@ Out of the box, Payload handles the persistence of your users' preferences in a
 <Banner type="warning">
   **Important:**
 
-  All preferences are stored on an individual user basis. Payload automatically recognizes the user
-  that is reading or setting a preference via all provided authentication methods.
+All preferences are stored on an individual user basis. Payload automatically recognizes the user
+that is reading or setting a preference via all provided authentication methods.
+
 </Banner>
 
 ## Use Cases
@@ -76,80 +77,66 @@ Here is an example for how you can utilize `usePreferences` within your custom A
 
 ```tsx
 'use client'
-import React, { Fragment, useState, useEffect, useCallback } from 'react';
+import React, { Fragment, useState, useEffect, useCallback } from 'react'
 import { usePreferences } from '@payloadcms/ui'
 
-const lastUsedColorsPreferenceKey = 'last-used-colors';
+const lastUsedColorsPreferenceKey = 'last-used-colors'
 
 export function CustomComponent() {
-  const { getPreference, setPreference } = usePreferences();
+  const { getPreference, setPreference } = usePreferences()
 
   // Store the last used colors in local state
-  const [lastUsedColors, setLastUsedColors] = useState([]);
+  const [lastUsedColors, setLastUsedColors] = useState([])
 
   // Callback to add a color to the last used colors
-  const updateLastUsedColors = useCallback((color) => {
-    // First, check if color already exists in last used colors.
-    // If it already exists, there is no need to update preferences
-    const colorAlreadyExists = lastUsedColors.indexOf(color) > -1;
+  const updateLastUsedColors = useCallback(
+    (color) => {
+      // First, check if color already exists in last used colors.
+      // If it already exists, there is no need to update preferences
+      const colorAlreadyExists = lastUsedColors.indexOf(color) > -1
 
-    if (!colorAlreadyExists) {
-      const newLastUsedColors = [
-        ...lastUsedColors,
-        color,
-      ];
+      if (!colorAlreadyExists) {
+        const newLastUsedColors = [...lastUsedColors, color]
 
-      setLastUsedColors(newLastUsedColors);
-      setPreference(lastUsedColorsPreferenceKey, newLastUsedColors);
-    }
-  }, [lastUsedColors, setPreference]);
+        setLastUsedColors(newLastUsedColors)
+        setPreference(lastUsedColorsPreferenceKey, newLastUsedColors)
+      }
+    },
+    [lastUsedColors, setPreference],
+  )
 
   // Retrieve preferences on component mount
   // This will only be run one time, because the `getPreference` method never changes
   useEffect(() => {
     const asyncGetPreference = async () => {
-      const lastUsedColorsFromPreferences = await getPreference(lastUsedColorsPreferenceKey);
-      setLastUsedColors(lastUsedColorsFromPreferences);
-    };
+      const lastUsedColorsFromPreferences = await getPreference(
+        lastUsedColorsPreferenceKey,
+      )
+      setLastUsedColors(lastUsedColorsFromPreferences)
+    }
 
-    asyncGetPreference();
-  }, [getPreference]);
+    asyncGetPreference()
+  }, [getPreference])
 
   return (
     <div>
-      <button
-        type="button"
-        onClick={() => updateLastUsedColors('red')}
-      >
+      <button type="button" onClick={() => updateLastUsedColors('red')}>
         Use red
       </button>
-      <button
-        type="button"
-        onClick={() => updateLastUsedColors('blue')}
-      >
+      <button type="button" onClick={() => updateLastUsedColors('blue')}>
         Use blue
       </button>
-      <button
-        type="button"
-        onClick={() => updateLastUsedColors('purple')}
-      >
+      <button type="button" onClick={() => updateLastUsedColors('purple')}>
         Use purple
       </button>
-      <button
-        type="button"
-        onClick={() => updateLastUsedColors('yellow')}
-      >
+      <button type="button" onClick={() => updateLastUsedColors('yellow')}>
         Use yellow
       </button>
       {lastUsedColors && (
         <Fragment>
           <h5>Last used colors:</h5>
           <ul>
-            {lastUsedColors?.map((color) => (
-              <li key={color}>
-                {color}
-              </li>
-            ))}
+            {lastUsedColors?.map((color) => <li key={color}>{color}</li>)}
           </ul>
         </Fragment>
       )}

docs/admin/preview.mdx

@@ -11,8 +11,10 @@ Preview is a feature that allows you to generate a direct link to your front-end
 The Preview feature can also be used to achieve something known as "Draft Preview". With Draft Preview, you can navigate to your front-end application and enter "draft mode", where your queries are modified to fetch draft content instead of published content. This is useful for seeing how your content will look before being published. [More details](#draft-preview).
 
 <Banner type="warning">
-  **Note:**
-  Preview is different than [Live Preview](../live-preview/overview). Live Preview loads your app within an iframe and renders it in the Admin Panel allowing you to see changes in real-time. Preview, on the other hand, allows you to generate a direct link to your front-end application.
+  **Note:** Preview is different than [Live Preview](../live-preview/overview).
+  Live Preview loads your app within an iframe and renders it in the Admin Panel
+  allowing you to see changes in real-time. Preview, on the other hand, allows
+  you to generate a direct link to your front-end application.
 </Banner>
 
 To add Preview, pass a function to the `admin.preview` property in any [Collection Config](../configuration/collections#admin-options) or [Global Config](../configuration/globals#admin-options):
@@ -29,7 +31,7 @@ export const Pages: CollectionConfig = {
     {
       name: 'slug',
       type: 'text',
-    }
+    },
   ],
 }
 ```
@@ -40,18 +42,18 @@ The `preview` function resolves to a string that points to your front-end applic
 
 The following arguments are provided to the `preview` function:
 
-| Path               | Description                                                                                                       |
-| ------------------ | ----------------------------------------------------------------------------------------------------------------- |
-| **`doc`**         | The data of the Document being edited. This includes changes that have not yet been saved.                         |
-| **`options`**     | An object with additional properties.                                                                              |
+| Path          | Description                                                                                |
+| ------------- | ------------------------------------------------------------------------------------------ |
+| **`doc`**     | The data of the Document being edited. This includes changes that have not yet been saved. |
+| **`options`** | An object with additional properties.                                                      |
 
 The `options` object contains the following properties:
 
-| Path               | Description                                                                                                       |
-| ------------------ | ----------------------------------------------------------------------------------------------------------------- |
-| **`locale`**      | The current locale of the Document being edited.                                                                   |
-| **`req`**         | The Payload Request object.                                                                                        |
-| **`token`**       | The JWT token of the currently authenticated in user.                                                              |
+| Path         | Description                                           |
+| ------------ | ----------------------------------------------------- |
+| **`locale`** | The current locale of the Document being edited.      |
+| **`req`**    | The Payload Request object.                           |
+| **`token`**  | The JWT token of the currently authenticated in user. |
 
 If your application requires a fully qualified URL, such as within deploying to Vercel Preview Deployments, you can use the `req` property to build this URL:
 
@@ -84,17 +86,17 @@ export const Pages: CollectionConfig = {
         slug,
         collection,
         path: `/${slug}`,
-        previewSecret: process.env.PREVIEW_SECRET || ''
+        previewSecret: process.env.PREVIEW_SECRET || '',
       })
 
       return `/preview?${encodedParams.toString()}` // highlight-line
-    }
+    },
   },
   fields: [
     {
       name: 'slug',
       type: 'text',
-    }
+    },
   ],
 }
 ```
@@ -133,7 +135,9 @@ export async function GET(
   const previewSecret = searchParams.get('previewSecret')
 
   if (previewSecret !== process.env.PREVIEW_SECRET) {
-    return new Response('You are not allowed to preview this page', { status: 403 })
+    return new Response('You are not allowed to preview this page', {
+      status: 403,
+    })
   }
 
   if (!path || !collection || !slug) {
@@ -141,7 +145,10 @@ export async function GET(
   }
 
   if (!path.startsWith('/')) {
-    return new Response('This endpoint can only be used for relative previews', { status: 500 })
+    return new Response(
+      'This endpoint can only be used for relative previews',
+      { status: 500 },
+    )
   }
 
   let user
@@ -152,15 +159,22 @@ export async function GET(
       headers: req.headers,
     })
   } catch (error) {
-    payload.logger.error({ err: error }, 'Error verifying token for live preview')
-    return new Response('You are not allowed to preview this page', { status: 403 })
+    payload.logger.error(
+      { err: error },
+      'Error verifying token for live preview',
+    )
+    return new Response('You are not allowed to preview this page', {
+      status: 403,
+    })
   }
 
   const draft = await draftMode()
 
   if (!user) {
     draft.disable()
-    return new Response('You are not allowed to preview this page', { status: 403 })
+    return new Response('You are not allowed to preview this page', {
+      status: 403,
+    })
   }
 
   // You can add additional checks here to see if the user is allowed to preview this page
@@ -211,7 +225,9 @@ export default async function Page({ params: paramsPromise }) {
 ```
 
 <Banner type="success">
-  **Note:**
-  For fully working example of this, check of the official [Draft Preview Example](https://github.com/payloadcms/payload/tree/main/examples/draft-preview) in the [Examples Directory](https://github.com/payloadcms/payload/tree/main/examples).
+  **Note:** For fully working example of this, check of the official [Draft
+  Preview
+  Example](https://github.com/payloadcms/payload/tree/main/examples/draft-preview)
+  in the [Examples
+  Directory](https://github.com/payloadcms/payload/tree/main/examples).
 </Banner>
-

docs/admin/react-hooks.mdx

@@ -9,8 +9,11 @@ keywords: admin, components, custom, documentation, Content Management System, c
 Payload provides a variety of powerful [React Hooks](https://react.dev/reference/react-dom/hooks) that can be used within your own [Custom Components](../custom-components/overview), such as [Custom Fields](../fields/overview#custom-components). With them, you can interface with Payload itself to build just about any type of complex customization you can think of.
 
 <Banner type="warning">
-  **Reminder:**
-  All Custom Components are [React Server Components](https://react.dev/reference/rsc/server-components) by default. Hooks, on the other hand, are only available in client-side environments. To use hooks, [ensure your component is a client component](../custom-components/overview#client-components).
+  **Reminder:** All Custom Components are [React Server
+  Components](https://react.dev/reference/rsc/server-components) by default.
+  Hooks, on the other hand, are only available in client-side environments. To
+  use hooks, [ensure your component is a client
+  component](../custom-components/overview#client-components).
 </Banner>
 
 ## useField
@@ -29,11 +32,11 @@ export const CustomTextField: TextFieldClientComponent = ({ path }) => {
 
   return (
     <div>
-      <p>
-        {path}
-      </p>
+      <p>{path}</p>
       <input
-        onChange={(e) => { setValue(e.target.value) }}
+        onChange={(e) => {
+          setValue(e.target.value)
+        }}
         value={value}
       />
     </div>
@@ -43,12 +46,12 @@ export const CustomTextField: TextFieldClientComponent = ({ path }) => {
 
 The `useField` hook accepts the following arguments:
 
-| Property          | Description                                                                                                                                                                                                                   |
-| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `path`            | If you do not provide a `path`, `name` will be used instead. This is the path to the field in the form data.                                                                                                                  |
+| Property          | Description                                                                                                                                                                                      |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `path`            | If you do not provide a `path`, `name` will be used instead. This is the path to the field in the form data.                                                                                     |
 | `validate`        | A validation function executed client-side _before_ submitting the form to the server. Different than [Field-level Validation](../fields/overview#validation) which runs strictly on the server. |
-| `disableFormData` | If `true`, the field will not be included in the form data when the form is submitted.                                                                                                                                         |
-| `hasRows` | If `true`, the field will be treated as a field with rows. This is useful for fields like `array` and `blocks`.                                                                                                                                         |
+| `disableFormData` | If `true`, the field will not be included in the form data when the form is submitted.                                                                                                           |
+| `hasRows`         | If `true`, the field will be treated as a field with rows. This is useful for fields like `array` and `blocks`.                                                                                  |
 
 The `useField` hook returns the following object:
 
@@ -78,8 +81,9 @@ type FieldType<T> = {
 There are times when a custom field component needs to have access to data from other fields, and you have a few options to do so. The `useFormFields` hook is a powerful and highly performant way to retrieve a form's field state, as well as to retrieve the `dispatchFields` method, which can be helpful for setting other fields' form states from anywhere within a form.
 
 <Banner type="success">
-  **This hook is great for retrieving only certain fields from form state** because it
-  ensures that it will only cause a rerender when the items that you ask for change.
+  **This hook is great for retrieving only certain fields from form state**
+  because it ensures that it will only cause a rerender when the items that you
+  ask for change.
 </Banner>
 
 Thanks to the awesome package [`use-context-selector`](https://github.com/dai-shi/use-context-selector), you can retrieve a specific field's state easily. This is ideal because you can ensure you have an up-to-date field state, and your component will only re-render when _that field's state_ changes.
@@ -95,9 +99,14 @@ const MyComponent: React.FC = () => {
   const amount = useFormFields(([fields, dispatch]) => fields.amount)
 
   // Do the same thing as above, but to the `feePercentage` field
-  const feePercentage = useFormFields(([fields, dispatch]) => fields.feePercentage)
+  const feePercentage = useFormFields(
+    ([fields, dispatch]) => fields.feePercentage,
+  )
 
-  if (typeof amount?.value !== 'undefined' && typeof feePercentage?.value !== 'undefined') {
+  if (
+    typeof amount?.value !== 'undefined' &&
+    typeof feePercentage?.value !== 'undefined'
+  ) {
     return <span>The fee is ${(amount.value * feePercentage.value) / 100}</span>
   }
 }
@@ -135,7 +144,7 @@ const ExampleComponent: React.FC = () => {
 
 #### Updating other fields' values
 
-If you are building a Custom Component, then you should use `setValue` which is returned from the `useField` hook to programmatically set your field's value. But if you're looking to update _another_ field's value, you can use `dispatchFields` returned from `useFormFields`.
+If you are building a Custom Component, then you should use `setValue` which is returned from the `useField` hook to programmatically set your field's value. But if you're looking to update _another_ field's value, you can use `dispatchFields` returned from `useAllFormFields`.
 
 You can send the following actions to the `dispatchFields` function.
 
@@ -159,10 +168,11 @@ The `useForm` hook can be used to interact with the form itself, and sends back
 <Banner type="warning">
   **Warning:**
 
-  This hook is optimized to avoid causing rerenders when fields change, and as such, its `fields`
-  property will be out of date. You should only leverage this hook if you need to perform actions
-  against the form in response to your users' actions. Do not rely on its returned "fields" as being
-  up-to-date. They will be removed from this hook's response in an upcoming version.
+This hook is optimized to avoid causing rerenders when fields change, and as such, its `fields`
+property will be out of date. You should only leverage this hook if you need to perform actions
+against the form in response to your users' actions. Do not rely on its returned "fields" as being
+up-to-date. They will be removed from this hook's response in an upcoming version.
+
 </Banner>
 
 The `useForm` hook returns an object with the following properties:
@@ -384,65 +394,63 @@ The `useForm` hook returns an object with the following properties:
     ]}
   />
 
-
 \`\`\`tsx
 import { useForm } from "@payloadcms/ui"
 
 export const CustomArrayManager = () => {
   const { addFieldRow } = useForm()
 
-  return (
-    <button
-      type="button"
-      onClick={() => {
-        addFieldRow({
-          path: "arrayField",
-          schemaPath: "arrayField",
-          rowIndex: 0, // optionally specify the index to add the row at
-          subFieldState: {
-            textField: {
-              initialValue: 'New row text',
-              valid: true,
-              value: 'New row text',
-            },
-          },
-          // blockType: "yourBlockSlug",
-          // ^ if managing a block array, you need to specify the block type
-        })
-      }}
-    >
-      Add Row
-    </button>
-  )
-}
-\`\`\`
+return (
+
+<button
+  type="button"
+  onClick={() => {
+    addFieldRow({
+      path: 'arrayField',
+      schemaPath: 'arrayField',
+      rowIndex: 0, // optionally specify the index to add the row at
+      subFieldState: {
+        textField: {
+          initialValue: 'New row text',
+          valid: true,
+          value: 'New row text',
+        },
+      },
+      // blockType: "yourBlockSlug",
+      // ^ if managing a block array, you need to specify the block type
+    })
+  }}
+>
+  Add Row
+</button>
+) } \`\`\`
 
 An example config to go along with the Custom Component
 
 \`\`\`tsx
 const ExampleCollection = {
-  slug: "example-collection",
-  fields: [
-    {
-      name: "arrayField",
-      type: "array",
-      fields: [
-        {
-          name: "textField",
-          type: "text",
-        },
-      ],
-    },
-    {
-      type: "ui",
-      name: "customArrayManager",
-      admin: {
-        components: {
-          Field: '/path/to/CustomArrayManagerField',
-        },
-      },
-    },
-  ],
+slug: "example-collection",
+fields: [
+{
+name: "arrayField",
+type: "array",
+fields: [
+{
+name: "textField",
+type: "text",
+},
+],
+},
+{
+type: "ui",
+name: "customArrayManager",
+admin: {
+components: {
+Field: '/path/to/CustomArrayManagerField',
+},
+},
+},
+],
 }
 \`\`\`
 `
@@ -460,32 +468,28 @@ const ExampleCollection = {
         drawerDescription: 'A useful method to programmatically remove a row from an array or block field.',
         drawerSlug: 'removeFieldRow',
         drawerContent:  `
-  <TableWithDrawers
-    columns={[
-      'Prop',
-      'Description',
-    ]}
-    rows={[
-      [
-        {
-          value: "**\\\`path\\\`**",
-        },
-        {
-          value: "The path to the array or block field",
-        },
-      ],
-      [
-        {
-          value: "**\\\`rowIndex\\\`**",
-        },
-        {
-          value: "The index of the row to remove",
-        },
-      ],
-    ]}
-  />
-
 
+<TableWithDrawers
+  columns={['Prop', 'Description']}
+  rows={[
+    [
+      {
+        value: '**\\`path\\`**',
+      },
+      {
+        value: 'The path to the array or block field',
+      },
+    ],
+    [
+      {
+        value: '**\\`rowIndex\\`**',
+      },
+      {
+        value: 'The index of the row to remove',
+      },
+    ],
+  ]}
+/>
 
 \`\`\`tsx
 import { useForm } from "@payloadcms/ui"
@@ -493,48 +497,47 @@ import { useForm } from "@payloadcms/ui"
 export const CustomArrayManager = () => {
   const { removeFieldRow } = useForm()
 
-  return (
-    <button
-      type="button"
-      onClick={() => {
-        removeFieldRow({
-          path: "arrayField",
-          rowIndex: 0,
-        })
-      }}
-    >
-      Remove Row
-    </button>
-  )
-}
-\`\`\`
+return (
+
+<button
+  type="button"
+  onClick={() => {
+    removeFieldRow({
+      path: 'arrayField',
+      rowIndex: 0,
+    })
+  }}
+>
+  Remove Row
+</button>
+) } \`\`\`
 
 An example config to go along with the Custom Component
 
 \`\`\`tsx
 const ExampleCollection = {
-  slug: "example-collection",
-  fields: [
-    {
-      name: "arrayField",
-      type: "array",
-      fields: [
-        {
-          name: "textField",
-          type: "text",
-        },
-      ],
-    },
-    {
-      type: "ui",
-      name: "customArrayManager",
-      admin: {
-        components: {
-          Field: '/path/to/CustomArrayManagerField',
-        },
-      },
-    },
-  ],
+slug: "example-collection",
+fields: [
+{
+name: "arrayField",
+type: "array",
+fields: [
+{
+name: "textField",
+type: "text",
+},
+],
+},
+{
+type: "ui",
+name: "customArrayManager",
+admin: {
+components: {
+Field: '/path/to/CustomArrayManagerField',
+},
+},
+},
+],
 }
 \`\`\`
 `
@@ -552,41 +555,36 @@ const ExampleCollection = {
         drawerDescription: 'A useful method to programmatically replace a row from an array or block field.',
         drawerSlug: 'replaceFieldRow',
         drawerContent:  `
-  <TableWithDrawers
-    columns={[
-      'Prop',
-      'Description',
-    ]}
-    rows={[
-      [
-        {
-          value: "**\\\`path\\\`**",
-        },
-        {
-          value: "The path to the array or block field",
-        },
-      ],
-      [
-        {
-          value: "**\\\`rowIndex\\\`**",
-        },
-        {
-          value: "The index of the row to replace",
-        },
-      ],
-      [
-        {
-         value: "**\\\`data\\\`**",
-        },
-        {
-          value: "The data to replace within the row",
-        },
-      ],
-    ]}
-  />
-
-
 
+<TableWithDrawers
+  columns={['Prop', 'Description']}
+  rows={[
+    [
+      {
+        value: '**\\`path\\`**',
+      },
+      {
+        value: 'The path to the array or block field',
+      },
+    ],
+    [
+      {
+        value: '**\\`rowIndex\\`**',
+      },
+      {
+        value: 'The index of the row to replace',
+      },
+    ],
+    [
+      {
+        value: '**\\`data\\`**',
+      },
+      {
+        value: 'The data to replace within the row',
+      },
+    ],
+  ]}
+/>
 
 \`\`\`tsx
 import { useForm } from "@payloadcms/ui"
@@ -594,69 +592,68 @@ import { useForm } from "@payloadcms/ui"
 export const CustomArrayManager = () => {
   const { replaceFieldRow } = useForm()
 
-  return (
-    <button
-      type="button"
-      onClick={() => {
-        replaceFieldRow({
-          path: "arrayField",
-          schemaPath: "arrayField",
-          rowIndex: 0, // optionally specify the index to add the row at
-          subFieldState: {
-            textField: {
-              initialValue: 'Updated text',
-              valid: true,
-              value: 'Upddated text',
-            },
-          },
-          // blockType: "yourBlockSlug",
-          // ^ if managing a block array, you need to specify the block type
-        })
-      }}
-    >
-      Replace Row
-    </button>
-  )
-}
-\`\`\`
+return (
+
+<button
+  type="button"
+  onClick={() => {
+    replaceFieldRow({
+      path: 'arrayField',
+      schemaPath: 'arrayField',
+      rowIndex: 0, // optionally specify the index to add the row at
+      subFieldState: {
+        textField: {
+          initialValue: 'Updated text',
+          valid: true,
+          value: 'Upddated text',
+        },
+      },
+      // blockType: "yourBlockSlug",
+      // ^ if managing a block array, you need to specify the block type
+    })
+  }}
+>
+  Replace Row
+</button>
+) } \`\`\`
 
 An example config to go along with the Custom Component
 
 \`\`\`tsx
 const ExampleCollection = {
-  slug: "example-collection",
-  fields: [
-    {
-      name: "arrayField",
-      type: "array",
-      fields: [
-        {
-          name: "textField",
-          type: "text",
-        },
-      ],
-    },
-    {
-      type: "ui",
-      name: "customArrayManager",
-      admin: {
-        components: {
-          Field: '/path/to/CustomArrayManagerField',
-        },
-      },
-    },
-  ],
+slug: "example-collection",
+fields: [
+{
+name: "arrayField",
+type: "array",
+fields: [
+{
+name: "textField",
+type: "text",
+},
+],
+},
+{
+type: "ui",
+name: "customArrayManager",
+admin: {
+components: {
+Field: '/path/to/CustomArrayManagerField',
+},
+},
+},
+],
 }
 \`\`\`
 `
-      }
-    ],
-  ]}
+}
+],
+]}
 />
 
 ## useDocumentForm
 
-The `useDocumentForm` hook works the same way as the [useForm](#useform) hook, but it always gives you access to the top-level `Form` of a document. This is useful if you need to access the document's `Form` context from within a child  `Form`.
+The `useDocumentForm` hook works the same way as the [useForm](#useform) hook, but it always gives you access to the top-level `Form` of a document. This is useful if you need to access the document's `Form` context from within a child `Form`.
 
 An example where this could happen would be custom components within lexical blocks, as lexical blocks initialize their own child `Form`.
 
@@ -669,7 +666,9 @@ const MyComponent: React.FC = () => {
   const { fields: parentDocumentFields } = useDocumentForm()
 
   return (
-    <p>The document's Form has ${Object.keys(parentDocumentFields).length} fields</p>
+    <p>
+      The document's Form has ${Object.keys(parentDocumentFields).length} fields
+    </p>
   )
 }
 ```
@@ -711,23 +710,41 @@ const CustomComponent: React.FC = () => {
 
 The `useDocumentInfo` hook provides information about the current document being edited, including the following:
 
-| Property                  | Description                                                                                                        |
-| ------------------------- | ------------------------------------------------------------------------------------------------------------------ |
-| **`currentEditor`**       | The user currently editing the document.                                                                             |
-| **`docConfig`**              | Either the Collection or Global config of the document, depending on what is being edited.                         |
-| **`documentIsLocked`**    | Whether the document is currently locked by another user.                                                          |
-| **`id`**                  | If the doc is a collection, its ID will be returned                                                                |
-| **`getDocPermissions`**   | Method to retrieve document-level user preferences.                                                 |
-| **`getDocPreferences`**   | Method to retrieve document-level user preferences.                                                 |
-| **`hasPublishedDoc`**     | Whether the document has a published version.                                                                      |
-| **`incrementVersionCount`** | Method to increment the version count of the document.                                                           |
-| **`preferencesKey`**      | The `preferences` key to use when interacting with document-level user preferences.                                 |
-| **`versions`**            | Versions of the current doc.                                                                                        |
-| **`unpublishedVersions`** | Unpublished versions of the current doc.                                                                            |
-| **`publishedDoc`**        | The currently published version of the doc being edited.                                                            |
-| **`getVersions`**         | Method to retrieve document versions.                                                               |
-| **`docPermissions`**      | The current documents permissions. Collection document permissions fallback when no id is present (i.e. on create). |
-| **`versionCount`**        | The current version count of the document.                                                                          |
+| Property                           | Description                                                                                                                                      |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| **`action`**                       | The URL attached to the action attribute on the underlying form element, which specifies where to send the form data when the form is submitted. |
+| **`apiURL`**                       | The API URL for the current document.                                                                                                            |
+| **`collectionSlug`**               | The slug of the collection if editing a collection document.                                                                                     |
+| **`currentEditor`**                | The user currently editing the document.                                                                                                         |
+| **`docConfig`**                    | Either the Collection or Global config of the document, depending on what is being edited.                                                       |
+| **`docPermissions`**               | The current document's permissions. Fallback to collection permissions when no id is present.                                                    |
+| **`documentIsLocked`**             | Whether the document is currently locked by another user. [More details](./locked-documents).                                                     |
+| **`getDocPermissions`**            | Method to retrieve document-level permissions.                                                                                                   |
+| **`getDocPreferences`**            | Method to retrieve document-level user preferences. [More details](./preferences).                                                               |
+| **`globalSlug`**                   | The slug of the global if editing a global document.                                                                                             |
+| **`hasPublishedDoc`**              | Whether the document has a published version.                                                                                                    |
+| **`hasPublishPermission`**         | Whether the current user has permission to publish the document.                                                                                 |
+| **`hasSavePermission`**            | Whether the current user has permission to save the document.                                                                                    |
+| **`id`**                           | If the doc is a collection, its ID will be returned.                                                                                             |
+| **`incrementVersionCount`**        | Method to increment the version count of the document.                                                                                           |
+| **`initialData`**                  | The initial data of the document.                                                                                                                |
+| **`isEditing`**                    | Whether the document is being edited (as opposed to created).                                                                                    |
+| **`isInitializing`**               | Whether the document info is still initializing.                                                                                                 |
+| **`isLocked`**                     | Whether the document is locked. [More details](./locked-documents).                                                                               |
+| **`lastUpdateTime`**               | Timestamp of the last update to the document.                                                                                                    |
+| **`mostRecentVersionIsAutosaved`** | Whether the most recent version is an autosaved version.                                                                                         |
+| **`preferencesKey`**               | The `preferences` key to use when interacting with document-level user preferences. [More details](./preferences).                               |
+| **`savedDocumentData`**            | The saved data of the document.                                                                                                                  |
+| **`setDocFieldPreferences`**       | Method to set preferences for a specific field. [More details](./preferences).                                                                   |
+| **`setDocumentTitle`**             | Method to set the document title.                                                                                                                |
+| **`setHasPublishedDoc`**           | Method to update whether the document has been published.                                                                                        |
+| **`title`**                        | The title of the document.                                                                                                                       |
+| **`unlockDocument`**               | Method to unlock a document. [More details](./locked-documents).                                                                                  |
+| **`unpublishedVersionCount`**      | The number of unpublished versions of the document.                                                                                              |
+| **`updateDocumentEditor`**         | Method to update who is currently editing the document. [More details](./locked-documents).                                                       |
+| **`updateSavedDocumentData`**      | Method to update the saved document data.                                                                                                        |
+| **`uploadStatus`**                 | Status of any uploads in progress ('idle', 'uploading', or 'failed').                                                                            |
+| **`versionCount`**                 | The current version count of the document.                                                                                                       |
 
 **Example:**
 
@@ -746,7 +763,9 @@ const LinkFromCategoryToPosts: React.FC = () => {
   }
 
   return (
-    <a href={`/admin/collections/posts?where[or][0][and][0][category][in][0]=[${id}]`}>
+    <a
+      href={`/admin/collections/posts?where[or][0][and][0][category][in][0]=[${id}]`}
+    >
       View posts
     </a>
   )
@@ -772,17 +791,18 @@ const MyComponent: React.FC = () => {
 
 The `useListQuery` hook returns an object with the following properties:
 
-| Property          | Description                                                                                   |
-| ----------------- | --------------------------------------------------------------------------------------------- |
-| **`data`**        | The data that is being displayed in the List View.                                           |
-| **`defaultLimit`**| The default limit of items to display in the List View.                                      |
-| **`defaultSort`** | The default sort order of items in the List View.                                             |
-| **`handlePageChange`** | A method to handle page changes in the List View.                                         |
-| **`handlePerPageChange`** | A method to handle per page changes in the List View.                                   |
-| **`handleSearchChange`** | A method to handle search changes in the List View.                                     |
-| **`handleSortChange`** | A method to handle sort changes in the List View.                                         |
-| **`handleWhereChange`** | A method to handle where changes in the List View.                                       |
-| **`query`**       | The current query that is being used to fetch the data in the List View.                             |
+| Property                  | Description                                                                            |
+| ------------------------- | -------------------------------------------------------------------------------------- |
+| **`data`**                | The data that is being displayed in the List View.                                     |
+| **`defaultLimit`**        | The default limit of items to display in the List View.                                |
+| **`defaultSort`**         | The default sort order of items in the List View.                                      |
+| **`handlePageChange`**    | A method to handle page changes in the List View.                                      |
+| **`handlePerPageChange`** | A method to handle per page changes in the List View.                                  |
+| **`handleSearchChange`**  | A method to handle search changes in the List View.                                    |
+| **`handleSortChange`**    | A method to handle sort changes in the List View.                                      |
+| **`handleWhereChange`**   | A method to handle where changes in the List View.                                     |
+| **`modified`**            | Whether the query has been changed from its [Query Preset](../query-presets/overview). |
+| **`query`**               | The current query that is being used to fetch the data in the List View.               |
 
 ## useSelection
 
@@ -811,11 +831,10 @@ const MyComponent: React.FC = () => {
 
   return (
     <>
-      <span>Selected {count} out of {totalDocs} docs!</span>
-      <button
-        type="button"
-        onClick={() => toggleAll(true)}
-      >
+      <span>
+        Selected {count} out of {totalDocs} docs!
+      </span>
+      <button type="button" onClick={() => toggleAll(true)}>
         Toggle All Selections
       </button>
     </>
@@ -899,10 +918,12 @@ import { useConfig } from '@payloadcms/ui'
 const MyComponent: React.FC = () => {
   // highlight-start
   const { getEntityConfig } = useConfig()
-  const mediaConfig = getEntityConfig({ collectionSlug: 'media'})
+  const mediaConfig = getEntityConfig({ collectionSlug: 'media' })
   // highlight-end
 
-  return <span>The media collection has {mediaConfig.fields.length} fields.</span>
+  return (
+    <span>The media collection has {mediaConfig.fields.length} fields.</span>
+  )
 }
 ```
 
@@ -947,7 +968,9 @@ const MyComponent: React.FC = () => {
       </span>
       <button
         type="button"
-        onClick={() => setTheme((prev) => (prev === 'light' ? 'dark' : 'light'))}
+        onClick={() =>
+          setTheme((prev) => (prev === 'light' ? 'dark' : 'light'))
+        }
       >
         Toggle theme
       </button>
@@ -1004,18 +1027,19 @@ const ListenForUpdates: React.FC = () => {
 ```
 
 <Banner type="info">
-  Right now the `useDocumentEvents` hook only tracks recently updated documents, but in the future
-  it will track more document-related events as needed, such as document creation, deletion, etc.
+  Right now the `useDocumentEvents` hook only tracks recently updated documents,
+  but in the future it will track more document-related events as needed, such
+  as document creation, deletion, etc.
 </Banner>
 
 ## useStepNav
 
 The `useStepNav` hook provides a way to change the step-nav breadcrumb links in the app header.
 
-| Property         | Description                                                                       |
-| ---------------- | --------------------------------------------------------------------------------- |
-| **`setStepNav`** | A state setter function which sets the `stepNav` array.                           |
-| **`stepNav`**    | A `StepNavItem` array where each `StepNavItem` has a label and optionally a url.  |
+| Property         | Description                                                                      |
+| ---------------- | -------------------------------------------------------------------------------- |
+| **`setStepNav`** | A state setter function which sets the `stepNav` array.                          |
+| **`stepNav`**    | A `StepNavItem` array where each `StepNavItem` has a label and optionally a url. |
 
 **Example:**
 
@@ -1056,7 +1080,9 @@ const MyComponent: React.FC = () => {
   // Fetch data from a collection item using its ID
   const [{ data, isError, isLoading }, { setParams }] = usePayloadAPI(
     '/api/posts/123',
-    { initialParams: { depth: 1 } }
+    {
+      initialParams: { depth: 1 },
+    },
   )
 
   if (isLoading) return <p>Loading...</p>
@@ -1123,11 +1149,7 @@ By default, any instances of `Link` from `@payloadcms/ui` will trigger route tra
 import { Link } from '@payloadcms/ui'
 
 const MyComponent = () => {
-  return (
-    <Link href="/somewhere">
-      Go Somewhere
-    </Link>
-  )
+  return <Link href="/somewhere">Go Somewhere</Link>
 }
 ```
 

docs/authentication/api-keys.mdx

@@ -16,7 +16,8 @@ For example, if you have a third-party service or external app that needs to be
 <Banner type="success">
   **Tip:**
 
-  This is particularly useful as you can create a "user" that reflects an integration with a specific external service and assign a "role" or specific access only needed by that service/integration.
+This is particularly useful as you can create a "user" that reflects an integration with a specific external service and assign a "role" or specific access only needed by that service/integration.
+
 </Banner>
 
 Technically, both of these options will work for third-party integrations but the second option with API key is simpler, because it reduces the amount of work that your integrations need to do to be authenticated properly.
@@ -42,8 +43,9 @@ your API keys will not be.
   **Important:**
   If you change your `PAYLOAD_SECRET`, you will need to regenerate your API keys.
 
-  The secret key is used to encrypt the API keys, so if you change the secret, existing API keys will
-  no longer be valid.
+The secret key is used to encrypt the API keys, so if you change the secret, existing API keys will
+no longer be valid.
+
 </Banner>
 
 ### HTTP Authentication

docs/authentication/cookies.mdx

@@ -9,8 +9,9 @@ keywords: authentication, config, configuration, documentation, Content Manageme
 Payload offers the ability to [Authenticate](./overview) via HTTP-only cookies. These can be read from the responses of `login`, `logout`, `refresh`, and `me` auth operations.
 
 <Banner type="success">
-  **Tip:**
-  You can access the logged-in user from within [Access Control](../access-control/overview) and [Hooks](../hooks/overview) through the `req.user` argument. [More details](./token-data).
+  **Tip:** You can access the logged-in user from within [Access
+  Control](../access-control/overview) and [Hooks](../hooks/overview) through
+  the `req.user` argument. [More details](./token-data).
 </Banner>
 
 ### Automatic browser inclusion
@@ -34,10 +35,10 @@ const pages = await response.json()
 For more about including cookies in requests from your app to your Payload API, [read the MDN docs](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch#Sending_a_request_with_credentials_included).
 
 <Banner type="success">
-  **Tip:**
-  To make sure you have a Payload cookie set properly in your browser after logging in, you can use
-  the browsers Developer Tools > Application > Cookies > [your-domain-here]. The Developer tools
-  will still show HTTP-only cookies.
+  **Tip:** To make sure you have a Payload cookie set properly in your browser
+  after logging in, you can use the browsers Developer Tools > Application >
+  Cookies > [your-domain-here]. The Developer tools will still show HTTP-only
+  cookies.
 </Banner>
 
 ### CSRF Attacks
@@ -53,8 +54,8 @@ So, if a user of `https://payload-finances.com` is logged in and is browsing aro
 // makes an authenticated request as on your behalf
 
 const maliciousRequest = await fetch(`https://payload-finances.com/api/me`, {
-  credentials: 'include'
-}).then(res => await res.json())
+  credentials: 'include',
+}).then((res) => await res.json())
 ```
 
 In this scenario, if your cookie was still valid, malicious-intent.com would be able to make requests like the one above on your behalf. This is a CSRF attack.
@@ -124,8 +125,8 @@ Configuration example:
 
 If you're configuring [cors](../production/preventing-abuse#cross-origin-resource-sharing-cors) in your Payload config, you won't be able to use a wildcard anymore, you'll need to specify the list of allowed domains.
 
-
 <Banner type="success">
-  **Good to know:**
-  Setting up `secure: true` will not work if you're developing on `http://localhost` or any non-https domain. For local development you should conditionally set this to `false` based on the environment.
+  **Good to know:** Setting up `secure: true` will not work if you're developing
+  on `http://localhost` or any non-https domain. For local development you
+  should conditionally set this to `false` based on the environment.
 </Banner>

docs/authentication/custom-strategies.mdx

@@ -7,8 +7,9 @@ keywords: authentication, config, configuration, overview, documentation, Conten
 ---
 
 <Banner type="warning">
-  This is an advanced feature, so only attempt this if you are an experienced developer. Otherwise,
-  just let Payload's built-in authentication handle user auth for you.
+  This is an advanced feature, so only attempt this if you are an experienced
+  developer. Otherwise, just let Payload's built-in authentication handle user
+  auth for you.
 </Banner>
 
 ### Creating a strategy
@@ -17,19 +18,18 @@ At the core, a strategy is a way to authenticate a user making a request. As of
 
 A strategy is made up of the following:
 
-| Parameter                   | Description                                                               |
-| --------------------------- | ------------------------------------------------------------------------- |
-| **`name`** *               | The name of your strategy                                                 |
-| **`authenticate`** *  | A function that takes in the parameters below and returns a user or null. |
+| Parameter             | Description                                                               |
+| --------------------- | ------------------------------------------------------------------------- |
+| **`name`** \*         | The name of your strategy                                                 |
+| **`authenticate`** \* | A function that takes in the parameters below and returns a user or null. |
 
 The `authenticate` function is passed the following arguments:
 
-| Argument            | Description                                                                                       |
-| ------------------- | ------------------------------------------------------------------------------------------------- |
-| **`headers`** *    | The headers on the incoming request. Useful for retrieving identifiable information on a request. |
-| **`payload`** *    | The Payload class. Useful for authenticating the identifiable information against Payload.        |
-| **`isGraphQL`**     | Whether or not the request was made from a GraphQL endpoint. Default is `false`.                  |
-
+| Argument         | Description                                                                                       |
+| ---------------- | ------------------------------------------------------------------------------------------------- |
+| **`headers`** \* | The headers on the incoming request. Useful for retrieving identifiable information on a request. |
+| **`payload`** \* | The Payload class. Useful for authenticating the identifiable information against Payload.        |
+| **`isGraphQL`**  | Whether or not the request was made from a GraphQL endpoint. Default is `false`.                  |
 
 ### Example Strategy
 
@@ -62,9 +62,12 @@ export const Users: CollectionConfig = {
           })
 
           return {
-            // Send the user back to authenticate,
+            // Send the user with the collection slug back to authenticate,
             // or send null if no user should be authenticated
-            user: usersQuery.docs[0] || null,
+            user: usersQuery.docs[0] ? {
+              collection: 'users'
+              ...usersQuery.docs[0],
+            } : null,
 
             // Optionally, you can return headers
             // that you'd like Payload to set here when

docs/authentication/email.mdx

@@ -20,19 +20,19 @@ import type { CollectionConfig } from 'payload'
 export const Customers: CollectionConfig = {
   // ...
   auth: {
-    verify: true // highlight-line
+    verify: true, // highlight-line
   },
 }
 ```
 
 <Banner type="info">
-  **Tip:**
-  Verification emails are fully customizable. [More details](#generateemailhtml).
+  **Tip:** Verification emails are fully customizable. [More
+  details](#generateemailhtml).
 </Banner>
 
 The following options are available:
 
-| Option                     | Description                                                                                                                                                                                                                         |
+| Option                     | Description                                                                                                                                           |
 | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **`generateEmailHTML`**    | Allows for overriding the HTML within emails that are sent to users indicating how to validate their account. [More details](#generateemailhtml).     |
 | **`generateEmailSubject`** | Allows for overriding the subject of the email that is sent to users indicating how to validate their account. [More details](#generateemailsubject). |
@@ -62,11 +62,11 @@ export const Customers: CollectionConfig = {
 ```
 
 <Banner type="warning">
-  **Important:**
-  If you specify a different URL to send your users to for email verification, such as a page on the
-  frontend of your app or similar, you need to handle making the call to the Payload REST or GraphQL
-  verification operation yourself on your frontend, using the token that was provided for you.
-  Above, it was passed via query parameter.
+  **Important:** If you specify a different URL to send your users to for email
+  verification, such as a page on the frontend of your app or similar, you need
+  to handle making the call to the Payload REST or GraphQL verification
+  operation yourself on your frontend, using the token that was provided for
+  you. Above, it was passed via query parameter.
 </Banner>
 
 #### generateEmailSubject
@@ -82,11 +82,11 @@ export const Customers: CollectionConfig = {
     verify: {
       // highlight-start
       generateEmailSubject: ({ req, user }) => {
-        return `Hey ${user.email}, reset your password!`;
-      }
+        return `Hey ${user.email}, reset your password!`
+      },
       // highlight-end
-    }
-  }
+    },
+  },
 }
 ```
 
@@ -100,7 +100,8 @@ import type { CollectionConfig } from 'payload'
 export const Customers: CollectionConfig = {
   // ...
   auth: {
-    forgotPassword: { // highlight-line
+    forgotPassword: {
+      // highlight-line
       // ...
     },
   },
@@ -109,10 +110,10 @@ export const Customers: CollectionConfig = {
 
 The following options are available:
 
-| Option               | Description                                                                                                                                                                                                                         |
-|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **`expiration`** | Configure how long password reset tokens remain valid, specified in milliseconds. |
-| **`generateEmailHTML`** | Allows for overriding the HTML within emails that are sent to users attempting to reset their password. [More details](#generateEmailHTML). |
+| Option                     | Description                                                                                                                                     |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`expiration`**           | Configure how long password reset tokens remain valid, specified in milliseconds.                                                               |
+| **`generateEmailHTML`**    | Allows for overriding the HTML within emails that are sent to users attempting to reset their password. [More details](#generateEmailHTML).     |
 | **`generateEmailSubject`** | Allows for overriding the subject of the email that is sent to users attempting to reset their password. [More details](#generateEmailSubject). |
 
 #### generateEmailHTML
@@ -152,28 +153,28 @@ export const Customers: CollectionConfig = {
 ```
 
 <Banner type="warning">
-  **Important:**
-  If you specify a different URL to send your users to for resetting their password, such as a page
-  on the frontend of your app or similar, you need to handle making the call to the Payload REST or
-  GraphQL reset-password operation yourself on your frontend, using the token that was provided for
-  you. Above, it was passed via query parameter.
+  **Important:** If you specify a different URL to send your users to for
+  resetting their password, such as a page on the frontend of your app or
+  similar, you need to handle making the call to the Payload REST or GraphQL
+  reset-password operation yourself on your frontend, using the token that was
+  provided for you. Above, it was passed via query parameter.
 </Banner>
 
 <Banner type="success">
-  **Tip:**
-  HTML templating can be used to create custom email templates, inline CSS automatically, and more.
-  You can make a reusable function that standardizes all email sent from Payload, which makes
-  sending custom emails more DRY. Payload doesn't ship with an HTML templating engine, so you are
-  free to choose your own.
+  **Tip:** HTML templating can be used to create custom email templates, inline
+  CSS automatically, and more. You can make a reusable function that
+  standardizes all email sent from Payload, which makes sending custom emails
+  more DRY. Payload doesn't ship with an HTML templating engine, so you are free
+  to choose your own.
 </Banner>
 
 The following arguments are passed to the `generateEmailHTML` function:
 
-| Argument | Description                                                                                   |
-|----------|-----------------------------------------------------------------------------------------------|
-| `req`    | The request object.                                                                           |
-| `token`  | The token that is generated for the user to reset their password.                             |
-| `user`   | The user document that is attempting to reset their password.                                 |
+| Argument | Description                                                       |
+| -------- | ----------------------------------------------------------------- |
+| `req`    | The request object.                                               |
+| `token`  | The token that is generated for the user to reset their password. |
+| `user`   | The user document that is attempting to reset their password.     |
 
 #### generateEmailSubject
 
@@ -188,17 +189,17 @@ export const Customers: CollectionConfig = {
     forgotPassword: {
       // highlight-start
       generateEmailSubject: ({ req, user }) => {
-        return `Hey ${user.email}, reset your password!`;
-      }
+        return `Hey ${user.email}, reset your password!`
+      },
       // highlight-end
-    }
-  }
+    },
+  },
 }
 ```
 
 The following arguments are passed to the `generateEmailSubject` function:
 
-| Argument | Description                                                                                   |
-|----------|-----------------------------------------------------------------------------------------------|
-| `req`    | The request object.                                                                           |
-| `user`   | The user document that is attempting to reset their password.                                 |
+| Argument | Description                                                   |
+| -------- | ------------------------------------------------------------- |
+| `req`    | The request object.                                           |
+| `user`   | The user document that is attempting to reset their password. |

docs/authentication/jwt.mdx

@@ -9,8 +9,9 @@ keywords: authentication, config, configuration, documentation, Content Manageme
 Payload offers the ability to [Authenticate](./overview) via JSON Web Tokens (JWT). These can be read from the responses of `login`, `logout`, `refresh`, and `me` auth operations.
 
 <Banner type="success">
-  **Tip:**
-  You can access the logged-in user from within [Access Control](../access-control/overview) and [Hooks](../hooks/overview) through the `req.user` argument. [More details](./token-data).
+  **Tip:** You can access the logged-in user from within [Access
+  Control](../access-control/overview) and [Hooks](../hooks/overview) through
+  the `req.user` argument. [More details](./token-data).
 </Banner>
 
 ### Identifying Users Via The Authorization Header
@@ -25,8 +26,8 @@ const user = await fetch('http://localhost:3000/api/users/login', {
   body: JSON.stringify({
     email: 'dev@payloadcms.com',
     password: 'password',
-  })
-}).then(req => await req.json())
+  }),
+}).then((req) => await req.json())
 
 const request = await fetch('http://localhost:3000', {
   headers: {

docs/authentication/operations.mdx

@@ -200,12 +200,15 @@ If successful, this operation will automatically renew the user's HTTP-only cook
 **Example REST API token refresh**:
 
 ```ts
-const res = await fetch('http://localhost:3000/api/[collection-slug]/refresh-token', {
-  method: 'POST',
-  headers: {
-    'Content-Type': 'application/json',
+const res = await fetch(
+  'http://localhost:3000/api/[collection-slug]/refresh-token',
+  {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/json',
+    },
   },
-})
+)
 
 const json = await res.json()
 
@@ -244,12 +247,15 @@ If your collection supports email verification, the Verify operation will be exp
 **Example REST API user verification**:
 
 ```ts
-const res = await fetch(`http://localhost:3000/api/[collection-slug]/verify/${TOKEN_HERE}`, {
-  method: 'POST',
-  headers: {
-    'Content-Type': 'application/json',
+const res = await fetch(
+  `http://localhost:3000/api/[collection-slug]/verify/${TOKEN_HERE}`,
+  {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/json',
+    },
   },
-})
+)
 ```
 
 **Example GraphQL Mutation**:
@@ -317,15 +323,18 @@ By default, the Forgot Password operations send users to the [Admin Panel](../ad
 **Example REST API Forgot Password**:
 
 ```ts
-const res = await fetch(`http://localhost:3000/api/[collection-slug]/forgot-password`, {
-  method: 'POST',
-  headers: {
-    'Content-Type': 'application/json',
+const res = await fetch(
+  `http://localhost:3000/api/[collection-slug]/forgot-password`,
+  {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/json',
+    },
+    body: JSON.stringify({
+      email: 'dev@payloadcms.com',
+    }),
   },
-  body: JSON.stringify({
-    email: 'dev@payloadcms.com',
-  }),
-})
+)
 ```
 
 **Example GraphQL Mutation**:
@@ -344,22 +353,29 @@ const token = await payload.forgotPassword({
   data: {
     email: 'dev@payloadcms.com',
   },
-  disableEmail: false, // you can disable the auto-generation of email via local API
+  disableEmail: false, // you can disable the auto-generation of email via Local API
 })
 ```
 
 <Banner type="info">
-  **Note:** if you do not have a `config.serverURL` set, Payload will attempt to create one for you if the `forgot-password` operation was triggered via REST or GraphQL by looking at the incoming `req`. But this is not supported if you are calling `payload.forgotPassword()` via the Local API. If you do not have a `serverURL` set, you may want to override your `auth.forgotPassword.generateEmailHTML` function to provide a full URL to link the user to a proper reset-password page.
+  **Note:** if you do not have a `config.serverURL` set, Payload will attempt to
+  create one for you if the `forgot-password` operation was triggered via REST
+  or GraphQL by looking at the incoming `req`. But this is not supported if you
+  are calling `payload.forgotPassword()` via the Local API. If you do not have a
+  `serverURL` set, you may want to override your
+  `auth.forgotPassword.generateEmailHTML` function to provide a full URL to link
+  the user to a proper reset-password page.
 </Banner>
 
 <Banner type="success">
   **Tip:**
 
-  You can stop the reset-password email from being sent via using the local API. This is helpful if
-  you need to create user accounts programmatically, but not set their password for them. This
-  effectively generates a reset password token which you can then use to send to a page you create,
-  allowing a user to "complete" their account by setting their password. In the background, you'd
-  use the token to "reset" their password.
+You can stop the reset-password email from being sent via using the Local API. This is helpful if
+you need to create user accounts programmatically, but not set their password for them. This
+effectively generates a reset password token which you can then use to send to a page you create,
+allowing a user to "complete" their account by setting their password. In the background, you'd
+use the token to "reset" their password.
+
 </Banner>
 
 ## Reset Password

docs/authentication/overview.mdx

@@ -41,8 +41,9 @@ _Admin Panel screenshot depicting an Admins Collection with Auth enabled_
 Any [Collection](../configuration/collections) can opt-in to supporting Authentication. Once enabled, each Document that is created within the Collection can be thought of as a "user". This enables a complete authentication workflow on your Collection, such as logging in and out, resetting their password, and more.
 
 <Banner type="warning">
-  **Note:**
-  By default, Payload provides an auth-enabled `User` Collection which is used to access the Admin Panel. [More details](../admin/overview#the-admin-user-collection).
+  **Note:** By default, Payload provides an auth-enabled `User` Collection which
+  is used to access the Admin Panel. [More
+  details](../admin/overview#the-admin-user-collection).
 </Banner>
 
 To enable Authentication on a Collection, use the `auth` property in the [Collection Config](../configuration/collections):
@@ -65,31 +66,32 @@ export const Admins: CollectionConfig = {
 ```
 
 <Banner type="info">
-  **Tip:**
-  For default auth behavior, set `auth: true`. This is a good starting point for most applications.
+  **Tip:** For default auth behavior, set `auth: true`. This is a good starting
+  point for most applications.
 </Banner>
 
 <Banner type="warning">
-  **Note:**
-  Auth-enabled Collections with be automatically injected with the `hash`, `salt`, and `email` fields. [More details](../fields/overview#field-names).
+  **Note:** Auth-enabled Collections with be automatically injected with the
+  `hash`, `salt`, and `email` fields. [More
+  details](../fields/overview#field-names).
 </Banner>
 
 The following options are available:
 
-| Option                     | Description                                                                                                                                                                                                                         |
-|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **`cookies`**              | Set cookie options, including `secure`, `sameSite`, and `domain`. For advanced users.                                                                                                                                               |
-| **`depth`**                | How many levels deep a `user` document should be populated when creating the JWT and binding the `user` to the `req`. Defaults to `0` and should only be modified if absolutely necessary, as this will affect performance. |
-| **`disableLocalStrategy`** | Advanced - disable Payload's built-in local auth strategy. Only use this property if you have replaced Payload's auth mechanisms with your own.                                                                                     |
-| **`forgotPassword`**       | Customize the way that the `forgotPassword` operation functions. [More details](./email#forgot-password).                                                                                                             |
-| **`lockTime`**             | Set the time (in milliseconds) that a user should be locked out if they fail authentication more times than `maxLoginAttempts` allows for.                                                                                          |
-| **`loginWithUsername`**    | Ability to allow users to login with username/password. [More](/docs/authentication/overview#login-with-username)                                                                                                                     |
-| **`maxLoginAttempts`**     | Only allow a user to attempt logging in X amount of times. Automatically locks out a user from authenticating if this limit is passed. Set to `0` to disable.                                                                       |
-| **`removeTokenFromResponses`** | Set to true if you want to remove the token from the returned authentication API responses such as login or refresh.                                                                                                                                                            |
-| **`strategies`**           | Advanced - an array of custom authentication strategies to extend this collection's authentication with. [More details](./custom-strategies).                                                                         |
-| **`tokenExpiration`**      | How long (in seconds) to keep the user logged in. JWTs and HTTP-only cookies will both expire at the same time.                                                                                                                     |
-| **`useAPIKey`**            | Payload Authentication provides for API keys to be set on each user within an Authentication-enabled Collection. [More details](./api-keys).                                                                       |
-| **`verify`**               | Set to `true` or pass an object with verification options to require users to verify by email before they are allowed to log into your app. [More details](./email#email-verification).                                  |
+| Option                         | Description                                                                                                                                                                                                                 |
+| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`cookies`**                  | Set cookie options, including `secure`, `sameSite`, and `domain`. For advanced users.                                                                                                                                       |
+| **`depth`**                    | How many levels deep a `user` document should be populated when creating the JWT and binding the `user` to the `req`. Defaults to `0` and should only be modified if absolutely necessary, as this will affect performance. |
+| **`disableLocalStrategy`**     | Advanced - disable Payload's built-in local auth strategy. Only use this property if you have replaced Payload's auth mechanisms with your own.                                                                             |
+| **`forgotPassword`**           | Customize the way that the `forgotPassword` operation functions. [More details](./email#forgot-password).                                                                                                                   |
+| **`lockTime`**                 | Set the time (in milliseconds) that a user should be locked out if they fail authentication more times than `maxLoginAttempts` allows for.                                                                                  |
+| **`loginWithUsername`**        | Ability to allow users to login with username/password. [More](/docs/authentication/overview#login-with-username)                                                                                                           |
+| **`maxLoginAttempts`**         | Only allow a user to attempt logging in X amount of times. Automatically locks out a user from authenticating if this limit is passed. Set to `0` to disable.                                                               |
+| **`removeTokenFromResponses`** | Set to true if you want to remove the token from the returned authentication API responses such as login or refresh.                                                                                                        |
+| **`strategies`**               | Advanced - an array of custom authentication strategies to extend this collection's authentication with. [More details](./custom-strategies).                                                                               |
+| **`tokenExpiration`**          | How long (in seconds) to keep the user logged in. JWTs and HTTP-only cookies will both expire at the same time.                                                                                                             |
+| **`useAPIKey`**                | Payload Authentication provides for API keys to be set on each user within an Authentication-enabled Collection. [More details](./api-keys).                                                                                |
+| **`verify`**                   | Set to `true` or pass an object with verification options to require users to verify by email before they are allowed to log into your app. [More details](./email#email-verification).                                     |
 
 ### Login With Username
 
@@ -153,14 +155,15 @@ export default buildConfig({
 ```
 
 <Banner type="warning">
-  **Warning:**
-  The recommended way to use this feature is behind an [Environment Variable](../configuration/environment-vars). This will ensure it is _disabled_ in production.
+  **Warning:** The recommended way to use this feature is behind an [Environment
+  Variable](../configuration/environment-vars). This will ensure it is
+  _disabled_ in production.
 </Banner>
 
 The following options are available:
 
 | Option            | Description                                                                                                     |
-|-------------------|-----------------------------------------------------------------------------------------------------------------|
+| ----------------- | --------------------------------------------------------------------------------------------------------------- |
 | **`username`**    | The username of the user to login as                                                                            |
 | **`email`**       | The email address of the user to login as                                                                       |
 | **`password`**    | The password of the user to login as. This is only needed if `prefillOnly` is set to true                       |

docs/authentication/token-data.mdx

@@ -24,10 +24,7 @@ export const Users: CollectionConfig = {
       saveToJWT: true,
       type: 'select',
       name: 'role',
-      options: [
-        'super-admin',
-        'user',
-      ]
+      options: ['super-admin', 'user'],
     },
     {
       // the entire object will be stored in the JWT
@@ -46,7 +43,7 @@ export const Users: CollectionConfig = {
           type: 'text',
           name: 'omitField',
         },
-      ]
+      ],
     },
     {
       type: 'group',
@@ -63,18 +60,18 @@ export const Users: CollectionConfig = {
           type: 'text',
           name: 'omitField',
         },
-      ]
+      ],
     },
-  ]
+  ],
 }
 ```
 
 <Banner type="success">
   **Tip:**
 
-  If you wish to use a different key other than the field `name`, you can define `saveToJWT` as a string.
-</Banner>
+If you wish to use a different key other than the field `name`, you can define `saveToJWT` as a string.
 
+</Banner>
 
 ### Using Token Data
 

docs/cloud/configuration.mdx

@@ -11,10 +11,10 @@ keywords: configuration, config, settings, project, cloud, payload cloud, deploy
 Once you have created a project, you will need to select your plan. This will determine the resources that are allocated to your project and the features that are available to you.
 
 <Banner type="success">
-  Note: All Payload Cloud teams that deploy a project require a card on file. This helps us prevent
-  fraud and abuse on our platform. If you select a plan with a free trial, you will not be charged
-  until your trial period is over. We’ll remind you 7 days before your trial ends and you can cancel
-  anytime.
+  Note: All Payload Cloud teams that deploy a project require a card on file.
+  This helps us prevent fraud and abuse on our platform. If you select a plan
+  with a free trial, you will not be charged until your trial period is over.
+  We’ll remind you 7 days before your trial ends and you can cancel anytime.
 </Banner>
 
 ## Project Details
@@ -44,8 +44,8 @@ If you are deploying a new project from a template, the following settings will
 Any of the features in Payload Cloud that require environment variables will automatically be provided to your application. If your app requires any custom environment variables, you can set them here.
 
 <Banner type="warning">
-  Note: For security reasons, any variables you wish to provide to the [Admin Panel](../admin/overview) must be prefixed
-  with `NEXT_PUBLIC_`.  Learn more
+  Note: For security reasons, any variables you wish to provide to the [Admin
+  Panel](../admin/overview) must be prefixed with `NEXT_PUBLIC_`.  Learn more
   [here](../configuration/environment-vars).
 </Banner>
 
@@ -54,8 +54,9 @@ Any of the features in Payload Cloud that require environment variables will aut
 Payment methods can be set per project and can be updated any time. You can use team’s default payment method, or add a new one. Modify your payment methods in your Project settings / Team settings.
 
 <Banner type="success">
-  **Note:** All Payload Cloud teams that deploy a project require a card on file. This
-  helps us prevent fraud and abuse on our platform. If you select a plan with a free trial, you will
-  not be charged until your trial period is over. We’ll remind you 7 days before your trial ends and
-  you can cancel anytime.
+  **Note:** All Payload Cloud teams that deploy a project require a card on
+  file. This helps us prevent fraud and abuse on our platform. If you select a
+  plan with a free trial, you will not be charged until your trial period is
+  over. We’ll remind you 7 days before your trial ends and you can cancel
+  anytime.
 </Banner>

docs/cloud/creating-a-project.mdx

@@ -13,8 +13,9 @@ Payload Cloud offers various plans tailored to meet your specific needs, includi
 To get started, you first need to create an account. Head over to [the login screen](https://payloadcms.com/login) and **Register for Free**.
 
 <Banner type="success">
-  To create your first project, you can either select [a template](#starting-from-a-template) or
-  [import an existing project](#importing-from-an-existing-codebase) from GitHub.
+  To create your first project, you can either select [a
+  template](#starting-from-a-template) or [import an existing
+  project](#importing-from-an-existing-codebase) from GitHub.
 </Banner>
 
 ## Starting from a Template
@@ -45,7 +46,8 @@ Payload Cloud works for any Node.js + MongoDB app. From the New Project page, se
 _Creating a new project from an existing repository._
 
 <Banner type="warning">
-  **Note:** In order to make use of the features of Payload Cloud in your own codebase,
-  you will need to add the [Cloud Plugin](https://github.com/payloadcms/payload/tree/main/packages/payload-cloud) to your
-  Payload app.
+  **Note:** In order to make use of the features of Payload Cloud in your own
+  codebase, you will need to add the [Cloud
+  Plugin](https://github.com/payloadcms/payload/tree/main/packages/payload-cloud)
+  to your Payload app.
 </Banner>

docs/cloud/projects.mdx

@@ -9,10 +9,11 @@ keywords: cloud, payload cloud, projects, project, overview, database, file stor
 ## Overview
 
 <Banner>
-  The overview tab shows your most recent deployment, along with build and deployment logs. From
-  here, you can see your live URL, deployment details like timestamps and commit hash, as well as
-  the status of your deployment. You can also trigger a redeployment manually, which will rebuild
-  your project using the current configuration.
+  The overview tab shows your most recent deployment, along with build and
+  deployment logs. From here, you can see your live URL, deployment details like
+  timestamps and commit hash, as well as the status of your deployment. You can
+  also trigger a redeployment manually, which will rebuild your project using
+  the current configuration.
 </Banner>
 
 ![Payload Cloud Overview Page](https://payloadcms.com/images/docs/cloud/overview-page.jpg)
@@ -59,7 +60,9 @@ You can update settings from your Project’s Settings tab. Changes to your buil
 From the Environment Variables page of the Settings tab, you can add, update and delete variables for use in your project. Like build settings, these changes will trigger a redeployment of your project.
 
 <Banner>
-  Note: For security reasons, any variables you wish to provide to the [Admin Panel](../admin/overview) must be prefixed with `NEXT_PUBLIC_`. [More details](../configuration/environment-vars).
+  Note: For security reasons, any variables you wish to provide to the [Admin
+  Panel](../admin/overview) must be prefixed with `NEXT_PUBLIC_`. [More
+  details](../configuration/environment-vars).
 </Banner>
 
 ## Custom Domains
@@ -67,8 +70,9 @@ From the Environment Variables page of the Settings tab, you can add, update and
 With Payload Cloud, you can add custom domain names to your project. To do so, first go to the Domains page of the Settings tab of your project. Here you can see your default domain. To add a new domain, type in the domain name you wish to use.
 
 <Banner>
-  Note: do not include the protocol (http:// or https://) or any paths (/page). Only include the
-  domain name and extension, and optionally a subdomain. - your-domain.com - backend.your-domain.com
+  Note: do not include the protocol (http:// or https://) or any paths (/page).
+  Only include the domain name and extension, and optionally a subdomain. -
+  your-domain.com - backend.your-domain.com
 </Banner>
 
 Once you click save, a DNS record will be generated for your domain name to point to your live project. Add this record into your DNS provider’s records, and once the records are resolving properly (this can take 1hr to 48hrs in some cases), your domain will now to point to your live project.
@@ -111,13 +115,14 @@ export default buildConfig({
 ```
 
 <Banner type="warning">
-  **Note:** If your Payload Config already has an email with transport, this will take precedence
-  over Payload Cloud's email service.
+  **Note:** If your Payload Config already has an email with transport, this
+  will take precedence over Payload Cloud's email service.
 </Banner>
 
 <Banner type="info">
-  Good to know: the Payload Cloud Plugin was previously named `@payloadcms/plugin-cloud`. If you are
-  using this plugin, you should update to the new package name.
+  Good to know: the Payload Cloud Plugin was previously named
+  `@payloadcms/plugin-cloud`. If you are using this plugin, you should update to
+  the new package name.
 </Banner>
 
 #### **Optional configuration**

docs/cloud/teams.mdx

@@ -7,8 +7,8 @@ keywords: team, teams, billing, subscription, payment, plan, plans, cloud, paylo
 ---
 
 <Banner>
-  Within Payload Cloud, the team management feature offers you the ability to manage your
-  organization, team members, billing, and subscription settings.
+  Within Payload Cloud, the team management feature offers you the ability to
+  manage your organization, team members, billing, and subscription settings.
 </Banner>
 
 ![Payload Cloud Team Settings](https://payloadcms.com/images/docs/cloud/team-settings.jpg)

docs/configuration/collections.mdx

@@ -19,15 +19,16 @@ import { buildConfig } from 'payload'
 
 export default buildConfig({
   // ...
-  collections: [ // highlight-line
+  collections: [
+    // highlight-line
     // Your Collections go here
   ],
 })
 ```
 
 <Banner type="success">
-  **Tip:**
-  If your Collection is only ever meant to contain a single Document, consider using a [Global](./globals) instead.
+  **Tip:** If your Collection is only ever meant to contain a single Document,
+  consider using a [Global](./globals) instead.
 </Banner>
 
 ## Config Options
@@ -45,41 +46,46 @@ export const Posts: CollectionConfig = {
     {
       name: 'title',
       type: 'text',
-    }
-  ]
+    },
+  ],
 }
 ```
 
 <Banner type="success">
-  **Reminder:**
-  For more complex examples, see the [Templates](https://github.com/payloadcms/payload/tree/main/templates) and [Examples](https://github.com/payloadcms/payload/tree/main/examples) directories in the Payload repository.
+  **Reminder:** For more complex examples, see the
+  [Templates](https://github.com/payloadcms/payload/tree/main/templates) and
+  [Examples](https://github.com/payloadcms/payload/tree/main/examples)
+  directories in the Payload repository.
 </Banner>
 
 The following options are available:
 
-| Option                 | Description                                                                                                                                                                                                          |
-| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `admin`            | The configuration options for the Admin Panel. [More details](#admin-options).                                                                                                                                 |
-| `access`           | Provide Access Control functions to define exactly who should be able to do what with Documents in this Collection. [More details](../access-control/collections).                                                   |
-| `auth`             | Specify options if you would like this Collection to feature authentication. [More details](../authentication/overview).                                                                                             |
-| `custom`           | Extension point for adding custom data (e.g. for plugins)                                                                                                                                                            |
-| `disableDuplicate` | When true, do not show the "Duplicate" button while editing documents within this Collection and prevent `duplicate` from all APIs.                                                                                  |
-| `defaultSort`      | Pass a top-level field to sort by default in the Collection List View. Prefix the name of the field with a minus symbol ("-") to sort in descending order. Multiple fields can be specified by using a string array. |
-| `dbName`           | Custom table or Collection name depending on the Database Adapter. Auto-generated from slug if not defined.                                                                                                          |
-| `endpoints`        | Add custom routes to the REST API. Set to `false` to disable routes. [More details](../rest-api/overview#custom-endpoints).                                                                                          |
-| `fields` *        | Array of field types that will determine the structure and functionality of the data stored within this Collection. [More details](../fields/overview).                                                              |
-| `graphQL`          | Manage GraphQL-related properties for this collection. [More](#graphql)                                                                                                                                              |
-| `hooks`            | Entry point for Hooks. [More details](../hooks/overview#collection-hooks).                                                                                                                                           |
-| `labels`           | Singular and plural labels for use in identifying this Collection throughout Payload. Auto-generated from slug if not defined.                                                                                       |
-| `lockDocuments`    | Enables or disables document locking. By default, document locking is enabled. Set to an object to configure, or set to `false` to disable locking. [More details](../admin/locked-documents).                       |
-| `slug` *          | Unique, URL-friendly string that will act as an identifier for this Collection.                                                                                                                                      |
-| `timestamps`       | Set to false to disable documents' automatically generated `createdAt` and `updatedAt` timestamps.                                                                                                                   |
-| `typescript`       | An object with property `interface` as the text used in schema generation. Auto-generated from slug if not defined.                                                                                                  |
-| `upload`           | Specify options if you would like this Collection to support file uploads. For more, consult the [Uploads](../upload/overview) documentation.                                                                        |
-| `versions`         | Set to true to enable default options, or configure with object properties. [More details](../versions/overview#collection-config).                                                                                  |
-| `defaultPopulate`  | Specify which fields to select when this Collection is populated from another document. [More Details](../queries/select#defaultpopulate-collection-config-property).                                                |
+| Option               | Description                                                                                                                                                                                                          |
+| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `admin`              | The configuration options for the Admin Panel. [More details](#admin-options).                                                                                                                                       |
+| `access`             | Provide Access Control functions to define exactly who should be able to do what with Documents in this Collection. [More details](../access-control/collections).                                                   |
+| `auth`               | Specify options if you would like this Collection to feature authentication. [More details](../authentication/overview).                                                                                             |
+| `custom`             | Extension point for adding custom data (e.g. for plugins)                                                                                                                                                            |
+| `disableDuplicate`   | When true, do not show the "Duplicate" button while editing documents within this Collection and prevent `duplicate` from all APIs.                                                                                  |
+| `defaultSort`        | Pass a top-level field to sort by default in the Collection List View. Prefix the name of the field with a minus symbol ("-") to sort in descending order. Multiple fields can be specified by using a string array. |
+| `dbName`             | Custom table or Collection name depending on the Database Adapter. Auto-generated from slug if not defined.                                                                                                          |
+| `endpoints`          | Add custom routes to the REST API. Set to `false` to disable routes. [More details](../rest-api/overview#custom-endpoints).                                                                                          |
+| `fields` \*          | Array of field types that will determine the structure and functionality of the data stored within this Collection. [More details](../fields/overview).                                                              |
+| `graphQL`            | Manage GraphQL-related properties for this collection. [More](#graphql)                                                                                                                                              |
+| `hooks`              | Entry point for Hooks. [More details](../hooks/overview#collection-hooks).                                                                                                                                           |
+| `labels`             | Singular and plural labels for use in identifying this Collection throughout Payload. Auto-generated from slug if not defined.                                                                                       |
+| `enableQueryPresets` | Enable query presets for this Collection. [More details](../query-presets/overview).                                                                                                                                 |
+| `lockDocuments`      | Enables or disables document locking. By default, document locking is enabled. Set to an object to configure, or set to `false` to disable locking. [More details](../admin/locked-documents).                       |
+| `slug` \*            | Unique, URL-friendly string that will act as an identifier for this Collection.                                                                                                                                      |
+| `timestamps`         | Set to false to disable documents' automatically generated `createdAt` and `updatedAt` timestamps.                                                                                                                   |
+| `typescript`         | An object with property `interface` as the text used in schema generation. Auto-generated from slug if not defined.                                                                                                  |
+| `upload`             | Specify options if you would like this Collection to support file uploads. For more, consult the [Uploads](../upload/overview) documentation.                                                                        |
+| `versions`           | Set to true to enable default options, or configure with object properties. [More details](../versions/overview#collection-config).                                                                                  |
+| `defaultPopulate`    | Specify which fields to select when this Collection is populated from another document. [More Details](../queries/select#defaultpopulate-collection-config-property).                                                |
+| `indexes`            | Define compound indexes for this collection. This can be used to either speed up querying/sorting by 2 or more fields at the same time or to ensure uniqueness between several fields.                               |
+| `forceSelect`        | Specify which fields should be selected always, regardless of the `select` query which can be useful that the field exists for access control / hooks                                                                |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ### Fields
 
@@ -104,7 +110,8 @@ import type { CollectionConfig } from 'payload'
 
 export const MyCollection: CollectionConfig = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -112,19 +119,20 @@ export const MyCollection: CollectionConfig = {
 
 The following options are available:
 
-| Option                           | Description                                                                                                                                                                                                                  |
-| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Option                       | Description                                                                                                                                                                                                                  |
+| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `group`                      | Text or localization object used to group Collection and Global links in the admin navigation. Set to `false` to hide the link from the navigation while keeping its routes accessible.                                      |
 | `hidden`                     | Set to true or a function, called with the current user, returning true to exclude this Collection from navigation and admin routing.                                                                                        |
 | `hooks`                      | Admin-specific hooks for this Collection. [More details](../hooks/collections).                                                                                                                                              |
 | `useAsTitle`                 | Specify a top-level field to use for a document title throughout the Admin Panel. If no field is defined, the ID of the document is used as the title. A field with `virtual: true` cannot be used as the title.             |
 | `description`                | Text to display below the Collection label in the List View to give editors more information. Alternatively, you can use the `admin.components.Description` to render a React component. [More details](#custom-components). |
 | `defaultColumns`             | Array of field names that correspond to which columns to show by default in this Collection's List View.                                                                                                                     |
+| `disableCopyToLocale`        | Disables the "Copy to Locale" button while editing documents within this Collection. Only applicable when localization is enabled.                                                                                           |
 | `hideAPIURL`                 | Hides the "API URL" meta field while editing documents within this Collection.                                                                                                                                               |
 | `enableRichTextLink`         | The [Rich Text](../fields/rich-text) field features a `Link` element which allows for users to automatically reference related documents within their rich text. Set to `true` by default.                                   |
 | `enableRichTextRelationship` | The [Rich Text](../fields/rich-text) field features a `Relationship` element which allows for users to automatically reference related documents within their rich text. Set to `true` by default.                           |
-| `meta`                       | Page metadata overrides to apply to this Collection within the Admin Panel. [More details](../admin/metadata).                                                                                                                      |
-| `preview`                    | Function to generate preview URLs within the Admin Panel that can point to your app. [More details](../admin/preview).                                                                                                               |
+| `meta`                       | Page metadata overrides to apply to this Collection within the Admin Panel. [More details](../admin/metadata).                                                                                                               |
+| `preview`                    | Function to generate preview URLs within the Admin Panel that can point to your app. [More details](../admin/preview).                                                                                                       |
 | `livePreview`                | Enable real-time editing for instant visual feedback of your front-end application. [More details](../live-preview/overview).                                                                                                |
 | `components`                 | Swap in your own React components to be used within this Collection. [More details](#custom-components).                                                                                                                     |
 | `listSearchableFields`       | Specify which fields should be searched in the List search view. [More details](#list-searchable-fields).                                                                                                                    |
@@ -143,7 +151,8 @@ import type { CollectionConfig } from 'payload'
 export const MyCollection: CollectionConfig = {
   // ...
   admin: {
-    components: { // highlight-line
+    components: {
+      // highlight-line
       // ...
     },
   },
@@ -152,16 +161,16 @@ export const MyCollection: CollectionConfig = {
 
 The following options are available:
 
-| Option                | Description                                                                                                                                                                        |
-| --------------------- |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `afterList`           | An array of components to inject _after_ the built-in List View. [More details](../custom-components/list-view#afterlist).                                                         |
-| `afterListTable`      | An array of components to inject _after_ the built-in List View's table. [More details](../custom-components/list-view#afterlisttable).                                            |
-| `beforeList`          | An array of components to inject _before_ the built-in List View. [More details](../custom-components/list-view#beforelist).                                                       |
-| `beforeListTable`     | An array of components to inject _before_ the built-in List View's table. [More details](../custom-components/list-view#beforelisttable).                                          |
-| `listMenuItems`       | An array of components to render within a menu next to the List Controls (after the Columns and Filters options)                                                                   |
-| `Description`         | A component to render below the Collection label in the List View. An alternative to the `admin.description` property. [More details](../custom-components/list-view#description). |
-| `edit`                | Override specific components within the Edit View. [More details](#edit-view-options).                                                                                             |
-| `views`               | Override or create new views within the Admin Panel. [More details](../custom-components/custom-views).                                                                            |
+| Option            | Description                                                                                                                                                                        |
+| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `afterList`       | An array of components to inject _after_ the built-in List View. [More details](../custom-components/list-view#afterlist).                                                         |
+| `afterListTable`  | An array of components to inject _after_ the built-in List View's table. [More details](../custom-components/list-view#afterlisttable).                                            |
+| `beforeList`      | An array of components to inject _before_ the built-in List View. [More details](../custom-components/list-view#beforelist).                                                       |
+| `beforeListTable` | An array of components to inject _before_ the built-in List View's table. [More details](../custom-components/list-view#beforelisttable).                                          |
+| `listMenuItems`   | An array of components to render within a menu next to the List Controls (after the Columns and Filters options)                                                                   |
+| `Description`     | A component to render below the Collection label in the List View. An alternative to the `admin.description` property. [More details](../custom-components/list-view#description). |
+| `edit`            | Override specific components within the Edit View. [More details](#edit-view-options).                                                                                             |
+| `views`           | Override or create new views within the Admin Panel. [More details](../custom-components/custom-views).                                                                            |
 
 #### Edit View Options
 
@@ -172,7 +181,8 @@ export const MyCollection: CollectionCOnfig = {
   // ...
   admin: {
     components: {
-      edit: { // highlight-line
+      edit: {
+        // highlight-line
         // ...
       },
     },
@@ -182,17 +192,17 @@ export const MyCollection: CollectionCOnfig = {
 
 The following options are available:
 
-| Option                 | Description                                                                                                                                |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| `SaveButton`      | Replace the default Save Button within the Edit View. [Drafts](../versions/drafts) must be disabled. [More details](../custom-components/edit-view#save-button). |
+| Option            | Description                                                                                                                                                                                               |
+| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `SaveButton`      | Replace the default Save Button within the Edit View. [Drafts](../versions/drafts) must be disabled. [More details](../custom-components/edit-view#save-button).                                          |
 | `SaveDraftButton` | Replace the default Save Draft Button within the Edit View. [Drafts](../versions/drafts) must be enabled and autosave must be disabled. [More details](../custom-components/edit-view#save-draft-button). |
-| `PublishButton`   | Replace the default Publish Button within the Edit View. [Drafts](../versions/drafts) must be enabled. [More details](../custom-components/edit-view#publish-button). |
-| `PreviewButton`   | Replace the default Preview Button within the Edit View. [Preview](../admin/preview) must be enabled. [More details](../custom-components/edit-view#preview-button). |
-| `Upload`          | Replace the default Upload component within the Edit View. [Upload](../upload/overview) must be enabled. [More details](../custom-components/edit-view#upload). |
+| `PublishButton`   | Replace the default Publish Button within the Edit View. [Drafts](../versions/drafts) must be enabled. [More details](../custom-components/edit-view#publish-button).                                     |
+| `PreviewButton`   | Replace the default Preview Button within the Edit View. [Preview](../admin/preview) must be enabled. [More details](../custom-components/edit-view#preview-button).                                      |
+| `Upload`          | Replace the default Upload component within the Edit View. [Upload](../upload/overview) must be enabled. [More details](../custom-components/edit-view#upload).                                           |
 
 <Banner type="success">
-  **Note:**
-  For details on how to build Custom Components, see [Building Custom Components](../custom-components/overview#building-custom-components).
+  **Note:** For details on how to build Custom Components, see [Building Custom
+  Components](../custom-components/overview#building-custom-components).
 </Banner>
 
 ### Pagination
@@ -244,8 +254,8 @@ export const Posts: CollectionConfig = {
 ```
 
 <Banner type="warning">
-  **Tip:**
-  If you are adding `listSearchableFields`, make sure you index each of these fields so your admin queries can remain performant.
+  **Tip:** If you are adding `listSearchableFields`, make sure you index each of
+  these fields so your admin queries can remain performant.
 </Banner>
 
 ## GraphQL
@@ -254,8 +264,8 @@ You can completely disable GraphQL for this collection by passing `graphQL: fals
 
 You can also pass an object to the collection's `graphQL` property, which allows you to define the following properties:
 
-| Option                 | Description                                                                         |
-| ---------------------- | ----------------------------------------------------------------------------------- |
+| Option             | Description                                                                         |
+| ------------------ | ----------------------------------------------------------------------------------- |
 | `singularName`     | Override the "singular" name that will be used in GraphQL schema generation.        |
 | `pluralName`       | Override the "plural" name that will be used in GraphQL schema generation.          |
 | `disableQueries`   | Disable all GraphQL queries that correspond to this collection by passing `true`.   |

docs/configuration/environment-vars.mdx

@@ -45,8 +45,10 @@ For security and safety reasons, the [Admin Panel](../admin/overview) does **not
 If you are building a [Custom Component](../custom-components/overview) and need to access Environment Variables from the client-side, you can do so by prefixing them with `NEXT_PUBLIC_`.
 
 <Banner type="warning">
-  **Important:**
-  Be careful about what variables you provide to your client-side code. Analyze every single one to make sure that you're not accidentally leaking sensitive information. Only ever include keys that are safe for the public to read in plain text.
+  **Important:** Be careful about what variables you provide to your client-side
+  code. Analyze every single one to make sure that you're not accidentally
+  leaking sensitive information. Only ever include keys that are safe for the
+  public to read in plain text.
 </Banner>
 
 For example, if you've got the following Environment Variable:
@@ -66,11 +68,7 @@ const stripeKey = process.env.NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY // highlight-li
 const MyClientComponent = () => {
   // do something with the key
 
-  return (
-    <div>
-      My Client Component
-    </div>
-  )
+  return <div>My Client Component</div>
 }
 ```
 
@@ -95,7 +93,7 @@ export default buildConfig({
 ```
 
 <Banner type="warning">
-  **Tip:**
-  Be sure that `dotenv` can find your `.env` file. By default, it will look for a file named `.env` in the root of your project. If you need to specify a different file, pass the path into the config options.
+  **Tip:** Be sure that `dotenv` can find your `.env` file. By default, it will
+  look for a file named `.env` in the root of your project. If you need to
+  specify a different file, pass the path into the config options.
 </Banner>
-

docs/configuration/globals.mdx

@@ -17,15 +17,16 @@ import { buildConfig } from 'payload'
 
 export default buildConfig({
   // ...
-  globals: [ // highlight-line
+  globals: [
+    // highlight-line
     // Your Globals go here
   ],
 })
 ```
 
 <Banner type="success">
-  **Tip:**
-  If you have more than one Global that share the same structure, consider using a [Collection](./collections) instead.
+  **Tip:** If you have more than one Global that share the same structure,
+  consider using a [Collection](./collections) instead.
 </Banner>
 
 ## Config Options
@@ -59,30 +60,33 @@ export const Nav: GlobalConfig = {
 ```
 
 <Banner type="success">
-  **Reminder:**
-  For more complex examples, see the [Templates](https://github.com/payloadcms/payload/tree/main/templates) and [Examples](https://github.com/payloadcms/payload/tree/main/examples) directories in the Payload repository.
+  **Reminder:** For more complex examples, see the
+  [Templates](https://github.com/payloadcms/payload/tree/main/templates) and
+  [Examples](https://github.com/payloadcms/payload/tree/main/examples)
+  directories in the Payload repository.
 </Banner>
 
 The following options are available:
 
-| Option              | Description                                                                                                                                                                                    |
-| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Option          | Description                                                                                                                                                                                    |
+| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `access`        | Provide Access Control functions to define exactly who should be able to do what with this Global. [More details](../access-control/globals).                                                  |
-| `admin`         | The configuration options for the Admin Panel. [More details](#admin-options).                                                                                                               |
+| `admin`         | The configuration options for the Admin Panel. [More details](#admin-options).                                                                                                                 |
 | `custom`        | Extension point for adding custom data (e.g. for plugins)                                                                                                                                      |
 | `dbName`        | Custom table or collection name for this Global depending on the Database Adapter. Auto-generated from slug if not defined.                                                                    |
 | `description`   | Text or React component to display below the Global header to give editors more information.                                                                                                   |
 | `endpoints`     | Add custom routes to the REST API. [More details](../rest-api/overview#custom-endpoints).                                                                                                      |
-| `fields` *     | Array of field types that will determine the structure and functionality of the data stored within this Global. [More details](../fields/overview).                                            |
+| `fields` \*     | Array of field types that will determine the structure and functionality of the data stored within this Global. [More details](../fields/overview).                                            |
 | `graphQL`       | Manage GraphQL-related properties related to this global. [More details](#graphql)                                                                                                             |
 | `hooks`         | Entry point for Hooks. [More details](../hooks/overview#global-hooks).                                                                                                                         |
 | `label`         | Text for the name in the Admin Panel or an object with keys for each language. Auto-generated from slug if not defined.                                                                        |
 | `lockDocuments` | Enables or disables document locking. By default, document locking is enabled. Set to an object to configure, or set to `false` to disable locking. [More details](../admin/locked-documents). |
-| `slug` *       | Unique, URL-friendly string that will act as an identifier for this Global.                                                                                                                    |
+| `slug` \*       | Unique, URL-friendly string that will act as an identifier for this Global.                                                                                                                    |
 | `typescript`    | An object with property `interface` as the text used in schema generation. Auto-generated from slug if not defined.                                                                            |
-| `versions`      | Set to true to enable default options, or configure with object properties. [More details](../versions/overview#global-config).                                                               |
+| `versions`      | Set to true to enable default options, or configure with object properties. [More details](../versions/overview#global-config).                                                                |
+| `forceSelect`   | Specify which fields should be selected always, regardless of the `select` query which can be useful that the field exists for access control / hooks                                          |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ### Fields
 
@@ -107,7 +111,8 @@ import { GlobalConfig } from 'payload'
 
 export const MyGlobal: GlobalConfig = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -115,15 +120,15 @@ export const MyGlobal: GlobalConfig = {
 
 The following options are available:
 
-| Option            | Description                                                                                                                       |
-| ----------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| Option        | Description                                                                                                                                                                             |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `group`       | Text or localization object used to group Collection and Global links in the admin navigation. Set to `false` to hide the link from the navigation while keeping its routes accessible. |
-| `hidden`      | Set to true or a function, called with the current user, returning true to exclude this Global from navigation and admin routing. |
-| `components`  | Swap in your own React components to be used within this Global. [More details](#custom-components).                           |
-| `preview`     | Function to generate a preview URL within the Admin Panel for this Global that can point to your app. [More details](../admin/preview).           |
-| `livePreview` | Enable real-time editing for instant visual feedback of your front-end application. [More details](../live-preview/overview).          |
-| `hideAPIURL`  | Hides the "API URL" meta field while editing documents within this collection.                                                    |
-| `meta`        | Page metadata overrides to apply to this Global within the Admin Panel. [More details](../admin/metadata).                                                                           |
+| `hidden`      | Set to true or a function, called with the current user, returning true to exclude this Global from navigation and admin routing.                                                       |
+| `components`  | Swap in your own React components to be used within this Global. [More details](#custom-components).                                                                                    |
+| `preview`     | Function to generate a preview URL within the Admin Panel for this Global that can point to your app. [More details](../admin/preview).                                                 |
+| `livePreview` | Enable real-time editing for instant visual feedback of your front-end application. [More details](../live-preview/overview).                                                           |
+| `hideAPIURL`  | Hides the "API URL" meta field while editing documents within this collection.                                                                                                          |
+| `meta`        | Page metadata overrides to apply to this Global within the Admin Panel. [More details](../admin/metadata).                                                                              |
 
 ### Custom Components
 
@@ -137,7 +142,8 @@ import type { SanitizedGlobalConfig } from 'payload'
 export const MyGlobal: SanitizedGlobalConfig = {
   // ...
   admin: {
-    components: { // highlight-line
+    components: {
+      // highlight-line
       // ...
     },
   },
@@ -148,10 +154,10 @@ The following options are available:
 
 #### General
 
-| Option                         | Description                                                                                                            |
-| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
-| `elements`                 | Override or create new elements within the Edit View. [More details](#edit-view-options).                                  |
-| `views`                    | Override or create new views within the Admin Panel. [More details](../custom-components/custom-views).                    |
+| Option     | Description                                                                                             |
+| ---------- | ------------------------------------------------------------------------------------------------------- |
+| `elements` | Override or create new elements within the Edit View. [More details](#edit-view-options).               |
+| `views`    | Override or create new views within the Admin Panel. [More details](../custom-components/custom-views). |
 
 #### Edit View Options
 
@@ -162,7 +168,8 @@ export const MyGlobal: SanitizedGlobalConfig = {
   // ...
   admin: {
     components: {
-      elements: { // highlight-line
+      elements: {
+        // highlight-line
         // ...
       },
     },
@@ -172,16 +179,16 @@ export const MyGlobal: SanitizedGlobalConfig = {
 
 The following options are available:
 
-| Option                         | Description                                                                                                                                                                                                       |
-| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `SaveButton`      | Replace the default Save Button with a Custom Component. [Drafts](../versions/drafts) must be disabled. [More details](../custom-components/edit-view#save-button).                                                            |
-| `SaveDraftButton` | Replace the default Save Draft Button with a Custom Component. [Drafts](../versions/drafts) must be enabled and autosave must be disabled. [More details](../custom-components/edit-view#save-draft-button).                   |
-| `PublishButton`   | Replace the default Publish Button with a Custom Component. [Drafts](../versions/drafts) must be enabled. [More details](../custom-components/edit-view#publish-button).                                                       |
-| `PreviewButton`   | Replace the default Preview Button with a Custom Component. [Preview](../admin/preview) must be enabled. [More details](../custom-components/edit-view#preview-button).                                                        |
+| Option            | Description                                                                                                                                                                                                  |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `SaveButton`      | Replace the default Save Button with a Custom Component. [Drafts](../versions/drafts) must be disabled. [More details](../custom-components/edit-view#save-button).                                          |
+| `SaveDraftButton` | Replace the default Save Draft Button with a Custom Component. [Drafts](../versions/drafts) must be enabled and autosave must be disabled. [More details](../custom-components/edit-view#save-draft-button). |
+| `PublishButton`   | Replace the default Publish Button with a Custom Component. [Drafts](../versions/drafts) must be enabled. [More details](../custom-components/edit-view#publish-button).                                     |
+| `PreviewButton`   | Replace the default Preview Button with a Custom Component. [Preview](../admin/preview) must be enabled. [More details](../custom-components/edit-view#preview-button).                                      |
 
 <Banner type="success">
-  **Note:**
-  For details on how to build Custom Components, see [Building Custom Components](../custom-components/overview#building-custom-components).
+  **Note:** For details on how to build Custom Components, see [Building Custom
+  Components](../custom-components/overview#building-custom-components).
 </Banner>
 
 ## GraphQL
@@ -190,11 +197,11 @@ You can completely disable GraphQL for this global by passing `graphQL: false` t
 
 You can also pass an object to the global's `graphQL` property, which allows you to define the following properties:
 
-| Option                 | Description                                                                         |
-| ---------------------- | ----------------------------------------------------------------------------------- |
-| `name`             | Override the name that will be used in GraphQL schema generation.                       |
-| `disableQueries`   | Disable all GraphQL queries that correspond to this global by passing `true`.           |
-| `disableMutations` | Disable all GraphQL mutations that correspond to this global by passing `true`.         |
+| Option             | Description                                                                     |
+| ------------------ | ------------------------------------------------------------------------------- |
+| `name`             | Override the name that will be used in GraphQL schema generation.               |
+| `disableQueries`   | Disable all GraphQL queries that correspond to this global by passing `true`.   |
+| `disableMutations` | Disable all GraphQL mutations that correspond to this global by passing `true`. |
 
 ## TypeScript
 

docs/configuration/i18n.mdx

@@ -23,15 +23,17 @@ import { buildConfig } from 'payload'
 
 export default buildConfig({
   // ...
-  i18n: { // highlight-line
+  i18n: {
+    // highlight-line
     // ...
   },
 })
 ```
 
 <Banner type="success">
-  **Note:**
-  If there is a language that Payload does not yet support, we accept [code contributions](https://github.com/payloadcms/payload/blob/main/CONTRIBUTING.md).
+  **Note:** If there is a language that Payload does not yet support, we accept
+  [code
+  contributions](https://github.com/payloadcms/payload/blob/main/CONTRIBUTING.md).
 </Banner>
 
 ## Config Options
@@ -46,18 +48,18 @@ export default buildConfig({
   // highlight-start
   i18n: {
     fallbackLanguage: 'en', // default
-  }
+  },
   // highlight-end
 })
 ```
 
 The following options are available:
 
-| Option                | Description                                                                                                                                                                                                                   |
-| --------------------- | --------------------------------|
-| `fallbackLanguage`     | The language to fall back to if the user's preferred language is not supported. Default is `'en'`.                                                                                                                           |
-| `translations`    | An object containing the translations. The keys are the language codes and the values are the translations.                                                                                                                |
-| `supportedLanguages` | An object containing the supported languages. The keys are the language codes and the values are the translations.                                                                                                         |
+| Option               | Description                                                                                                        |
+| -------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| `fallbackLanguage`   | The language to fall back to if the user's preferred language is not supported. Default is `'en'`.                 |
+| `translations`       | An object containing the translations. The keys are the language codes and the values are the translations.        |
+| `supportedLanguages` | An object containing the supported languages. The keys are the language codes and the values are the translations. |
 
 ## Adding Languages
 
@@ -81,8 +83,8 @@ export default buildConfig({
 ```
 
 <Banner type="warning">
- **Tip:**
- It's best to only support the languages that you need so that the bundled JavaScript is kept to a minimum for your project.
+  **Tip:** It's best to only support the languages that you need so that the
+  bundled JavaScript is kept to a minimum for your project.
 </Banner>
 
 ### Custom Translations
@@ -163,7 +165,7 @@ export const Articles: CollectionConfig = {
         placeholder: {
           // highlight-start
           en: 'Enter title',
-          es: 'Introduce el título'
+          es: 'Introduce el título',
           // highlight-end
         },
       },
@@ -188,25 +190,29 @@ In order to use [Custom Translations](#custom-translations) in your project, you
 
 Here we create a shareable translations object. We will import this in both our custom components and in our Payload config.
 
+In this example we show how to extend English, but you can do the same for any language you want.
+
 ```ts
 // <rootDir>/custom-translations.ts
 
-import type { Config } from 'payload'
+import { enTranslations } from '@payloadcms/translations/languages/en'
 import type { NestedKeysStripped } from '@payloadcms/translations'
 
-export const customTranslations: Config['i18n']['translations'] = {
+export const customTranslations = {
   en: {
     general: {
       myCustomKey: 'My custom english translation',
     },
     fields: {
       addLabel: 'Add!',
-    }
+    },
   },
 }
 
-export type CustomTranslationsObject = typeof customTranslations.en
-export type CustomTranslationsKeys = NestedKeysStripped<CustomTranslationsObject>
+export type CustomTranslationsObject = typeof customTranslations.en &
+  typeof enTranslations
+export type CustomTranslationsKeys =
+  NestedKeysStripped<CustomTranslationsObject>
 ```
 
 Import the shared translations object into our Payload config so they are available for use:
@@ -236,10 +242,16 @@ Import the shared translation types to use in your [Custom Component](../custom-
 import type React from 'react'
 import { useTranslation } from '@payloadcms/ui'
 
-import type { CustomTranslationsObject, CustomTranslationsKeys } from '../custom-translations'
+import type {
+  CustomTranslationsObject,
+  CustomTranslationsKeys,
+} from '../custom-translations'
 
 export const MyComponent: React.FC = () => {
-  const { i18n, t } = useTranslation<CustomTranslationsObject, CustomTranslationsKeys>() // These generics merge your custom translations with the default client translations
+  const { i18n, t } = useTranslation<
+    CustomTranslationsObject,
+    CustomTranslationsKeys
+  >() // These generics merge your custom translations with the default client translations
 
   return t('general:myCustomKey')
 }
@@ -250,7 +262,10 @@ Additionally, Payload exposes the `t` function in various places, for example in
 ```ts
 // <rootDir>/fields/myField.ts
 
-import type { DefaultTranslationKeys, TFunction } from '@payloadcms/translations'
+import type {
+  DefaultTranslationKeys,
+  TFunction,
+} from '@payloadcms/translations'
 import type { Field } from 'payload'
 
 import { CustomTranslationsKeys } from '../custom-translations'
@@ -258,8 +273,9 @@ import { CustomTranslationsKeys } from '../custom-translations'
 const field: Field = {
   name: 'myField',
   type: 'text',
-  label: (
-    { t }: { t: TFunction<CustomTranslationsKeys | DefaultTranslationKeys> }, // The generic passed to TFunction does not automatically merge the custom translations with the default translations. We need to merge them ourselves here
-  ) => t('fields:addLabel'),
+  label: ({ t: defaultT }) => {
+    const t = defaultT as TFunction<CustomTranslationsKeys>
+    return t('fields:addLabel')
+  },
 }
 ```

docs/configuration/localization.mdx

@@ -17,7 +17,8 @@ import { buildConfig } from 'payload'
 
 export default buildConfig({
   // ...
-  localization: { // highlight-line
+  localization: {
+    // highlight-line
     // ...
   },
 })
@@ -71,18 +72,18 @@ export default buildConfig({
 ```
 
 <Banner type="success">
-  **Tip:**
-  Localization works very well alongside [I18n](/docs/configuration/i18n).
+  **Tip:** Localization works very well alongside
+  [I18n](/docs/configuration/i18n).
 </Banner>
 
 The following options are available:
 
 | Option                       | Description                                                                                                                                                                                                                                                                                                                                                                                                                       |
-|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **`locales`**                | Array of all the languages that you would like to support. [More details](#locales)                                                                                                                                                                                                                                                                                                                                               |
 | **`defaultLocale`**          | Required string that matches one of the locale codes from the array provided. By default, if no locale is specified, documents will be returned in this locale.                                                                                                                                                                                                                                                                   |
 | **`fallback`**               | Boolean enabling "fallback" locale functionality. If a document is requested in a locale, but a field does not have a localized value corresponding to the requested locale, then if this property is enabled, the document will automatically fall back to the fallback locale value. If this property is not enabled, the value will not be populated unless a fallback is explicitly provided in the request. True by default. |
-| **`filterAvailableLocales`** | A function that is called with the array of `locales` and the `req`,  it should return locales to show in admin UI selector. [See more](#filter-available-options).                                                                                                                                                                                                                                                                         |
+| **`filterAvailableLocales`** | A function that is called with the array of `locales` and the `req`, it should return locales to show in admin UI selector. [See more](#filter-available-options).                                                                                                                                                                                                                                                                |
 
 ### Locales
 
@@ -94,18 +95,19 @@ The locale codes do not need to be in any specific format. It's up to you to def
 
 | Option               | Description                                                                                                                    |
 | -------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
-| **`code`** *        | Unique code to identify the language throughout the APIs for `locale` and `fallbackLocale`                                     |
+| **`code`** \*        | Unique code to identify the language throughout the APIs for `locale` and `fallbackLocale`                                     |
 | **`label`**          | A string to use for the selector when choosing a language, or an object keyed on the i18n keys for different languages in use. |
 | **`rtl`**            | A boolean that when true will make the admin UI display in Right-To-Left.                                                      |
 | **`fallbackLocale`** | The code for this language to fallback to when properties of a document are not present.                                       |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 #### Filter Available Options
+
 In some projects you may want to filter the available locales shown in the admin UI selector. You can do this by providing a `filterAvailableLocales` function in your Payload Config. This is called on the server side and is passed the array of locales. This means that you can determine what locales are visible in the localizer selection menu at the top of the admin panel. You could do this per user, or implement a function that scopes these to tenants and more. Here is an example using request headers in a multi-tenant application:
 
 ```ts
-// ... rest of payload config
+// ... rest of Payload config
 localization: {
   defaultLocale: 'en',
   locales: ['en', 'es'],
@@ -129,7 +131,6 @@ localization: {
 
 Since the filtering happens at the root level of the application and its result is not calculated every time you navigate to a new page, you may want to call `router.refresh` in a custom component that watches when values that affect the result change. In the example above, you would want to do this when `supportedLocales` changes on the tenant document.
 
-
 ## Field Localization
 
 Payload Localization works on a **field** level—not a document level. In addition to configuring the base Payload Config to support Localization, you need to specify each field that you would like to localize.
@@ -151,18 +152,18 @@ With the above configuration, the `title` field will now be saved in the databas
 All field types with a `name` property support the `localized` property—even the more complex field types like `array`s and `block`s.
 
 <Banner type="info">
-  **Note:**
-  Enabling Localization for field types that support nested fields will automatically create
-  localized "sets" of all fields contained within the field. For example, if you have a page layout
-  using a blocks field type, you have the choice of either localizing the full layout, by enabling
-  Localization on the top-level blocks field, or only certain fields within the layout.
+  **Note:** Enabling Localization for field types that support nested fields
+  will automatically create localized "sets" of all fields contained within the
+  field. For example, if you have a page layout using a blocks field type, you
+  have the choice of either localizing the full layout, by enabling Localization
+  on the top-level blocks field, or only certain fields within the layout.
 </Banner>
 
 <Banner type="warning">
-  **Important:**
-  When converting an existing field to or from `localized: true` the data structure in the document
-  will change for this field and so existing data for this field will be lost. Before changing the
-  Localization setting on fields with existing data, you may need to consider a field migration
+  **Important:** When converting an existing field to or from `localized: true`
+  the data structure in the document will change for this field and so existing
+  data for this field will be lost. Before changing the Localization setting on
+  fields with existing data, you may need to consider a field migration
   strategy.
 </Banner>
 
@@ -213,9 +214,10 @@ query {
 ```
 
 <Banner>
-  In GraphQL, specifying the locale at the top level of a query will automatically apply it
-  throughout all nested relationship fields. You can override this behavior by re-specifying locale
-  arguments in nested related document queries.
+  In GraphQL, specifying the locale at the top level of a query will
+  automatically apply it throughout all nested relationship fields. You can
+  override this behavior by re-specifying locale arguments in nested related
+  document queries.
 </Banner>
 
 #### Local API
@@ -235,8 +237,8 @@ const posts = await payload.find({
 ```
 
 <Banner type="success">
-  **Tip:**
-  The REST and Local APIs can return all Localization data in one request by passing 'all' or '*' as
-  the **locale** parameter. The response will be structured so that field values come
-  back as the full objects keyed for each locale instead of the single, translated value.
+  **Tip:** The REST and Local APIs can return all Localization data in one
+  request by passing 'all' or '*' as the **locale** parameter. The response will
+  be structured so that field values come back as the full objects keyed for
+  each locale instead of the single, translated value.
 </Banner>

docs/configuration/overview.mdx

@@ -23,8 +23,8 @@ export default buildConfig({
 The Payload Config is strongly typed and ties directly into Payload's TypeScript codebase. This means your IDE (such as VSCode) will provide helpful information like type-ahead suggestions while you write your config.
 
 <Banner type="success">
-  **Tip:**
-  The location of your Payload Config can be customized. [More details](#customizing-the-config-location).
+  **Tip:** The location of your Payload Config can be customized. [More
+  details](#customizing-the-config-location).
 </Banner>
 
 ## Config Options
@@ -48,62 +48,65 @@ export default buildConfig({
       fields: [
         {
           name: 'title',
-          type: 'text'
-        }
-      ]
-    }
+          type: 'text',
+        },
+      ],
+    },
   ],
 })
 ```
 
 <Banner type="success">
-  **Note:**
-  For more complex examples, see the [Templates](https://github.com/payloadcms/payload/tree/main/templates) and [Examples](https://github.com/payloadcms/payload/tree/main/examples) directories in the Payload repository.
+  **Note:** For more complex examples, see the
+  [Templates](https://github.com/payloadcms/payload/tree/main/templates) and
+  [Examples](https://github.com/payloadcms/payload/tree/main/examples)
+  directories in the Payload repository.
 </Banner>
 
 The following options are available:
 
-| Option                     | Description                                                                                                                                                                                                                  |
-| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`admin`**                | The configuration options for the Admin Panel, including Custom Components, Live Preview, etc. [More details](../admin/overview#admin-options).                                                                              |
-| **`bin`**                  | Register custom bin scripts for Payload to execute.                                                                                                                                                                          |
-| **`editor`**               | The Rich Text Editor which will be used by `richText` fields. [More details](../rich-text/overview).                                                                                                                         |
-| **`db`** *                 | The Database Adapter which will be used by Payload. [More details](../database/overview).                                                                                                                                    |
-| **`serverURL`**            | A string used to define the absolute URL of your app. This includes the protocol, for example `https://example.com`. No paths allowed, only protocol, domain and (optionally) port.                                          |
-| **`collections`**          | An array of Collections for Payload to manage. [More details](./collections).                                                                                                                                                |
-| **`compatibility`**        | Compatibility flags for earlier versions of Payload. [More details](#compatibility-flags).                                                                                                                                   |
-| **`globals`**              | An array of Globals for Payload to manage. [More details](./globals).                                                                                                                                                        |
-| **`cors`**                 | Cross-origin resource sharing (CORS) is a mechanism that accept incoming requests from given domains. You can also customize the `Access-Control-Allow-Headers` header. [More details](#cors).                               |
-| **`localization`**         | Opt-in to translate your content into multiple locales. [More details](./localization).                                                                                                                                      |
-| **`logger`**               | Logger options, logger options with a destination stream, or an instantiated logger instance. [More details](https://getpino.io/#/docs/api?id=options).                                                                      |
-| **`loggingLevels`**        | An object to override the level to use in the logger for Payload's errors.                                                                                                                                                   |
-| **`graphQL`**              | Manage GraphQL-specific functionality, including custom queries and mutations, query complexity limits, etc. [More details](../graphql/overview#graphql-options).                                                            |
-| **`cookiePrefix`**         | A string that will be prefixed to all cookies that Payload sets.                                                                                                                                                             |
-| **`csrf`**                 | A whitelist array of URLs to allow Payload to accept cookies from. [More details](../authentication/cookies#csrf-attacks).                                                                                                   |
-| **`defaultDepth`**         | If a user does not specify `depth` while requesting a resource, this depth will be used. [More details](../queries/depth).                                                                                                   |
-| **`defaultMaxTextLength`** | The maximum allowed string length to be permitted application-wide. Helps to prevent malicious public document creation.                                                                                                     |
-| **`maxDepth`**             | The maximum allowed depth to be permitted application-wide. This setting helps prevent against malicious queries. Defaults to `10`. [More details](../queries/depth).                                                        |
-| **`indexSortableFields`**  | Automatically index all sortable top-level fields in the database to improve sort performance and add database compatibility for Azure Cosmos and similar.                                                                   |
-| **`upload`**               | Base Payload upload configuration. [More details](../upload/overview#payload-wide-upload-options).                                                                                                                           |
-| **`routes`**               | Control the routing structure that Payload binds itself to. [More details](../admin/overview#root-level-routes).                                                                                                             |
-| **`email`**                | Configure the Email Adapter for Payload to use. [More details](../email/overview).                                                                                                                                           |
-| **`onInit`**               | A function that is called immediately following startup that receives the Payload instance as its only argument.                                                                                                             |
-| **`debug`**                | Enable to expose more detailed error information.                                                                                                                                                                            |
-| **`telemetry`**            | Disable Payload telemetry by passing `false`. [More details](#telemetry).                                                                                                                                                    |
-| **`hooks`**                | An array of Root Hooks. [More details](../hooks/overview).                                                                                                                                                                   |
-| **`plugins`**              | An array of Plugins. [More details](../plugins/overview).                                                                                                                                                                    |
-| **`endpoints`**            | An array of Custom Endpoints added to the Payload router. [More details](../rest-api/overview#custom-endpoints).                                                                                                             |
-| **`custom`**               | Extension point for adding custom data (e.g. for plugins).                                                                                                                                                                   |
-| **`i18n`**                 | Internationalization configuration. Pass all i18n languages you'd like the admin UI to support. Defaults to English-only. [More details](./i18n).                                                                            |
-| **`secret`** *             | A secure, unguessable string that Payload will use for any encryption workflows - for example, password salt / hashing.                                                                                                      |
-| **`sharp`**                | If you would like Payload to offer cropping, focal point selection, and automatic media resizing, install and pass the Sharp module to the config here.                                                                      |
-| **`typescript`**           | Configure TypeScript settings here. [More details](#typescript).                                                                                                                                                             |
+| Option                     | Description                                                                                                                                                                                    |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`admin`**                | The configuration options for the Admin Panel, including Custom Components, Live Preview, etc. [More details](../admin/overview#admin-options).                                                |
+| **`bin`**                  | Register custom bin scripts for Payload to execute. [More Details](#custom-bin-scripts).                                                                                                       |
+| **`editor`**               | The Rich Text Editor which will be used by `richText` fields. [More details](../rich-text/overview).                                                                                           |
+| **`db`** \*                | The Database Adapter which will be used by Payload. [More details](../database/overview).                                                                                                      |
+| **`serverURL`**            | A string used to define the absolute URL of your app. This includes the protocol, for example `https://example.com`. No paths allowed, only protocol, domain and (optionally) port.            |
+| **`collections`**          | An array of Collections for Payload to manage. [More details](./collections).                                                                                                                  |
+| **`compatibility`**        | Compatibility flags for earlier versions of Payload. [More details](#compatibility-flags).                                                                                                     |
+| **`globals`**              | An array of Globals for Payload to manage. [More details](./globals).                                                                                                                          |
+| **`cors`**                 | Cross-origin resource sharing (CORS) is a mechanism that accept incoming requests from given domains. You can also customize the `Access-Control-Allow-Headers` header. [More details](#cors). |
+| **`localization`**         | Opt-in to translate your content into multiple locales. [More details](./localization).                                                                                                        |
+| **`logger`**               | Logger options, logger options with a destination stream, or an instantiated logger instance. [More details](https://getpino.io/#/docs/api?id=options).                                        |
+| **`loggingLevels`**        | An object to override the level to use in the logger for Payload's errors.                                                                                                                     |
+| **`graphQL`**              | Manage GraphQL-specific functionality, including custom queries and mutations, query complexity limits, etc. [More details](../graphql/overview#graphql-options).                              |
+| **`cookiePrefix`**         | A string that will be prefixed to all cookies that Payload sets.                                                                                                                               |
+| **`csrf`**                 | A whitelist array of URLs to allow Payload to accept cookies from. [More details](../authentication/cookies#csrf-attacks).                                                                     |
+| **`defaultDepth`**         | If a user does not specify `depth` while requesting a resource, this depth will be used. [More details](../queries/depth).                                                                     |
+| **`defaultMaxTextLength`** | The maximum allowed string length to be permitted application-wide. Helps to prevent malicious public document creation.                                                                       |
+| `queryPresets`             | An object that to configure Collection Query Presets. [More details](../query-presets/overview).                                                                                               |
+| **`maxDepth`**             | The maximum allowed depth to be permitted application-wide. This setting helps prevent against malicious queries. Defaults to `10`. [More details](../queries/depth).                          |
+| **`indexSortableFields`**  | Automatically index all sortable top-level fields in the database to improve sort performance and add database compatibility for Azure Cosmos and similar.                                     |
+| **`upload`**               | Base Payload upload configuration. [More details](../upload/overview#payload-wide-upload-options).                                                                                             |
+| **`routes`**               | Control the routing structure that Payload binds itself to. [More details](../admin/overview#root-level-routes).                                                                               |
+| **`email`**                | Configure the Email Adapter for Payload to use. [More details](../email/overview).                                                                                                             |
+| **`onInit`**               | A function that is called immediately following startup that receives the Payload instance as its only argument.                                                                               |
+| **`debug`**                | Enable to expose more detailed error information.                                                                                                                                              |
+| **`telemetry`**            | Disable Payload telemetry by passing `false`. [More details](#telemetry).                                                                                                                      |
+| **`hooks`**                | An array of Root Hooks. [More details](../hooks/overview).                                                                                                                                     |
+| **`plugins`**              | An array of Plugins. [More details](../plugins/overview).                                                                                                                                      |
+| **`endpoints`**            | An array of Custom Endpoints added to the Payload router. [More details](../rest-api/overview#custom-endpoints).                                                                               |
+| **`custom`**               | Extension point for adding custom data (e.g. for plugins).                                                                                                                                     |
+| **`i18n`**                 | Internationalization configuration. Pass all i18n languages you'd like the admin UI to support. Defaults to English-only. [More details](./i18n).                                              |
+| **`secret`** \*            | A secure, unguessable string that Payload will use for any encryption workflows - for example, password salt / hashing.                                                                        |
+| **`sharp`**                | If you would like Payload to offer cropping, focal point selection, and automatic media resizing, install and pass the Sharp module to the config here.                                        |
+| **`typescript`**           | Configure TypeScript settings here. [More details](#typescript).                                                                                                                               |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 <Banner type="warning">
-  **Note:**
-  Some properties are removed from the client-side bundle. [More details](../custom-components/overview#accessing-the-payload-config).
+  **Note:** Some properties are removed from the client-side bundle. [More
+  details](../custom-components/overview#accessing-the-payload-config).
 </Banner>
 
 ### Typescript Config
@@ -117,33 +120,36 @@ import { buildConfig } from 'payload'
 
 export default buildConfig({
   // ...
-  typescript: { // highlight-line
+  typescript: {
+    // highlight-line
     // ...
-  }
+  },
 })
 ```
 
 The following options are available:
 
-| Option          | Description                                                                                                                                                                                                 |
-| --------------- | --------------------- |
+| Option             | Description                                                                                                                                                                                                         |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **`autoGenerate`** | By default, Payload will auto-generate TypeScript interfaces for all collections and globals that your config defines. Opt out by setting `typescript.autoGenerate: false`. [More details](../typescript/overview). |
-| **`declare`**     | By default, Payload adds a `declare` block to your generated types, which makes sure that Payload uses your generated types for all Local API methods. Opt out by setting `typescript.declare: false`. |
-| **`outputFile`**  | Control the output path and filename of Payload's auto-generated types by defining the `typescript.outputFile` property to a full, absolute path. |
+| **`declare`**      | By default, Payload adds a `declare` block to your generated types, which makes sure that Payload uses your generated types for all Local API methods. Opt out by setting `typescript.declare: false`.              |
+| **`outputFile`**   | Control the output path and filename of Payload's auto-generated types by defining the `typescript.outputFile` property to a full, absolute path.                                                                   |
 
 ## Config Location
 
 For Payload command-line scripts, we need to be able to locate your Payload Config. We'll check a variety of locations for the presence of `payload.config.ts` by default, including:
 
 1. The root current working directory
-1. The `compilerOptions` in your `tsconfig`*
-1. The `dist` directory*
+1. The `compilerOptions` in your `tsconfig`\*
+1. The `dist` directory\*
 
-_* Config location detection is different between development and production environments. See below for more details._
+_\* Config location detection is different between development and production environments. See below for more details._
 
 <Banner type="warning">
-  **Important:**
-  Ensure your `tsconfig.json` is properly configured for Payload to auto-detect your config location. If if does not exist, or does not specify the proper `compilerOptions`, Payload will default to the current working directory.
+  **Important:** Ensure your `tsconfig.json` is properly configured for Payload
+  to auto-detect your config location. If if does not exist, or does not specify
+  the proper `compilerOptions`, Payload will default to the current working
+  directory.
 </Banner>
 
 **Development Mode**
@@ -194,8 +200,8 @@ To use a custom config location, set the `PAYLOAD_CONFIG_PATH` environment varia
 ```
 
 <Banner type="info">
-  **Tip:**
-  `PAYLOAD_CONFIG_PATH` can be either an absolute path, or path relative to your current working directory.
+  **Tip:** `PAYLOAD_CONFIG_PATH` can be either an absolute path, or path
+  relative to your current working directory.
 </Banner>
 
 ## Telemetry
@@ -208,10 +214,10 @@ For more information about what we track, take a look at our [privacy policy](/p
 
 Cross-origin resource sharing (CORS) can be configured with either a whitelist array of URLS to allow CORS requests from, a wildcard string (`*`) to accept incoming requests from any domain, or a object with the following properties:
 
-| Option    | Description                                                                                                                                                                        |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| Option        | Description                                                                                                                             |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
 | **`origins`** | Either a whitelist array of URLS to allow CORS requests from, or a wildcard string (`'*'`) to accept incoming requests from any domain. |
-| **`headers`**  | A list of allowed headers that will be appended in `Access-Control-Allow-Headers`. |
+| **`headers`** | A list of allowed headers that will be appended in `Access-Control-Allow-Headers`.                                                      |
 
 Here's an example showing how to allow incoming requests from any domain:
 
@@ -220,7 +226,7 @@ import { buildConfig } from 'payload'
 
 export default buildConfig({
   // ...
-  cors: '*' // highlight-line
+  cors: '*', // highlight-line
 })
 ```
 
@@ -265,3 +271,46 @@ The Payload Config can accept compatibility flags for running the newest version
 Payload localization works on a field-by-field basis. As you can nest fields within other fields, you could potentially nest a localized field within a localized field—but this would be redundant and unnecessary. There would be no reason to define a localized field within a localized parent field, given that the entire data structure from the parent field onward would be localized.
 
 By default, Payload will remove the `localized: true` property from sub-fields if a parent field is localized. Set this compatibility flag to `true` only if you have an existing Payload MongoDB database from pre-3.0, and you have nested localized fields that you would like to maintain without migrating.
+
+## Custom bin scripts
+
+Using the `bin` configuration property, you can inject your own scripts to `npx payload`.
+Example for `pnpm payload seed`:
+
+Step 1: create `seed.ts` file in the same folder with `payload.config.ts` with:
+
+```ts
+import type { SanitizedConfig } from 'payload'
+
+import payload from 'payload'
+
+// Script must define a "script" function export that accepts the sanitized config
+export const script = async (config: SanitizedConfig) => {
+  await payload.init({ config })
+  await payload.create({
+    collection: 'pages',
+    data: { title: 'my title' },
+  })
+  payload.logger.info('Succesffully seeded!')
+  process.exit(0)
+}
+```
+
+Step 2: add the `seed` script to `bin`:
+
+```ts
+export default buildConfig({
+  bin: [
+    {
+      scriptPath: path.resolve(dirname, 'seed.ts'),
+      key: 'seed',
+    },
+  ],
+})
+```
+
+Now you can run the command using:
+
+```sh
+pnpm payload seed
+```

docs/custom-components/custom-providers.mdx

@@ -27,23 +27,22 @@ Then build your Custom Provider as follows:
 
 ```tsx
 'use client'
-import React, { createContext, useContext } from 'react'
+import React, { createContext, use } from 'react'
 
 const MyCustomContext = React.createContext(myCustomValue)
 
 export function MyProvider({ children }: { children: React.ReactNode }) {
-  return (
-    <MyCustomContext.Provider value={myCustomValue}>
-      {children}
-    </MyCustomContext.Provider>
-  )
+  return <MyCustomContext value={myCustomValue}>{children}</MyCustomContext>
 }
 
-export const useMyCustomContext = () => useContext(MyCustomContext)
+export const useMyCustomContext = () => use(MyCustomContext)
 ```
 
 _For details on how to build Custom Components, see [Building Custom Components](./overview#building-custom-components)._
 
 <Banner type="warning">
-  **Reminder:** React Context exists only within Client Components. This means they must include the `use client` directive at the top of their files and cannot contain server-only code. To use a Server Component here, simply _wrap_ your Client Component with it.
+  **Reminder:** React Context exists only within Client Components. This means
+  they must include the `use client` directive at the top of their files and
+  cannot contain server-only code. To use a Server Component here, simply _wrap_
+  your Client Component with it.
 </Banner>

docs/custom-components/custom-views.mdx

@@ -38,26 +38,26 @@ const config = buildConfig({
         // highlight-start
         dashboard: {
           Component: '/path/to/MyCustomDashboard',
-        }
+        },
         // highlight-end
-      }
-    }
-  }
+      },
+    },
+  },
 })
 ```
 
 For more granular control, pass a configuration object instead. Payload exposes the following properties for each view:
 
-| Property           | Description                                                                                                                                                                                |
-| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `Component` * | Pass in the component path that should be rendered when a user navigates to this route.                                                                                                         |
-| `path` *      | Any valid URL path or array of paths that [`path-to-regexp`](https://www.npmjs.com/package/path-to-regex) understands.                                                                     |
-| `exact`        | Boolean. When true, will only match if the path matches the `usePathname()` exactly.                                                                                                     |
+| Property       | Description                                                                                                                                                                         |
+| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Component` \* | Pass in the component path that should be rendered when a user navigates to this route.                                                                                             |
+| `path` \*      | Any valid URL path or array of paths that [`path-to-regexp`](https://www.npmjs.com/package/path-to-regex) understands.                                                              |
+| `exact`        | Boolean. When true, will only match if the path matches the `usePathname()` exactly.                                                                                                |
 | `strict`       | When true, a path that has a trailing slash will only match a `location.pathname` with a trailing slash. This has no effect when there are additional URL segments in the pathname. |
-| `sensitive`    | When true, will match if the path is case sensitive.|
-| `meta`         | Page metadata overrides to apply to this view within the Admin Panel. [More details](./metadata).                                                                           |
+| `sensitive`    | When true, will match if the path is case sensitive.                                                                                                                                |
+| `meta`         | Page metadata overrides to apply to this view within the Admin Panel. [More details](../admin/metadata).                                                                            |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ### Adding New Views
 
@@ -86,14 +86,12 @@ const config = buildConfig({
 ```
 
 <Banner type="warning">
-  **Note:**
-  Routes are cascading, so unless explicitly given the `exact` property, they will
-  match on URLs that simply _start_ with the route's path. This is helpful when creating catch-all
-  routes in your application. Alternatively, define your nested route _before_ your parent
-  route.
+  **Note:** Routes are cascading, so unless explicitly given the `exact`
+  property, they will match on URLs that simply _start_ with the route's path.
+  This is helpful when creating catch-all routes in your application.
+  Alternatively, define your nested route _before_ your parent route.
 </Banner>
 
-
 ## Building Custom Views
 
 Custom Views are simply [Custom Components](./overview) rendered at the page-level. Custom Views can either [replace existing views](#replacing-views) or [add entirely new ones](#adding-new-views). The process is generally the same regardless of the type of view you are customizing.
@@ -110,8 +108,8 @@ export const MyCollectionConfig: CollectionConfig = {
       views: {
         // highlight-start
         edit: {
-          Component: '/path/to/MyCustomView' // highlight-line
-        }
+          Component: '/path/to/MyCustomView', // highlight-line
+        },
         // highlight-end
       },
     },
@@ -123,20 +121,21 @@ export const MyCollectionConfig: CollectionConfig = {
 
 Your Custom Views will be provided with the following props:
 
-| Prop                      | Description                                                                                                                        |
-| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
-| `initPageResult`      | An object containing `req`, `payload`, `permissions`, etc.                                                                         |
-| `clientConfig`        | The Client Config object. [More details](./overview#accessing-the-payload-config).                                        |
-| `importMap`           | The import map object.                                                                                                             |
-| `params`              | An object containing the [Dynamic Route Parameters](https://nextjs.org/docs/app/building-your-application/routing/dynamic-routes). |
-| `searchParams`        | An object containing the [Search Parameters](https://developer.mozilla.org/docs/Learn/Common_questions/What_is_a_URL#parameters).  |
-| `doc`                 | The document being edited. Only available in Document Views. [More details](./document-views).                                      |
-| `i18n`           |    The [i18n](../configuration/i18n) object.                                        |
-| `payload`        |    The [Payload](../local-api/overview) class.                                      |
+| Prop             | Description                                                                                                                        |
+| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| `initPageResult` | An object containing `req`, `payload`, `permissions`, etc.                                                                         |
+| `clientConfig`   | The Client Config object. [More details](./overview#accessing-the-payload-config).                                                 |
+| `importMap`      | The import map object.                                                                                                             |
+| `params`         | An object containing the [Dynamic Route Parameters](https://nextjs.org/docs/app/building-your-application/routing/dynamic-routes). |
+| `searchParams`   | An object containing the [Search Parameters](https://developer.mozilla.org/docs/Learn/Common_questions/What_is_a_URL#parameters).  |
+| `doc`            | The document being edited. Only available in Document Views. [More details](./document-views).                                     |
+| `i18n`           | The [i18n](../configuration/i18n) object.                                                                                          |
+| `payload`        | The [Payload](../local-api/overview) class.                                                                                        |
 
 <Banner type="warning">
-  **Note:**
-  Some views may receive additional props, such as [Collection Views](#collection-views) and [Global Views](#global-views). See the relevant section for more details.
+  **Note:** Some views may receive additional props, such as [Collection
+  Views](#collection-views) and [Global Views](#global-views). See the relevant
+  section for more details.
 </Banner>
 
 Here is an example of a Custom View component:
@@ -158,8 +157,8 @@ export function MyCustomView(props: AdminViewServerProps) {
 ```
 
 <Banner type="success">
-  **Tip:**
-  For consistent layout and navigation, you may want to wrap your Custom View with one of the built-in [Template](./overview#templates).
+  **Tip:** For consistent layout and navigation, you may want to wrap your
+  Custom View with one of the built-in [Template](./overview#templates).
 </Banner>
 
 ### View Templates
@@ -212,13 +211,9 @@ import type { AdminViewServerProps } from 'payload'
 import { Gutter } from '@payloadcms/ui'
 import React from 'react'
 
-export function MyCustomView({
-  initPageResult
-}: AdminViewServerProps) {
+export function MyCustomView({ initPageResult }: AdminViewServerProps) {
   const {
-    req: {
-      user
-    }
+    req: { user },
   } = initPageResult
 
   if (!user) {
@@ -251,7 +246,7 @@ const config = buildConfig({
         // highlight-start
         dashboard: {
           Component: '/path/to/Dashboard',
-        }
+        },
         // highlight-end
         // Other options include:
         // - account
@@ -267,11 +262,11 @@ _For details on how to build Custom Views, including all available props, see [B
 
 The following options are available:
 
-| Property        | Description                                                                   |
-| --------------- | ----------------------------------------------------------------------------- |
-| `account`   | The Account view is used to show the currently logged in user's Account page. |
-| `dashboard` | The main landing page of the Admin Panel.                                     |
-| `[key]` | Any other key can be used to add a completely new Root View. [More details](#adding-new-views).                             |
+| Property    | Description                                                                                     |
+| ----------- | ----------------------------------------------------------------------------------------------- |
+| `account`   | The Account view is used to show the currently logged in user's Account page.                   |
+| `dashboard` | The main landing page of the Admin Panel.                                                       |
+| `[key]`     | Any other key can be used to add a completely new Root View. [More details](#adding-new-views). |
 
 ## Collection Views
 
@@ -291,8 +286,8 @@ export const MyCollectionConfig: CollectionConfig = {
         edit: {
           default: {
             Component: '/path/to/MyCustomCollectionView',
-          }
-        }
+          },
+        },
         // highlight-end
         // Other options include:
         // - list
@@ -305,17 +300,18 @@ export const MyCollectionConfig: CollectionConfig = {
 ```
 
 <Banner type="success">
-  **Reminder:**
-  The `edit` key is comprised of various nested views, known as Document Views, that relate to the same Collection Document. [More details](./document-views).
+  **Reminder:** The `edit` key is comprised of various nested views, known as
+  Document Views, that relate to the same Collection Document. [More
+  details](./document-views).
 </Banner>
 
 The following options are available:
 
-| Property   | Description                                                                                                                                                    |
-| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `edit` | The Edit View corresponds to a single Document for any given Collection and consists of various nested views. [More details](./document-views). |
-| `list` | The List View is used to show a list of Documents for any given Collection. [More details](#list-view).                                                            |
-| `[key]` | Any other key can be used to add a completely new Collection View. [More details](#adding-new-views).                             |
+| Property | Description                                                                                                                                     |
+| -------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| `edit`   | The Edit View corresponds to a single Document for any given Collection and consists of various nested views. [More details](./document-views). |
+| `list`   | The List View is used to show a list of Documents for any given Collection. [More details](#list-view).                                         |
+| `[key]`  | Any other key can be used to add a completely new Collection View. [More details](#adding-new-views).                                           |
 
 _For details on how to build Custom Views, including all available props, see [Building Custom Views](#building-custom-views)._
 
@@ -337,8 +333,8 @@ export const MyGlobalConfig: SanitizedGlobalConfig = {
         edit: {
           default: {
             Component: '/path/to/MyCustomGlobalView',
-          }
-        }
+          },
+        },
         // highlight-end
         // Other options include:
         // - [key: string]
@@ -350,15 +346,16 @@ export const MyGlobalConfig: SanitizedGlobalConfig = {
 ```
 
 <Banner type="success">
-  **Reminder:**
-  The `edit` key is comprised of various nested views, known as Document Views, that relate to the same Global Document. [More details](./document-views).
+  **Reminder:** The `edit` key is comprised of various nested views, known as
+  Document Views, that relate to the same Global Document. [More
+  details](./document-views).
 </Banner>
 
 The following options are available:
 
-| Property   | Description                                                                                                                                     |
-| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
-| `edit` | The Edit View represents a single Document for any given Global and consists of various nested views. [More details](./document-views). |
-| `[key]` | Any other key can be used to add a completely new Global View. [More details](#adding-new-views).                             |
+| Property | Description                                                                                                                             |
+| -------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| `edit`   | The Edit View represents a single Document for any given Global and consists of various nested views. [More details](./document-views). |
+| `[key]`  | Any other key can be used to add a completely new Global View. [More details](#adding-new-views).                                       |
 
 _For details on how to build Custom Views, including all available props, see [Building Custom Views](#building-custom-views)._

docs/custom-components/document-views.mdx

@@ -45,15 +45,15 @@ export const MyCollectionOrGlobalConfig: CollectionConfig = {
 
 The following options are available:
 
-| Property          | Description                                                                                                                                                     |
-| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `root`        | The Root View overrides all other nested views and routes. No document controls or tabs are rendered when this key is set. [More details](#document-root). |
-| `default`     | The Default View is the primary view in which your document is edited. It is rendered within the "Edit" tab. [More details](./edit-view).                                                    |
+| Property      | Description                                                                                                                                                     |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `root`        | The Root View overrides all other nested views and routes. No document controls or tabs are rendered when this key is set. [More details](#document-root).      |
+| `default`     | The Default View is the primary view in which your document is edited. It is rendered within the "Edit" tab. [More details](./edit-view).                       |
 | `versions`    | The Versions View is used to navigate the version history of a single document. It is rendered within the "Versions" tab. [More details](../versions/overview). |
 | `version`     | The Version View is used to edit a single version of a document. It is rendered within the "Version" tab. [More details](../versions/overview).                 |
 | `api`         | The API View is used to display the REST API JSON response for a given document. It is rendered within the "API" tab.                                           |
 | `livePreview` | The LivePreview view is used to display the Live Preview interface. It is rendered within the "Live Preview" tab. [More details](../live-preview/overview).     |
-| `[key]`       | Any other key can be used to add a completely new Document View.                                                                |
+| `[key]`       | Any other key can be used to add a completely new Document View.                                                                                                |
 
 _For details on how to build Custom Views, including all available props, see [Building Custom Views](./custom-views#building-custom-views)._
 
@@ -112,8 +112,8 @@ export const MyCollection: CollectionConfig = {
             path: '/my-custom-tab',
             // highlight-start
             tab: {
-              Component: '/path/to/MyCustomTabComponent'
-            }
+              Component: '/path/to/MyCustomTabComponent',
+            },
             // highlight-end
           },
           anotherCustomTab: {
@@ -123,7 +123,7 @@ export const MyCollection: CollectionConfig = {
             tab: {
               label: 'Another Custom View',
               href: '/another-custom-view',
-            }
+            },
             // highlight-end
           },
         },
@@ -134,16 +134,15 @@ export const MyCollection: CollectionConfig = {
 ```
 
 <Banner type="warning">
- **Note:**
- This applies to _both_ Collections _and_ Globals.
+  **Note:** This applies to _both_ Collections _and_ Globals.
 </Banner>
 
 The following options are available for tabs:
 
-| Property    | Description                                                                                           |
-| ----------- | ----------------------------------------------------------------------------------------------------- |
-| `label`     | The label to display in the tab.                                                                      |
-| `href`      | The URL to navigate to when the tab is clicked. This is optional and defaults to the tab's `path`.    |
+| Property    | Description                                                                                                   |
+| ----------- | ------------------------------------------------------------------------------------------------------------- |
+| `label`     | The label to display in the tab.                                                                              |
+| `href`      | The URL to navigate to when the tab is clicked. This is optional and defaults to the tab's `path`.            |
 | `Component` | The component to render in the tab. This can be a Server or Client component. [More details](#tab-components) |
 
 ### Tab Components
@@ -161,9 +160,7 @@ import { Link } from '@payloadcms/ui'
 
 export function MyCustomTabComponent(props: DocumentTabServerProps) {
   return (
-    <Link href="/my-custom-tab">
-      This is a custom Document Tab (Server)
-    </Link>
+    <Link href="/my-custom-tab">This is a custom Document Tab (Server)</Link>
   )
 }
 ```
@@ -178,9 +175,7 @@ import { Link } from '@payloadcms/ui'
 
 export function MyCustomTabComponent(props: DocumentTabClientProps) {
   return (
-    <Link href="/my-custom-tab">
-      This is a custom Document Tab (Client)
-    </Link>
+    <Link href="/my-custom-tab">This is a custom Document Tab (Client)</Link>
   )
 }
 ```

docs/custom-components/edit-view.mdx

@@ -11,8 +11,9 @@ The Edit View is where users interact with individual [Collection](../collection
 The Edit View can be swapped out in its entirety for a Custom View, or it can be injected with a number of Custom Components to add additional functionality or presentational elements without replacing the entire view.
 
 <Banner type="warning">
-  **Note:**
-  The Edit View is one of many [Document Views](./document-views) in the Payload Admin Panel. Each Document View is responsible for a different aspect of the interacting with a single Document.
+  **Note:** The Edit View is one of many [Document Views](./document-views) in
+  the Payload Admin Panel. Each Document View is responsible for a different
+  aspect of the interacting with a single Document.
 </Banner>
 
 ## Custom Edit View
@@ -33,7 +34,7 @@ const config = buildConfig({
             Component: '/path/to/MyCustomEditViewComponent',
           },
           // highlight-end
-        }
+        },
       },
     },
   },
@@ -49,11 +50,7 @@ import React from 'react'
 import type { DocumentViewServerProps } from 'payload'
 
 export function MyCustomServerEditView(props: DocumentViewServerProps) {
-  return (
-    <div>
-      This is a custom Edit View (Server)
-    </div>
-  )
+  return <div>This is a custom Edit View (Server)</div>
 }
 ```
 
@@ -65,11 +62,7 @@ import React from 'react'
 import type { DocumentViewClientProps } from 'payload'
 
 export function MyCustomClientEditView(props: DocumentViewClientProps) {
-  return (
-    <div>
-      This is a custom Edit View (Client)
-    </div>
-  )
+  return <div>This is a custom Edit View (Client)</div>
 }
 ```
 
@@ -80,8 +73,9 @@ _For details on how to build Custom Views, including all available props, see [B
 In addition to swapping out the entire Edit View with a [Custom View](./custom-views), you can also override individual components. This allows you to customize specific parts of the Edit View without swapping out the entire view.
 
 <Banner type="warning">
-  **Important:**
-  Collection and Globals are keyed to a different property in the `admin.components` object have slightly different options. Be sure to use the correct key for the entity you are working with.
+  **Important:** Collection and Globals are keyed to a different property in the
+  `admin.components` object have slightly different options. Be sure to use the
+  correct key for the entity you are working with.
 </Banner>
 
 #### Collections
@@ -107,14 +101,14 @@ export const MyCollection: CollectionConfig = {
 
 The following options are available:
 
-| Path                  | Description                                                                                                                                                                                                         |
-|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `SaveButton`         | A button that saves the current document. [More details](#SaveButton).                                                                                                                                  |
-| `SaveDraftButton`    | A button that saves the current document as a draft. [More details](#SaveDraftButton).                                                                                                                                  |
-| `PublishButton`      | A button that publishes the current document. [More details](#PublishButton).                                                                                                                                  |
-| `PreviewButton`      | A button that previews the current document. [More details](#PreviewButton).                                                                                                                                  |
-| `Description`        | A description of the Collection. [More details](#Description).                                                                                                                                  |
-| `Upload`             | A file upload component. [More details](#Upload).                                                                                                                                  |
+| Path              | Description                                                                            |
+| ----------------- | -------------------------------------------------------------------------------------- |
+| `SaveButton`      | A button that saves the current document. [More details](#SaveButton).                 |
+| `SaveDraftButton` | A button that saves the current document as a draft. [More details](#SaveDraftButton). |
+| `PublishButton`   | A button that publishes the current document. [More details](#PublishButton).          |
+| `PreviewButton`   | A button that previews the current document. [More details](#PreviewButton).           |
+| `Description`     | A description of the Collection. [More details](#Description).                         |
+| `Upload`          | A file upload component. [More details](#Upload).                                      |
 
 #### Globals
 
@@ -139,13 +133,13 @@ export const MyGlobal: GlobalConfig = {
 
 The following options are available:
 
-| Path                  | Description                                                                                                                                                                                                         |
-|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `SaveButton`         | A button that saves the current document. [More details](#SaveButton).                                                                                                                                  |
-| `SaveDraftButton`    | A button that saves the current document as a draft. [More details](#SaveDraftButton).                                                                                                                                  |
-| `PublishButton`      | A button that publishes the current document. [More details](#PublishButton).                                                                                                                                  |
-| `PreviewButton`      | A button that previews the current document. [More details](#PreviewButton).                                                                                                                                  |
-| `Description`        | A description of the Global. [More details](#Description).                                                                                                                                  |
+| Path              | Description                                                                            |
+| ----------------- | -------------------------------------------------------------------------------------- |
+| `SaveButton`      | A button that saves the current document. [More details](#SaveButton).                 |
+| `SaveDraftButton` | A button that saves the current document as a draft. [More details](#SaveDraftButton). |
+| `PublishButton`   | A button that publishes the current document. [More details](#PublishButton).          |
+| `PreviewButton`   | A button that previews the current document. [More details](#PreviewButton).           |
+| `Description`     | A description of the Global. [More details](#Description).                             |
 
 ### SaveButton
 
@@ -164,7 +158,7 @@ export const MyCollection: CollectionConfig = {
         // highlight-start
         SaveButton: '/path/to/MySaveButton',
         // highlight-end
-      }
+      },
     },
   },
 }
@@ -180,9 +174,7 @@ import { SaveButton } from '@payloadcms/ui'
 import type { SaveButtonServerProps } from 'payload'
 
 export function MySaveButton(props: SaveButtonServerProps) {
-  return (
-    <SaveButton label="Save" />
-  )
+  return <SaveButton label="Save" />
 }
 ```
 
@@ -195,9 +187,7 @@ import { SaveButton } from '@payloadcms/ui'
 import type { SaveButtonClientProps } from 'payload'
 
 export function MySaveButton(props: SaveButtonClientProps) {
-  return (
-    <SaveButton label="Save" />
-  )
+  return <SaveButton label="Save" />
 }
 ```
 
@@ -218,7 +208,7 @@ export const MyCollection: CollectionConfig = {
         // highlight-start
         SaveDraftButton: '/path/to/MySaveDraftButton',
         // highlight-end
-      }
+      },
     },
   },
 }
@@ -234,9 +224,7 @@ import { SaveDraftButton } from '@payloadcms/ui'
 import type { SaveDraftButtonServerProps } from 'payload'
 
 export function MySaveDraftButton(props: SaveDraftButtonServerProps) {
-  return (
-    <SaveDraftButton />
-  )
+  return <SaveDraftButton />
 }
 ```
 
@@ -249,9 +237,7 @@ import { SaveDraftButton } from '@payloadcms/ui'
 import type { SaveDraftButtonClientProps } from 'payload'
 
 export function MySaveDraftButton(props: SaveDraftButtonClientProps) {
-  return (
-    <SaveDraftButton />
-  )
+  return <SaveDraftButton />
 }
 ```
 
@@ -272,7 +258,7 @@ export const MyCollection: CollectionConfig = {
         // highlight-start
         PublishButton: '/path/to/MyPublishButton',
         // highlight-end
-      }
+      },
     },
   },
 }
@@ -288,9 +274,7 @@ import { PublishButton } from '@payloadcms/ui'
 import type { PublishButtonClientProps } from 'payload'
 
 export function MyPublishButton(props: PublishButtonServerProps) {
-  return (
-    <PublishButton label="Publish" />
-  )
+  return <PublishButton label="Publish" />
 }
 ```
 
@@ -303,9 +287,7 @@ import { PublishButton } from '@payloadcms/ui'
 import type { PublishButtonClientProps } from 'payload'
 
 export function MyPublishButton(props: PublishButtonClientProps) {
-  return (
-    <PublishButton label="Publish" />
-  )
+  return <PublishButton label="Publish" />
 }
 ```
 
@@ -326,7 +308,7 @@ export const MyCollection: CollectionConfig = {
         // highlight-start
         PreviewButton: '/path/to/MyPreviewButton',
         // highlight-end
-      }
+      },
     },
   },
 }
@@ -342,9 +324,7 @@ import { PreviewButton } from '@payloadcms/ui'
 import type { PreviewButtonServerProps } from 'payload'
 
 export function MyPreviewButton(props: PreviewButtonServerProps) {
-  return (
-    <PreviewButton />
-  )
+  return <PreviewButton />
 }
 ```
 
@@ -357,9 +337,7 @@ import { PreviewButton } from '@payloadcms/ui'
 import type { PreviewButtonClientProps } from 'payload'
 
 export function MyPreviewButton(props: PreviewButtonClientProps) {
-  return (
-    <PreviewButton />
-  )
+  return <PreviewButton />
 }
 ```
 
@@ -385,8 +363,8 @@ export const MyCollection: CollectionConfig = {
 ```
 
 <Banner type="warning">
-  **Note:**
-  The `Description` component is shared between the Edit View and the [List View](./list-view).
+  **Note:** The `Description` component is shared between the Edit View and the
+  [List View](./list-view).
 </Banner>
 
 Here's an example of a custom `Description` component:
@@ -398,11 +376,7 @@ import React from 'react'
 import type { ViewDescriptionServerProps } from 'payload'
 
 export function MyDescriptionComponent(props: ViewDescriptionServerProps) {
-  return (
-    <div>
-      This is a custom description component (Server)
-    </div>
-  )
+  return <div>This is a custom description component (Server)</div>
 }
 ```
 
@@ -414,11 +388,7 @@ import React from 'react'
 import type { ViewDescriptionClientProps } from 'payload'
 
 export function MyDescriptionComponent(props: ViewDescriptionClientProps) {
-  return (
-    <div>
-      This is a custom description component (Client)
-    </div>
-  )
+  return <div>This is a custom description component (Client)</div>
 }
 ```
 
@@ -439,15 +409,14 @@ export const MyCollection: CollectionConfig = {
         // highlight-start
         Upload: '/path/to/MyUploadComponent',
         // highlight-end
-      }
+      },
     },
   },
 }
 ```
 
 <Banner type="warning">
-  **Note:**
-  The Upload component is only available for Collections.
+  **Note:** The Upload component is only available for Collections.
 </Banner>
 
 Here's an example of a custom `Upload` component:
@@ -456,8 +425,6 @@ Here's an example of a custom `Upload` component:
 import React from 'react'
 
 export function MyUploadComponent() {
-  return (
-    <input type="file" />
-  )
+  return <input type="file" />
 }
 ```

docs/custom-components/list-view.mdx

@@ -6,13 +6,14 @@ desc:
 keywords: admin, components, custom, documentation, Content Management System, cms, headless, javascript, node, react, nextjs
 ---
 
-The List View is where users interact with a list of [Collection](../collections/overview) Documents within the [Admin Panel](../admin/overview). This is where they can view, sort, filter, and paginate their documents to find exactly what they're looking for. This is also where users can perform bulk operations on multiple documents at once, such as deleting, editing, or publishing many.
+The List View is where users interact with a list of [Collection](../configuration/collections) Documents within the [Admin Panel](../admin/overview). This is where they can view, sort, filter, and paginate their documents to find exactly what they're looking for. This is also where users can perform bulk operations on multiple documents at once, such as deleting, editing, or publishing many.
 
 The List View can be swapped out in its entirety for a Custom View, or it can be injected with a number of Custom Components to add additional functionality or presentational elements without replacing the entire view.
 
 <Banner type="info">
-  **Note:**
-  Only [Collections](../collections/overview) have a List View. [Globals](../globals/overview) do not have a List View as they are single documents.
+  **Note:** Only [Collections](../configuration/collections) have a List View.
+  [Globals](../configuration/globals) do not have a List View as they are single
+  documents.
 </Banner>
 
 ## Custom List View
@@ -46,11 +47,7 @@ import type { ListViewServerProps } from 'payload'
 import { DefaultListView } from '@payloadcms/ui'
 
 export function MyCustomServerListView(props: ListViewServerProps) {
-  return (
-    <div>
-      This is a custom List View (Server)
-    </div>
-  )
+  return <div>This is a custom List View (Server)</div>
 }
 ```
 
@@ -62,11 +59,7 @@ import React from 'react'
 import type { ListViewClientProps } from 'payload'
 
 export function MyCustomClientListView(props: ListViewClientProps) {
-  return (
-    <div>
-      This is a custom List View (Client)
-    </div>
-  )
+  return <div>This is a custom List View (Client)</div>
 }
 ```
 
@@ -95,13 +88,13 @@ export const MyCollection: CollectionConfig = {
 
 The following options are available:
 
-| Path                  | Description                                                                                                                  |
-|-----------------------|----------------------------------------------------------------------------------------------------------------------------- |
-| `beforeList`          | An array of custom components to inject before the list of documents in the List View. [More details](#beforeList).          |
-| `beforeListTable`     | An array of custom components to inject before the table of documents in the List View. [More details](#beforeListTable).    |
-| `afterList`           | An array of custom components to inject after the list of documents in the List View. [More details](#afterList).            |
-| `afterListTable`      | An array of custom components to inject after the table of documents in the List View. [More details](#afterListTable).      |
-| `Description`         | A component to render a description of the Collection. [More details](#Description).                                         |
+| Path              | Description                                                                                                               |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------- |
+| `beforeList`      | An array of custom components to inject before the list of documents in the List View. [More details](#beforelist).       |
+| `beforeListTable` | An array of custom components to inject before the table of documents in the List View. [More details](#beforelisttable). |
+| `afterList`       | An array of custom components to inject after the list of documents in the List View. [More details](#afterlist).         |
+| `afterListTable`  | An array of custom components to inject after the table of documents in the List View. [More details](#afterlisttable).   |
+| `Description`     | A component to render a description of the Collection. [More details](#description).                                      |
 
 ### beforeList
 
@@ -117,9 +110,7 @@ export const MyCollection: CollectionConfig = {
   admin: {
     components: {
       // highlight-start
-      beforeList: [
-        '/path/to/MyBeforeListComponent',
-      ],
+      beforeList: ['/path/to/MyBeforeListComponent'],
       // highlight-end
     },
   },
@@ -135,11 +126,7 @@ import React from 'react'
 import type { BeforeListServerProps } from 'payload'
 
 export function MyBeforeListComponent(props: BeforeListServerProps) {
-  return (
-    <div>
-      This is a custom beforeList component (Server)
-    </div>
-  )
+  return <div>This is a custom beforeList component (Server)</div>
 }
 ```
 
@@ -151,11 +138,7 @@ import React from 'react'
 import type { BeforeListClientProps } from 'payload'
 
 export function MyBeforeListComponent(props: BeforeListClientProps) {
-  return (
-    <div>
-      This is a custom beforeList component (Client)
-    </div>
-  )
+  return <div>This is a custom beforeList component (Client)</div>
 }
 ```
 
@@ -173,9 +156,7 @@ export const MyCollection: CollectionConfig = {
   admin: {
     components: {
       // highlight-start
-      beforeListTable: [
-        '/path/to/MyBeforeListTableComponent',
-      ],
+      beforeListTable: ['/path/to/MyBeforeListTableComponent'],
       // highlight-end
     },
   },
@@ -191,11 +172,7 @@ import React from 'react'
 import type { BeforeListTableServerProps } from 'payload'
 
 export function MyBeforeListTableComponent(props: BeforeListTableServerProps) {
-  return (
-    <div>
-      This is a custom beforeListTable component (Server)
-    </div>
-  )
+  return <div>This is a custom beforeListTable component (Server)</div>
 }
 ```
 
@@ -207,11 +184,7 @@ import React from 'react'
 import type { BeforeListTableClientProps } from 'payload'
 
 export function MyBeforeListTableComponent(props: BeforeListTableClientProps) {
-  return (
-    <div>
-      This is a custom beforeListTable component (Client)
-    </div>
-  )
+  return <div>This is a custom beforeListTable component (Client)</div>
 }
 ```
 
@@ -229,9 +202,7 @@ export const MyCollection: CollectionConfig = {
   admin: {
     components: {
       // highlight-start
-      afterList: [
-        '/path/to/MyAfterListComponent',
-      ],
+      afterList: ['/path/to/MyAfterListComponent'],
       // highlight-end
     },
   },
@@ -247,11 +218,7 @@ import React from 'react'
 import type { AfterListServerProps } from 'payload'
 
 export function MyAfterListComponent(props: AfterListServerProps) {
-  return (
-    <div>
-      This is a custom afterList component (Server)
-    </div>
-  )
+  return <div>This is a custom afterList component (Server)</div>
 }
 ```
 
@@ -263,11 +230,7 @@ import React from 'react'
 import type { AfterListClientProps } from 'payload'
 
 export function MyAfterListComponent(props: AfterListClientProps) {
-  return (
-    <div>
-      This is a custom afterList component (Client)
-    </div>
-  )
+  return <div>This is a custom afterList component (Client)</div>
 }
 ```
 
@@ -285,9 +248,7 @@ export const MyCollection: CollectionConfig = {
   admin: {
     components: {
       // highlight-start
-      afterListTable: [
-        '/path/to/MyAfterListTableComponent',
-      ],
+      afterListTable: ['/path/to/MyAfterListTableComponent'],
       // highlight-end
     },
   },
@@ -303,11 +264,7 @@ import React from 'react'
 import type { AfterListTableServerProps } from 'payload'
 
 export function MyAfterListTableComponent(props: AfterListTableServerProps) {
-  return (
-    <div>
-      This is a custom afterListTable component (Server)
-    </div>
-  )
+  return <div>This is a custom afterListTable component (Server)</div>
 }
 ```
 
@@ -319,11 +276,7 @@ import React from 'react'
 import type { AfterListTableClientProps } from 'payload'
 
 export function MyAfterListTableComponent(props: AfterListTableClientProps) {
-  return (
-    <div>
-      This is a custom afterListTable component (Client)
-    </div>
-  )
+  return <div>This is a custom afterListTable component (Client)</div>
 }
 ```
 
@@ -349,8 +302,8 @@ export const MyCollection: CollectionConfig = {
 ```
 
 <Banner type="warning">
-  **Note:**
-  The `Description` component is shared between the List View and the [Edit View](./edit-view).
+  **Note:** The `Description` component is shared between the List View and the
+  [Edit View](./edit-view).
 </Banner>
 
 Here's an example of a custom `Description` component:
@@ -362,11 +315,7 @@ import React from 'react'
 import type { ViewDescriptionServerProps } from 'payload'
 
 export function MyDescriptionComponent(props: ViewDescriptionServerProps) {
-  return (
-    <div>
-      This is a custom Collection description component (Server)
-    </div>
-  )
+  return <div>This is a custom Collection description component (Server)</div>
 }
 ```
 
@@ -378,10 +327,6 @@ import React from 'react'
 import type { ViewDescriptionClientProps } from 'payload'
 
 export function MyDescriptionComponent(props: ViewDescriptionClientProps) {
-  return (
-    <div>
-      This is a custom Collection description component (Client)
-    </div>
-  )
+  return <div>This is a custom Collection description component (Client)</div>
 }
 ```

docs/custom-components/overview.mdx

@@ -11,8 +11,12 @@ The Payload [Admin Panel](../admin/overview) is designed to be as minimal and st
 All Custom Components in Payload are [React Server Components](https://react.dev/reference/rsc/server-components) by default. This enables the use of the [Local API](../local-api/overview) directly on the front-end. Custom Components are available for nearly every part of the Admin Panel for extreme granularity and control.
 
 <Banner type="success">
-  **Note:**
-  Client Components continue to be fully supported. To use Client Components in your app, simply include the `'use client'` directive. Payload will automatically detect and remove all [non-serializable](https://react.dev/reference/rsc/use-client#serializable-types) default props before rendering your component. [More details](#client-components).
+  **Note:** Client Components continue to be fully supported. To use Client
+  Components in your app, simply include the `'use client'` directive. Payload
+  will automatically detect and remove all
+  [non-serializable](https://react.dev/reference/rsc/use-client#serializable-types)
+  default props before rendering your component. [More
+  details](#client-components).
 </Banner>
 
 There are four main types of Custom Components in Payload:
@@ -38,16 +42,17 @@ const config = buildConfig({
   admin: {
     components: {
       logout: {
-        Button: '/src/components/Logout#MyComponent' // highlight-line
-      }
-    }
+        Button: '/src/components/Logout#MyComponent', // highlight-line
+      },
+    },
   },
 })
 ```
 
 <Banner type="success">
-  **Note:**
-  All Custom Components can be either Server Components or Client Components, depending on the presence of the `'use client'` directive at the top of the file.
+  **Note:** All Custom Components can be either Server Components or Client
+  Components, depending on the presence of the `'use client'` directive at the
+  top of the file.
 </Banner>
 
 ### Component Paths
@@ -73,9 +78,9 @@ const config = buildConfig({
     },
     components: {
       logout: {
-        Button: '/components/Logout#MyComponent' // highlight-line
-      }
-    }
+        Button: '/components/Logout#MyComponent', // highlight-line
+      },
+    },
   },
 })
 ```
@@ -98,10 +103,10 @@ const config = buildConfig({
         Button: {
           path: '/src/components/Logout',
           exportName: 'MyComponent',
-        }
+        },
         // highlight-end
-      }
-    }
+      },
+    },
   },
 })
 ```
@@ -109,20 +114,47 @@ const config = buildConfig({
 The following options are available:
 
 | Property      | Description                                                                                                                   |
-|---------------|-------------------------------------------------------------------------------------------------------------------------------|
-| `clientProps` | Props to be passed to the Custom Components if it's a Client Component. [More details](#custom-props).                         |
+| ------------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| `clientProps` | Props to be passed to the Custom Components if it's a Client Component. [More details](#custom-props).                        |
 | `exportName`  | Instead of declaring named exports using `#` in the component path, you can also omit them from `path` and pass them in here. |
-| `path`        | File path to the Custom Component. Named exports can be appended to the end of the path, separated by a `#`.                         |
+| `path`        | File path to the Custom Component. Named exports can be appended to the end of the path, separated by a `#`.                  |
 | `serverProps` | Props to be passed to the Custom Component if it's a Server Component. [More details](#custom-props).                         |
 
 For details on how to build Custom Components, see [Building Custom Components](#building-custom-components).
 
 ### Import Map
 
-In order for Payload to make use of [Component Paths](#component-paths), an "Import Map" is automatically generated at `app/(payload)/admin/importMap.js`. This file contains every Custom Component in your config, keyed to their respective paths. When Payload needs to lookup a component, it uses this file to find the correct import.
+In order for Payload to make use of [Component Paths](#component-paths), an "Import Map" is automatically generated at either `src/app/(payload)/admin/importMap.js` or `app/(payload)/admin/importMap.js`. This file contains every Custom Component in your config, keyed to their respective paths. When Payload needs to lookup a component, it uses this file to find the correct import.
 
 The Import Map is automatically regenerated at startup and whenever Hot Module Replacement (HMR) runs, or you can run `payload generate:importmap` to manually regenerate it.
 
+#### Overriding Import Map Location
+
+Using the `config.admin.importMap.importMapFile` property, you can override the location of the import map. This is useful if you want to place the import map in a different location, or if you want to use a custom file name.
+
+```ts
+import { buildConfig } from 'payload'
+import { fileURLToPath } from 'node:url'
+import path from 'path'
+const filename = fileURLToPath(import.meta.url)
+const dirname = path.dirname(filename)
+
+const config = buildConfig({
+  // ...
+  admin: {
+    importMap: {
+      baseDir: path.resolve(dirname, 'src'),
+      importMapFile: path.resolve(
+        dirname,
+        'app',
+        '(payload)',
+        'custom-import-map.js',
+      ), // highlight-line
+    },
+  },
+})
+```
+
 #### Custom Imports
 
 If needed, custom items can be appended onto the Import Map. This is mostly only relevant for plugin authors who need to add a custom import that is not referenced in a known location.
@@ -137,7 +169,8 @@ export default buildConfig({
   admin: {
     // ...
     dependencies: {
-      myTestComponent: { // myTestComponent is the key - can be anything
+      myTestComponent: {
+        // myTestComponent is the key - can be anything
         path: '/components/TestComponent.js#TestComponent',
         type: 'component',
         clientProps: {
@@ -145,8 +178,8 @@ export default buildConfig({
         },
       },
     },
-  }
-}
+  },
+})
 ```
 
 ## Building Custom Components
@@ -164,7 +197,7 @@ import React from 'react'
 import type { Payload } from 'payload'
 
 async function MyServerComponent({
-  payload // highlight-line
+  payload, // highlight-line
 }: {
   payload: Payload
 }) {
@@ -173,22 +206,25 @@ async function MyServerComponent({
     id: '123',
   })
 
-  return (
-    <p>{page.title}</p>
-  )
+  return <p>{page.title}</p>
 }
 ```
 
 Each Custom Component receives the following props by default:
 
-| Prop                      | Description                                                                                           |
-| ------------------------- | ----------------------------------------------------------------------------------------------------- |
-| `payload`                 | The [Payload](../local-api/overview) class.                                                           |
-| `i18n`                    | The [i18n](../configuration/i18n) object.                                                                           |
+| Prop      | Description                                 |
+| --------- | ------------------------------------------- |
+| `payload` | The [Payload](../local-api/overview) class. |
+| `i18n`    | The [i18n](../configuration/i18n) object.   |
 
 <Banner type="warning">
-  **Reminder:**
-  All Custom Components also receive various other props that are specific to the component being rendered. See [Root Components](#root-components), [Collection Components](../configuration/collections#custom-components), [Global Components](../configuration/globals#custom-components), or [Field Components](../fields/overview#custom-components) for a complete list of all default props per component.
+  **Reminder:** All Custom Components also receive various other props that are
+  specific to the component being rendered. See [Root
+  Components](#root-components), [Collection
+  Components](../configuration/collections#custom-components), [Global
+  Components](../configuration/globals#custom-components), or [Field
+  Components](../fields/overview#custom-components) for a complete list of all
+  default props per component.
 </Banner>
 
 ### Custom Props
@@ -200,17 +236,18 @@ import { buildConfig } from 'payload'
 
 const config = buildConfig({
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     components: {
       logout: {
         Button: {
           path: '/src/components/Logout#MyComponent',
           clientProps: {
-            myCustomProp: 'Hello, World!' // highlight-line
+            myCustomProp: 'Hello, World!', // highlight-line
           },
-        }
-      }
-    }
+        },
+      },
+    },
   },
 })
 ```
@@ -222,9 +259,7 @@ import React from 'react'
 import { Link } from '@payloadcms/ui'
 
 export function MyComponent({ myCustomProp }: { myCustomProp: string }) {
-  return (
-    <Link href="/admin/logout">{myCustomProp}</Link>
-  )
+  return <Link href="/admin/logout">{myCustomProp}</Link>
 }
 ```
 
@@ -242,16 +277,16 @@ export function MyClientComponent() {
   const [count, setCount] = useState(0)
 
   return (
-    <button onClick={() => setCount(count + 1)}>
-      Clicked {count} times
-    </button>
+    <button onClick={() => setCount(count + 1)}>Clicked {count} times</button>
   )
 }
 ```
 
 <Banner type="warning">
-  **Reminder:**
-  Client Components cannot be passed [non-serializable props](https://react.dev/reference/rsc/use-client#serializable-types). If you are rendering your Client Component _from within_ a Server Component, ensure that its props are serializable.
+  **Reminder:** Client Components cannot be passed [non-serializable
+  props](https://react.dev/reference/rsc/use-client#serializable-types). If you
+  are rendering your Client Component _from within_ a Server Component, ensure
+  that its props are serializable.
 </Banner>
 
 ### Accessing the Payload Config
@@ -263,20 +298,16 @@ import React from 'react'
 
 export default async function MyServerComponent({
   payload: {
-    config // highlight-line
-  }
+    config, // highlight-line
+  },
 }) {
-  return (
-    <Link href={config.serverURL}>
-      Go Home
-    </Link>
-  )
+  return <Link href={config.serverURL}>Go Home</Link>
 }
 ```
 
 But, the Payload Config is [non-serializable](https://react.dev/reference/rsc/use-client#serializable-types) by design. It is full of custom validation functions and more. This means that the Payload Config, in its entirety, cannot be passed directly to Client Components.
 
-For this reason, Payload creates a Client Config and passes it into the Config Provider. This is a serializable version of the Payload Config that can be accessed from any Client Component via the [`useConfig`](../admin/hooks#useconfig) hook:
+For this reason, Payload creates a Client Config and passes it into the Config Provider. This is a serializable version of the Payload Config that can be accessed from any Client Component via the [`useConfig`](../admin/react-hooks#useconfig) hook:
 
 ```tsx
 'use client'
@@ -285,14 +316,12 @@ import { useConfig } from '@payloadcms/ui'
 
 export function MyClientComponent() {
   // highlight-start
-  const { config: { serverURL } } = useConfig()
+  const {
+    config: { serverURL },
+  } = useConfig()
   // highlight-end
 
-  return (
-    <Link href={serverURL}>
-      Go Home
-    </Link>
-  )
+  return <Link href={serverURL}>Go Home</Link>
 }
 ```
 
@@ -308,12 +337,10 @@ Within Server Components, this prop is named `field`:
 import React from 'react'
 import type { TextFieldServerComponent } from 'payload'
 
-export const MyClientFieldComponent: TextFieldServerComponent = ({ field: { name } }) => {
-  return (
-    <p>
-      {`This field's name is ${name}`}
-    </p>
-  )
+export const MyClientFieldComponent: TextFieldServerComponent = ({
+  field: { name },
+}) => {
+  return <p>{`This field's name is ${name}`}</p>
 }
 ```
 
@@ -324,12 +351,10 @@ Within Client Components, this prop is named `clientField` because its non-seria
 import React from 'react'
 import type { TextFieldClientComponent } from 'payload'
 
-export const MyClientFieldComponent: TextFieldClientComponent = ({ clientField: { name } }) => {
-  return (
-    <p>
-      {`This field's name is ${name}`}
-    </p>
-  )
+export const MyClientFieldComponent: TextFieldClientComponent = ({
+  clientField: { name },
+}) => {
+  return <p>{`This field's name is ${name}`}</p>
 }
 ```
 
@@ -348,9 +373,7 @@ import { getTranslation } from '@payloadcms/translations'
 export default async function MyServerComponent({ i18n }) {
   const translatedTitle = getTranslation(myTranslation, i18n) // highlight-line
 
-  return (
-    <p>{translatedTitle}</p>
-  )
+  return <p>{translatedTitle}</p>
 }
 ```
 
@@ -375,7 +398,8 @@ export function MyClientComponent() {
 ```
 
 <Banner type="success">
-  See the [Hooks](../admin/hooks) documentation for a full list of available hooks.
+  See the [Hooks](../admin/react-hooks) documentation for a full list of
+  available hooks.
 </Banner>
 
 ### Getting the Current Locale
@@ -394,9 +418,7 @@ export default async function MyServerComponent({ payload, locale }) {
     locale,
   })
 
-  return (
-    <p>{localizedPage.title}</p>
-  )
+  return <p>{localizedPage.title}</p>
 }
 ```
 
@@ -415,19 +437,18 @@ function Greeting() {
     es: 'Hola',
   }
 
-  return (
-    <span>{trans[locale.code]}</span>
-  )
+  return <span>{trans[locale.code]}</span>
 }
 ```
 
 <Banner type="success">
-  See the [Hooks](../admin/hooks) documentation for a full list of available hooks.
+  See the [Hooks](../admin/react-hooks) documentation for a full list of
+  available hooks.
 </Banner>
 
 ### Using Hooks
 
-To make it easier to [build your Custom Components](#building-custom-components), you can use [Payload's built-in React Hooks](../admin/hooks) in any Client Component. For example, you might want to interact with one of Payload's many React Contexts. To do this, you can use one of the many hooks available depending on your needs.
+To make it easier to [build your Custom Components](#building-custom-components), you can use [Payload's built-in React Hooks](../admin/react-hooks) in any Client Component. For example, you might want to interact with one of Payload's many React Contexts. To do this, you can use one of the many hooks available depending on your needs.
 
 ```tsx
 'use client'
@@ -437,14 +458,13 @@ import { useDocumentInfo } from '@payloadcms/ui'
 export function MyClientComponent() {
   const { slug } = useDocumentInfo() // highlight-line
 
-  return (
-    <p>{`Entity slug: ${slug}`}</p>
-  )
+  return <p>{`Entity slug: ${slug}`}</p>
 }
 ```
 
 <Banner type="success">
-  See the [Hooks](../admin/hooks) documentation for a full list of available hooks.
+  See the [Hooks](../admin/react-hooks) documentation for a full list of
+  available hooks.
 </Banner>
 
 ### Adding Styles
@@ -457,11 +477,7 @@ To apply custom styles, simply import your own `.css` or `.scss` file into your
 import './index.scss'
 
 export function MyComponent() {
-  return (
-    <div className="my-component">
-      My Custom Component
-    </div>
-  )
+  return <div className="my-component">My Custom Component</div>
 }
 ```
 
@@ -486,6 +502,6 @@ Payload also exports its [SCSS](https://sass-lang.com) library for reuse which i
 ```
 
 <Banner type="success">
-  **Note:**
-  You can also drill into Payload's own component styles, or easily apply global, app-wide CSS. More on that [here](../admin/customizing-css).
+  **Note:** You can also drill into Payload's own component styles, or easily
+  apply global, app-wide CSS. More on that [here](../admin/customizing-css).
 </Banner>

docs/custom-components/root-components.mdx

@@ -31,28 +31,30 @@ export default buildConfig({
 
 The following options are available:
 
-| Path                  | Description                                                                                                                                                                                                         |
-|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `actions`         | An array of Custom Components to be rendered _within_ the header of the Admin Panel, providing additional interactivity and functionality. [More details](#actions).                                                |
-| `afterDashboard`  | An array of Custom Components to inject into the built-in Dashboard, _after_ the default dashboard contents. [More details](#afterdashboard).                                                                        |
-| `afterLogin`      | An array of Custom Components to inject into the built-in Login, _after_ the default login form. [More details](#afterlogin).                                                                                       |
-| `afterNavLinks`   | An array of Custom Components to inject into the built-in Nav, _after_ the links. [More details](#afternavlinks).                                                                                                  |
-| `beforeDashboard` | An array of Custom Components to inject into the built-in Dashboard, _before_ the default dashboard contents. [More details](#beforedashboard).                                                                      |
-| `beforeLogin`     | An array of Custom Components to inject into the built-in Login, _before_ the default login form. [More details](#beforelogin).                                                                                     |
-| `beforeNavLinks`  | An array of Custom Components to inject into the built-in Nav, _before_ the links themselves. [More details](#beforenavlinks).                                                                                      |
-| `graphics.Icon`   | The simplified logo used in contexts like the the `Nav` component. [More details](#graphicsicon).                                                                                                                  |
-| `graphics.Logo`   | The full logo used in contexts like the `Login` view. [More details](#graphicslogo).                                                                                                                               |
-| `header`          | An array of Custom Components to be injected above the Payload header. [More details](#header).                                                                                                                    |
-| `logout.Button`   | The button displayed in the sidebar that logs the user out. [More details](#logoutbutton).                                                                                                                         |
-| `Nav`             | Contains the sidebar / mobile menu in its entirety. [More details](#nav).                                                                                                                                         |
-| `providers`       | Custom [React Context](https://react.dev/learn/scaling-up-with-reducer-and-context) providers that will wrap the entire Admin Panel. [More details](./custom-providers).                                       |
-| `views`           | Override or create new views within the Admin Panel. [More details](./custom-views).                                                                                                                                 |
+| Path              | Description                                                                                                                                                              |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `actions`         | An array of Custom Components to be rendered _within_ the header of the Admin Panel, providing additional interactivity and functionality. [More details](#actions).     |
+| `afterDashboard`  | An array of Custom Components to inject into the built-in Dashboard, _after_ the default dashboard contents. [More details](#afterdashboard).                            |
+| `afterLogin`      | An array of Custom Components to inject into the built-in Login, _after_ the default login form. [More details](#afterlogin).                                            |
+| `afterNavLinks`   | An array of Custom Components to inject into the built-in Nav, _after_ the links. [More details](#afternavlinks).                                                        |
+| `beforeDashboard` | An array of Custom Components to inject into the built-in Dashboard, _before_ the default dashboard contents. [More details](#beforedashboard).                          |
+| `beforeLogin`     | An array of Custom Components to inject into the built-in Login, _before_ the default login form. [More details](#beforelogin).                                          |
+| `beforeNavLinks`  | An array of Custom Components to inject into the built-in Nav, _before_ the links themselves. [More details](#beforenavlinks).                                           |
+| `graphics.Icon`   | The simplified logo used in contexts like the the `Nav` component. [More details](#graphicsicon).                                                                        |
+| `graphics.Logo`   | The full logo used in contexts like the `Login` view. [More details](#graphicslogo).                                                                                     |
+| `header`          | An array of Custom Components to be injected above the Payload header. [More details](#header).                                                                          |
+| `logout.Button`   | The button displayed in the sidebar that logs the user out. [More details](#logoutbutton).                                                                               |
+| `Nav`             | Contains the sidebar / mobile menu in its entirety. [More details](#nav).                                                                                                |
+| `providers`       | Custom [React Context](https://react.dev/learn/scaling-up-with-reducer-and-context) providers that will wrap the entire Admin Panel. [More details](./custom-providers). |
+| `views`           | Override or create new views within the Admin Panel. [More details](./custom-views).                                                                                     |
 
 _For details on how to build Custom Components, see [Building Custom Components](./overview#building-custom-components)._
 
 <Banner type="success">
-  **Note:**
-  You can also use set [Collection Components](../configuration/collections#custom-components) and [Global Components](../configuration/globals#custom-components) in their respective configs.
+  **Note:** You can also use set [Collection
+  Components](../configuration/collections#custom-components) and [Global
+  Components](../configuration/globals#custom-components) in their respective
+  configs.
 </Banner>
 
 ## Components
@@ -71,9 +73,7 @@ export default buildConfig({
   admin: {
     // highlight-start
     components: {
-      actions: [
-        '/path/to/your/component',
-      ],
+      actions: ['/path/to/your/component'],
     },
     // highlight-end
   },
@@ -93,8 +93,8 @@ export default function MyCustomAction() {
 ```
 
 <Banner type="success">
-  **Note:**
-  You can also use add Actions to the [Edit View](./edit-view) and [List View](./list-view) in their respective configs.
+  **Note:** You can also use add Actions to the [Edit View](./edit-view) and
+  [List View](./list-view) in their respective configs.
 </Banner>
 
 ### beforeDashboard
@@ -111,9 +111,7 @@ export default buildConfig({
   admin: {
     // highlight-start
     components: {
-      beforeDashboard: [
-        '/path/to/your/component',
-      ],
+      beforeDashboard: ['/path/to/your/component'],
     },
     // highlight-end
   },
@@ -124,11 +122,7 @@ Here is an example of a simple `beforeDashboard` component:
 
 ```tsx
 export default function MyBeforeDashboardComponent() {
-  return (
-    <div>
-      This is a custom component injected before the Dashboard.
-    </div>
-  )
+  return <div>This is a custom component injected before the Dashboard.</div>
 }
 ```
 
@@ -146,9 +140,7 @@ export default buildConfig({
   admin: {
     // highlight-start
     components: {
-      afterDashboard: [
-        '/path/to/your/component',
-      ],
+      afterDashboard: ['/path/to/your/component'],
     },
     // highlight-end
   },
@@ -159,11 +151,7 @@ Here is an example of a simple `afterDashboard` component:
 
 ```tsx
 export default function MyAfterDashboardComponent() {
-  return (
-    <div>
-      This is a custom component injected after the Dashboard.
-    </div>
-  )
+  return <div>This is a custom component injected after the Dashboard.</div>
 }
 ```
 
@@ -181,9 +169,7 @@ export default buildConfig({
   admin: {
     // highlight-start
     components: {
-      beforeLogin: [
-        '/path/to/your/component',
-      ],
+      beforeLogin: ['/path/to/your/component'],
     },
     // highlight-end
   },
@@ -194,11 +180,7 @@ Here is an example of a simple `beforeLogin` component:
 
 ```tsx
 export default function MyBeforeLoginComponent() {
-  return (
-    <div>
-      This is a custom component injected before the Login form.
-    </div>
-  )
+  return <div>This is a custom component injected before the Login form.</div>
 }
 ```
 
@@ -216,9 +198,7 @@ export default buildConfig({
   admin: {
     // highlight-start
     components: {
-      afterLogin: [
-        '/path/to/your/component',
-      ],
+      afterLogin: ['/path/to/your/component'],
     },
     // highlight-end
   },
@@ -229,11 +209,7 @@ Here is an example of a simple `afterLogin` component:
 
 ```tsx
 export default function MyAfterLoginComponent() {
-  return (
-    <div>
-      This is a custom component injected after the Login form.
-    </div>
-  )
+  return <div>This is a custom component injected after the Login form.</div>
 }
 ```
 
@@ -251,9 +227,7 @@ export default buildConfig({
   admin: {
     // highlight-start
     components: {
-      beforeNavLinks: [
-        '/path/to/your/component',
-      ],
+      beforeNavLinks: ['/path/to/your/component'],
     },
     // highlight-end
   },
@@ -264,11 +238,7 @@ Here is an example of a simple `beforeNavLinks` component:
 
 ```tsx
 export default function MyBeforeNavLinksComponent() {
-  return (
-    <div>
-      This is a custom component injected before the Nav links.
-    </div>
-  )
+  return <div>This is a custom component injected before the Nav links.</div>
 }
 ```
 
@@ -286,9 +256,7 @@ export default buildConfig({
   admin: {
     // highlight-start
     components: {
-      afterNavLinks: [
-        '/path/to/your/component',
-      ],
+      afterNavLinks: ['/path/to/your/component'],
     },
     // highlight-end
   },
@@ -299,9 +267,7 @@ Here is an example of a simple `afterNavLinks` component:
 
 ```tsx
 export default function MyAfterNavLinksComponent() {
-  return (
-    <p>This is a custom component injected after the Nav links.</p>
-  )
+  return <p>This is a custom component injected after the Nav links.</p>
 }
 ```
 
@@ -336,9 +302,7 @@ export default function MyCustomNav() {
     <nav>
       <ul>
         <li>
-          <Link href="/dashboard">
-            Dashboard
-          </Link>
+          <Link href="/dashboard">Dashboard</Link>
         </li>
       </ul>
     </nav>
@@ -373,9 +337,7 @@ Here is an example of a simple `Icon` component:
 
 ```tsx
 export default function MyCustomIcon() {
-  return (
-    <img src="/path/to/your/icon.png" alt="My Custom Icon" />
-  )
+  return <img src="/path/to/your/icon.png" alt="My Custom Icon" />
 }
 ```
 
@@ -406,9 +368,7 @@ Here is an example of a simple `Logo` component:
 
 ```tsx
 export default function MyCustomLogo() {
-  return (
-    <img src="/path/to/your/logo.png" alt="My Custom Logo" />
-  )
+  return <img src="/path/to/your/logo.png" alt="My Custom Logo" />
 }
 ```
 
@@ -428,9 +388,7 @@ export default buildConfig({
   admin: {
     // highlight-start
     components: {
-      Header: [
-        '/path/to/your/component'
-      ],
+      Header: ['/path/to/your/component'],
     },
     // highlight-end
   },
@@ -465,7 +423,7 @@ export default buildConfig({
     components: {
       logout: {
         Button: '/path/to/your/component',
-      }
+      },
     },
     // highlight-end
   },
@@ -476,10 +434,6 @@ Here is an example of a simple `logout.Button` component:
 
 ```tsx
 export default function MyCustomLogoutButton() {
-  return (
-    <button onClick={() => alert('Logging out!')}>
-      Log Out
-    </button>
-  )
+  return <button onClick={() => alert('Logging out!')}>Log Out</button>
 }
 ```

docs/database/migrations.mdx

@@ -20,8 +20,9 @@ Ensure you have an npm script called "payload" in your `package.json` file.
 ```
 
 <Banner>
-  Note that you need to run Payload migrations through the package manager that you are using,
-  because Payload should not be globally installed on your system.
+  Note that you need to run Payload migrations through the package manager that
+  you are using, because Payload should not be globally installed on your
+  system.
 </Banner>
 
 ## Migration file contents
@@ -52,7 +53,7 @@ export async function down({ payload, req }: MigrateDownArgs): Promise<void> {
 ## Using Transactions
 
 When migrations are run, each migration is performed in a new [transaction](/docs/database/transactions) for you. All
-you need to do is pass the `req` object to any [local API](/docs/local-api/overview) or direct database calls, such as
+you need to do is pass the `req` object to any [Local API](/docs/local-api/overview) or direct database calls, such as
 `payload.db.updateMany()`, to make database changes inside the transaction. Assuming no errors were thrown, the transaction is committed
 after your `up` or `down` function runs. If the migration errors at any point or fails to commit, it is caught and the
 transaction gets aborted. This way no change is made to the database if the migration fails.
@@ -62,15 +63,23 @@ transaction gets aborted. This way no change is made to the database if the migr
 Additionally, you can bypass Payload's layer entirely and perform operations directly on your underlying database within the active transaction:
 
 ### MongoDB:
+
 ```ts
 import { type MigrateUpArgs } from '@payloadcms/db-mongodb'
 
-export async function up({ session, payload, req }: MigrateUpArgs): Promise<void> {
-  const posts = await payload.db.collections.posts.collection.find({ session }).toArray()
+export async function up({
+  session,
+  payload,
+  req,
+}: MigrateUpArgs): Promise<void> {
+  const posts = await payload.db.collections.posts.collection
+    .find({ session })
+    .toArray()
 }
 ```
 
 ### Postgres:
+
 ```ts
 import { type MigrateUpArgs, sql } from '@payloadcms/db-postgres'
 
@@ -80,7 +89,9 @@ export async function up({ db, payload, req }: MigrateUpArgs): Promise<void> {
 ```
 
 ### SQLite:
+
 In SQLite, transactions are disabled by default. [More](./transactions).
+
 ```ts
 import { type MigrateUpArgs, sql } from '@payloadcms/db-sqlite'
 
@@ -118,6 +129,11 @@ default, migrations will be named using a timestamp.
 npm run payload migrate:create optional-name-here
 ```
 
+Flags:
+
+- `--skip-empty`: with Postgres, it skips the "no schema changes detected. Would you like to create a blank migration file?" prompt which can be useful for generating migration in CI.
+- `--force-accept-warning`: accepts any command prompts, creates a blank migration even if there weren't any changes to the schema.
+
 ### Status
 
 The `migrate:status` command will check the status of migrations and output a table of which migrations have been run,
@@ -196,9 +212,10 @@ The typical workflow in Payload is to build out your Payload configs, install pl
 But importantly, you do not need to run migrations against your development database, because Drizzle will have already pushed your changes to your database for you.
 
 <Banner type="warning">
-  Warning: do not mix "push" and migrations with your local development database. If you use "push"
-  locally, and then try to migrate, Payload will throw a warning, telling you that these two methods
-  are not meant to be used interchangeably.
+  Warning: do not mix "push" and migrations with your local development
+  database. If you use "push" locally, and then try to migrate, Payload will
+  throw a warning, telling you that these two methods are not meant to be used
+  interchangeably.
 </Banner>
 
 **2 - create a migration**
@@ -213,7 +230,10 @@ But once you're ready, you can run `pnpm payload migrate:create`, which will per
 We won't immediately run this migration for you, however.
 
 <Banner type="success">
-  Tip: migrations created by Payload are relatively programmatic in nature, so there should not be any surprises, but before you check in the created migration it's a good idea to always double-check the contents of the migration files.
+  Tip: migrations created by Payload are relatively programmatic in nature, so
+  there should not be any surprises, but before you check in the created
+  migration it's a good idea to always double-check the contents of the
+  migration files.
 </Banner>
 
 **3 - set up your build process to run migrations**
@@ -266,13 +286,15 @@ export default buildConfig({
   // your config here
   db: postgresAdapter({
     //  your adapter config here
-    prodMigrations: migrations
-  })
+    prodMigrations: migrations,
+  }),
 })
 ```
 
 Passing your migrations as shown above will tell Payload, in production only, to execute any migrations that need to be run prior to completing the initialization of Payload. This is ideal for long-running services where Payload will only be initialized at startup.
 
 <Banner type="warning">
-  **Warning:** if Payload is instructed to run migrations in production, this may slow down serverless cold starts on platforms such as Vercel. Generally, this option should only be used for long-running servers / containers.
+  **Warning:** if Payload is instructed to run migrations in production, this
+  may slow down serverless cold starts on platforms such as Vercel. Generally,
+  this option should only be used for long-running servers / containers.
 </Banner>

docs/database/mongodb.mdx

@@ -34,11 +34,13 @@ export default buildConfig({
 | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | `autoPluralization`        | Tell Mongoose to auto-pluralize any collection names if it encounters any singular words used as collection `slug`s.                                                                                                                                                                                         |
 | `connectOptions`           | Customize MongoDB connection options. Payload will connect to your MongoDB database using default options which you can override and extend to include all the [options](https://mongoosejs.com/docs/connections.html#options) available to mongoose.                                                        |
-| `collectionsSchemaOptions` | Customize Mongoose schema options for collections.                                                                                                                                                                                                                                                                                                             |
+| `collectionsSchemaOptions` | Customize Mongoose schema options for collections.                                                                                                                                                                                                                                                           |
 | `disableIndexHints`        | Set to true to disable hinting to MongoDB to use 'id' as index. This is currently done when counting documents for pagination, as it increases the speed of the count function used in that query. Disabling this optimization might fix some problems with AWS DocumentDB. Defaults to false                |
 | `migrationDir`             | Customize the directory that migrations are stored.                                                                                                                                                                                                                                                          |
 | `transactionOptions`       | An object with configuration properties used in [transactions](https://www.mongodb.com/docs/manual/core/transactions/) or `false` which will disable the use of transactions.                                                                                                                                |
 | `collation`                | Enable language-specific string comparison with customizable options. Available on MongoDB 3.4+. Defaults locale to "en". Example: `{ strength: 3 }`. For a full list of collation options and their definitions, see the [MongoDB documentation](https://www.mongodb.com/docs/manual/reference/collation/). |
+| `allowAdditionalKeys`      | By default, Payload strips all additional keys from MongoDB data that don't exist in the Payload schema. If you have some data that you want to include to the result but it doesn't exist in Payload, you can set this to `true`. Be careful as Payload access control _won't_ work for this data.          |
+| `allowIDOnCreate`          | Set to `true` to use the `id` passed in data on the create API operations without using a custom ID field.                                                                                                                                                                                                   |
 
 ## Access to Mongoose models
 
@@ -50,3 +52,12 @@ You can access Mongoose models as follows:
 - Collection models - `payload.db.collections[myCollectionSlug]`
 - Globals model - `payload.db.globals`
 - Versions model (both collections and globals) - `payload.db.versions[myEntitySlug]`
+
+## Using other MongoDB implementations
+
+Limitations with [DocumentDB](https://aws.amazon.com/documentdb/) and [Azure Cosmos DB](https://azure.microsoft.com/en-us/products/cosmos-db):
+
+- For Azure Cosmos DB you must pass `transactionOptions: false` to the adapter options. Azure Cosmos DB does not support transactions that update two and more documents in different collections, which is a common case when using Payload (via hooks).
+- For Azure Cosmos DB the root config property `indexSortableFields` must be set to `true`.
+- The [Join Field](../fields/join) is not supported in DocumentDB and Azure Cosmos DB, as we internally use MongoDB aggregations to query data for that field, which are limited there. This can be changed in the future.
+- For DocumentDB pass `disableIndexHints: true` to disable hinting to the DB to use `id` as index which can cause problems with DocumentDB.

docs/database/overview.mdx

@@ -31,8 +31,10 @@ export default buildConfig({
 ```
 
 <Banner type="warning">
-  **Reminder:**
-  The Database Adapter is an external dependency and must be installed in your project separately from Payload. You can find the installation instructions for each Database Adapter in their respective documentation.
+  **Reminder:** The Database Adapter is an external dependency and must be
+  installed in your project separately from Payload. You can find the
+  installation instructions for each Database Adapter in their respective
+  documentation.
 </Banner>
 
 ## Selecting a Database

docs/database/postgres.mdx

@@ -44,45 +44,55 @@ export default buildConfig({
   // Optionally, can accept the same options as the @vercel/postgres package.
   db: vercelPostgresAdapter({
     pool: {
-      connectionString: process.env.DATABASE_URL
+      connectionString: process.env.DATABASE_URL,
     },
   }),
 })
 ```
 
 <Banner type="info">
-  **Note:**
-  If you're using `vercelPostgresAdapter` your `process.env.POSTGRES_URL` or `pool.connectionString` points to a local database (e.g hostname has `localhost` or `127.0.0.1`) we use the `pg` module for pooling instead of `@vercel/postgres`. This is because `@vercel/postgres` doesn't work with local databases, if you want to disable that behavior, you can pass `forceUseVercelPostgres: true` to the adapter's args and follow [Vercel guide](https://vercel.com/docs/storage/vercel-postgres/local-development#option-2:-local-postgres-instance-with-docker) for a Docker Neon DB setup.
+  **Note:** If you're using `vercelPostgresAdapter` your
+  `process.env.POSTGRES_URL` or `pool.connectionString` points to a local
+  database (e.g hostname has `localhost` or `127.0.0.1`) we use the `pg` module
+  for pooling instead of `@vercel/postgres`. This is because `@vercel/postgres`
+  doesn't work with local databases, if you want to disable that behavior, you
+  can pass `forceUseVercelPostgres: true` to the adapter's args and follow
+  [Vercel
+  guide](https://vercel.com/docs/storage/vercel-postgres/local-development#option-2:-local-postgres-instance-with-docker)
+  for a Docker Neon DB setup.
 </Banner>
 
 ## Options
 
 | Option                      | Description                                                                                                                                                                      |
 | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `pool` *                   | [Pool connection options](https://orm.drizzle.team/docs/quick-postgresql/node-postgres) that will be passed to Drizzle and `node-postgres` or to `@vercel/postgres`              |
+| `pool` \*                   | [Pool connection options](https://orm.drizzle.team/docs/quick-postgresql/node-postgres) that will be passed to Drizzle and `node-postgres` or to `@vercel/postgres`              |
 | `push`                      | Disable Drizzle's [`db push`](https://orm.drizzle.team/kit-docs/overview#prototyping-with-db-push) in development mode. By default, `push` is enabled for development mode only. |
 | `migrationDir`              | Customize the directory that migrations are stored.                                                                                                                              |
 | `schemaName` (experimental) | A string for the postgres schema to use, defaults to 'public'.                                                                                                                   |
 | `idType`                    | A string of 'serial', or 'uuid' that is used for the data type given to id columns.                                                                                              |
 | `transactionOptions`        | A PgTransactionConfig object for transactions, or set to `false` to disable using transactions. [More details](https://orm.drizzle.team/docs/transactions)                       |
 | `disableCreateDatabase`     | Pass `true` to disable auto database creation if it doesn't exist. Defaults to `false`.                                                                                          |
-| `localesSuffix`             | A string appended to the end of table names for storing localized fields. Default is '_locales'.                                                                                 |
-| `relationshipsSuffix`       | A string appended to the end of table names for storing relationships. Default is '_rels'.                                                                                       |
-| `versionsSuffix`            | A string appended to the end of table names for storing versions. Defaults to '_v'.                                                                                              |
+| `localesSuffix`             | A string appended to the end of table names for storing localized fields. Default is '\_locales'.                                                                                |
+| `relationshipsSuffix`       | A string appended to the end of table names for storing relationships. Default is '\_rels'.                                                                                      |
+| `versionsSuffix`            | A string appended to the end of table names for storing versions. Defaults to '\_v'.                                                                                             |
 | `beforeSchemaInit`          | Drizzle schema hook. Runs before the schema is built. [More Details](#beforeschemainit)                                                                                          |
 | `afterSchemaInit`           | Drizzle schema hook. Runs after the schema is built. [More Details](#afterschemainit)                                                                                            |
 | `generateSchemaOutputFile`  | Override generated schema from `payload generate:db-schema` file path. Defaults to `{CWD}/src/payload-generated.schema.ts`                                                       |
+| `allowIDOnCreate`           | Set to `true` to use the `id` passed in data on the create API operations without using a custom ID field.                                                                       |
 
 ## Access to Drizzle
 
 After Payload is initialized, this adapter will expose the full power of Drizzle to you for use if you need it.
 
 To ensure type-safety, you need to generate Drizzle schema first with:
+
 ```sh
 npx payload generate:db-schema
 ```
 
 Then, you can access Drizzle as follows:
+
 ```ts
 import { posts } from './payload-generated-schema'
 // To avoid installing Drizzle, you can import everything that drizzle has from our re-export path.
@@ -91,7 +101,12 @@ import { eq, sql, and } from '@payloadcms/db-postgres/drizzle'
 // Drizzle's Querying API: https://orm.drizzle.team/docs/rqb
 const posts = await payload.db.drizzle.query.posts.findMany()
 // Drizzle's Select API https://orm.drizzle.team/docs/select
-const result = await payload.db.drizzle.select().from(posts).where(and(eq(posts.id, 50), sql`lower(${posts.title}) = 'example post title'`))
+const result = await payload.db.drizzle
+  .select()
+  .from(posts)
+  .where(
+    and(eq(posts.id, 50), sql`lower(${posts.title}) = 'example post title'`),
+  )
 ```
 
 ## Tables, relations, and enums
@@ -126,7 +141,11 @@ Runs before the schema is built. You can use this hook to extend your database s
 
 ```ts
 import { postgresAdapter } from '@payloadcms/db-postgres'
-import { integer, pgTable, serial } from '@payloadcms/db-postgres/drizzle/pg-core'
+import {
+  integer,
+  pgTable,
+  serial,
+} from '@payloadcms/db-postgres/drizzle/pg-core'
 
 postgresAdapter({
   beforeSchemaInit: [
@@ -150,7 +169,13 @@ To quickly generate the Drizzle schema from your database you can use [Drizzle I
 You should get the `schema.ts` file which may look like this:
 
 ```ts
-import { pgTable, uniqueIndex, serial, varchar, text } from 'drizzle-orm/pg-core'
+import {
+  pgTable,
+  uniqueIndex,
+  serial,
+  varchar,
+  text,
+} from 'drizzle-orm/pg-core'
 
 export const users = pgTable('users', {
   id: serial('id').primaryKey(),
@@ -170,7 +195,6 @@ export const countries = pgTable(
     }
   },
 )
-
 ```
 
 You can import them into your config and append to the schema with the `beforeSchemaInit` hook like this:
@@ -187,7 +211,7 @@ postgresAdapter({
         tables: {
           ...schema.tables,
           users,
-          countries
+          countries,
         },
       }
     },
@@ -197,7 +221,6 @@ postgresAdapter({
 
 Make sure Payload doesn't overlap table names with its collections. For example, if you already have a collection with slug "users", you should either change the slug or `dbName` to change the table name for this collection.
 
-
 ### afterSchemaInit
 
 Runs after the Drizzle schema is built. You can use this hook to modify the schema with features that aren't supported by Payload, or if you want to add a column that you don't want to be in the Payload config.
@@ -234,10 +257,9 @@ export default buildConfig({
             extraIntegerColumn: integer('extra_integer_column'),
           },
           extraConfig: (table) => ({
-            country_city_composite_index: index('country_city_composite_index').on(
-              table.country,
-              table.city,
-            ),
+            country_city_composite_index: index(
+              'country_city_composite_index',
+            ).on(table.country, table.city),
           }),
         })
 
@@ -246,10 +268,10 @@ export default buildConfig({
     ],
   }),
 })
-
 ```
 
 ### Note for generated schema:
+
 Columns and tables, added in schema hooks won't be added to the generated via `payload generate:db-schema` Drizzle schema.
 If you want them to be there, you either have to edit this file manually or mutate the internal Payload "raw" SQL schema in the `beforeSchemaInit`:
 
@@ -266,9 +288,9 @@ postgresAdapter({
           my_id: {
             name: 'my_id',
             type: 'serial',
-            primaryKey: true
-          }
-        }
+            primaryKey: true,
+          },
+        },
       }
 
       // Add a new column to generated by Payload table:
@@ -276,13 +298,13 @@ postgresAdapter({
         name: 'custom_column',
         // Note that Payload SQL doesn't support everything that Drizzle does.
         type: 'integer',
-        notNull: true
+        notNull: true,
       }
       // Add a new index to generated by Payload table:
       adapter.rawTables.posts.indexes.customColumnIdx = {
         name: 'custom_column_idx',
         unique: true,
-        on: ['custom_column']
+        on: ['custom_column'],
       }
 
       return schema

docs/database/sqlite.mdx

@@ -27,7 +27,7 @@ export default buildConfig({
     client: {
       url: process.env.DATABASE_URL,
       authToken: process.env.DATABASE_AUTH_TOKEN,
-    }
+    },
   }),
 })
 ```
@@ -36,30 +36,33 @@ export default buildConfig({
 
 | Option                     | Description                                                                                                                                                                      |
 | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `client` *                | [Client connection options](https://orm.drizzle.team/docs/get-started-sqlite#turso) that will be passed to `createClient` from `@libsql/client`.                                 |
+| `client` \*                | [Client connection options](https://orm.drizzle.team/docs/get-started-sqlite#turso) that will be passed to `createClient` from `@libsql/client`.                                 |
 | `push`                     | Disable Drizzle's [`db push`](https://orm.drizzle.team/kit-docs/overview#prototyping-with-db-push) in development mode. By default, `push` is enabled for development mode only. |
 | `migrationDir`             | Customize the directory that migrations are stored.                                                                                                                              |
 | `logger`                   | The instance of the logger to be passed to drizzle. By default Payload's will be used.                                                                                           |
 | `idType`                   | A string of 'number', or 'uuid' that is used for the data type given to id columns.                                                                                              |
 | `transactionOptions`       | A SQLiteTransactionConfig object for transactions, or set to `false` to disable using transactions. [More details](https://orm.drizzle.team/docs/transactions)                   |
-| `localesSuffix`            | A string appended to the end of table names for storing localized fields. Default is '_locales'.                                                                                 |
-| `relationshipsSuffix`      | A string appended to the end of table names for storing relationships. Default is '_rels'.                                                                                       |
-| `versionsSuffix`           | A string appended to the end of table names for storing versions. Defaults to '_v'.                                                                                              |
+| `localesSuffix`            | A string appended to the end of table names for storing localized fields. Default is '\_locales'.                                                                                |
+| `relationshipsSuffix`      | A string appended to the end of table names for storing relationships. Default is '\_rels'.                                                                                      |
+| `versionsSuffix`           | A string appended to the end of table names for storing versions. Defaults to '\_v'.                                                                                             |
 | `beforeSchemaInit`         | Drizzle schema hook. Runs before the schema is built. [More Details](#beforeschemainit)                                                                                          |
 | `afterSchemaInit`          | Drizzle schema hook. Runs after the schema is built. [More Details](#afterschemainit)                                                                                            |
 | `generateSchemaOutputFile` | Override generated schema from `payload generate:db-schema` file path. Defaults to `{CWD}/src/payload-generated.schema.ts`                                                       |
 | `autoIncrement`            | Pass `true` to enable SQLite [AUTOINCREMENT](https://www.sqlite.org/autoinc.html) for primary keys to ensure the same ID cannot be reused from deleted rows                      |
+| `allowIDOnCreate`          | Set to `true` to use the `id` passed in data on the create API operations without using a custom ID field.                                                                       |
 
 ## Access to Drizzle
 
 After Payload is initialized, this adapter will expose the full power of Drizzle to you for use if you need it.
 
 To ensure type-safety, you need to generate Drizzle schema first with:
+
 ```sh
 npx payload generate:db-schema
 ```
 
 Then, you can access Drizzle as follows:
+
 ```ts
 // Import table from the generated file
 import { posts } from './payload-generated-schema'
@@ -69,7 +72,12 @@ import { eq, sql, and } from '@payloadcms/db-sqlite/drizzle'
 // Drizzle's Querying API: https://orm.drizzle.team/docs/rqb
 const posts = await payload.db.drizzle.query.posts.findMany()
 // Drizzle's Select API https://orm.drizzle.team/docs/select
-const result = await payload.db.drizzle.select().from(posts).where(and(eq(posts.id, 50), sql`lower(${posts.title}) = 'example post title'`))
+const result = await payload.db.drizzle
+  .select()
+  .from(posts)
+  .where(
+    and(eq(posts.id, 50), sql`lower(${posts.title}) = 'example post title'`),
+  )
 ```
 
 ## Tables and relations
@@ -127,12 +135,17 @@ To quickly generate the Drizzle schema from your database you can use [Drizzle I
 You should get the `schema.ts` file which may look like this:
 
 ```ts
-import { sqliteTable, text, uniqueIndex, integer } from 'drizzle-orm/sqlite-core'
+import {
+  sqliteTable,
+  text,
+  uniqueIndex,
+  integer,
+} from 'drizzle-orm/sqlite-core'
 
 export const users = sqliteTable('users', {
   id: integer('id').primaryKey({ autoIncrement: true }),
   fullName: text('full_name'),
-  phone: text('phone', {length: 256}),
+  phone: text('phone', { length: 256 }),
 })
 
 export const countries = sqliteTable(
@@ -147,7 +160,6 @@ export const countries = sqliteTable(
     }
   },
 )
-
 ```
 
 You can import them into your config and append to the schema with the `beforeSchemaInit` hook like this:
@@ -164,7 +176,7 @@ sqliteAdapter({
         tables: {
           ...schema.tables,
           users,
-          countries
+          countries,
         },
       }
     },
@@ -174,7 +186,6 @@ sqliteAdapter({
 
 Make sure Payload doesn't overlap table names with its collections. For example, if you already have a collection with slug "users", you should either change the slug or `dbName` to change the table name for this collection.
 
-
 ### afterSchemaInit
 
 Runs after the Drizzle schema is built. You can use this hook to modify the schema with features that aren't supported by Payload, or if you want to add a column that you don't want to be in the Payload config.
@@ -211,10 +222,9 @@ export default buildConfig({
             extraIntegerColumn: integer('extra_integer_column'),
           },
           extraConfig: (table) => ({
-            country_city_composite_index: index('country_city_composite_index').on(
-              table.country,
-              table.city,
-            ),
+            country_city_composite_index: index(
+              'country_city_composite_index',
+            ).on(table.country, table.city),
           }),
         })
 
@@ -223,10 +233,10 @@ export default buildConfig({
     ],
   }),
 })
-
 ```
 
 ### Note for generated schema:
+
 Columns and tables, added in schema hooks won't be added to the generated via `payload generate:db-schema` Drizzle schema.
 If you want them to be there, you either have to edit this file manually or mutate the internal Payload "raw" SQL schema in the `beforeSchemaInit`:
 
@@ -237,15 +247,15 @@ sqliteAdapter({
   beforeSchemaInit: [
     ({ schema, adapter }) => {
       // Add a new table
-       adapter.rawTables.myTable = {
+      adapter.rawTables.myTable = {
         name: 'my_table',
         columns: {
           my_id: {
             name: 'my_id',
             type: 'integer',
-            primaryKey: true
-          }
-        }
+            primaryKey: true,
+          },
+        },
       }
 
       // Add a new column to generated by Payload table:
@@ -253,13 +263,13 @@ sqliteAdapter({
         name: 'custom_column',
         // Note that Payload SQL doesn't support everything that Drizzle does.
         type: 'integer',
-        notNull: true
+        notNull: true,
       }
       // Add a new index to generated by Payload table:
       adapter.rawTables.posts.indexes.customColumnIdx = {
         name: 'custom_column_idx',
         unique: true,
-        on: ['custom_column']
+        on: ['custom_column'],
       }
 
       return schema

docs/database/transactions.mdx

@@ -13,13 +13,15 @@ By default, Payload will use transactions for all data changing operations, as l
 <Banner type="info">
   **Note:**
 
-  MongoDB requires a connection to a replicaset in order to make use of transactions.
+MongoDB requires a connection to a replicaset in order to make use of transactions.
+
 </Banner>
 
 <Banner type="info">
   **Note:**
 
-  Transactions in SQLite are disabled by default. You need to pass `transactionOptions: {}` to enable them.
+Transactions in SQLite are disabled by default. You need to pass `transactionOptions: {}` to enable them.
+
 </Banner>
 
 The initial request made to Payload will begin a new transaction and attach it to the `req.transactionID`. If you have a `hook` that interacts with the database, you can opt in to using the same transaction by passing the `req` in the arguments. For example:
@@ -67,7 +69,7 @@ const afterChange: CollectionAfterChangeHook = async ({ req }) => {
 
 ## Direct Transaction Access
 
-When writing your own scripts or custom endpoints, you may wish to have direct control over transactions. This is useful for interacting with your database outside of Payload's local API.
+When writing your own scripts or custom endpoints, you may wish to have direct control over transactions. This is useful for interacting with your database outside of Payload's Local API.
 
 The following functions can be used for managing transactions:
 
@@ -75,7 +77,7 @@ The following functions can be used for managing transactions:
 - `payload.db.commitTransaction` - Takes the identifier for the transaction, finalizes any changes.
 - `payload.db.rollbackTransaction` - Takes the identifier for the transaction, discards any changes.
 
-Payload uses the `req` object to pass the transaction ID through to the database adapter. If you are not using the `req` object, you can make a new object to pass the transaction ID directly to database adapter methods and local API calls.
+Payload uses the `req` object to pass the transaction ID through to the database adapter. If you are not using the `req` object, you can make a new object to pass the transaction ID directly to database adapter methods and Local API calls.
 Example:
 
 ```ts
@@ -89,14 +91,14 @@ const standalonePayloadScript = async () => {
   const transactionID = await payload.db.beginTransaction()
 
   try {
-    // Make an update using the local API
+    // Make an update using the Local API
     await payload.update({
       collection: 'posts',
       data: {
         some: 'data',
       },
       where: {
-        slug: { equals: 'my-slug' }
+        slug: { equals: 'my-slug' },
       },
       req: { transactionID },
     })
@@ -121,7 +123,7 @@ standalonePayloadScript()
 
 If you wish to disable transactions entirely, you can do so by passing `false` as the `transactionOptions` in your database adapter configuration. All the official Payload database adapters support this option.
 
-In addition to allowing database transactions to be disabled at the adapter level. You can prevent Payload from using a transaction in direct calls to the local API by adding `disableTransaction: true` to the args. For example:
+In addition to allowing database transactions to be disabled at the adapter level. You can prevent Payload from using a transaction in direct calls to the Local API by adding `disableTransaction: true` to the args. For example:
 
 ```ts
 await payload.update({
@@ -130,7 +132,7 @@ await payload.update({
     some: 'data',
   },
   where: {
-    slug: { equals: 'my-slug' }
+    slug: { equals: 'my-slug' },
   },
   disableTransaction: true,
 })

docs/email/overview.mdx

@@ -16,7 +16,7 @@ The email adapter should be passed into the `email` property of the Payload Conf
 
 ### Default Configuration
 
-When email is not needed or desired, Payload will log a warning on startup notifying that email is not configured. A  warning message will also be logged on any attempt to send an email.
+When email is not needed or desired, Payload will log a warning on startup notifying that email is not configured. A warning message will also be logged on any attempt to send an email.
 
 ### Email Adapter
 
@@ -24,9 +24,8 @@ An email adapter will require at least the following fields:
 
 | Option                      | Description                                                                      |
 | --------------------------- | -------------------------------------------------------------------------------- |
-| **`defaultFromName`** *    | The name part of the From field that will be seen on the delivered email         |
-| **`defaultFromAddress`** * | The email address part of the From field that will be used when delivering email |
-
+| **`defaultFromName`** \*    | The name part of the From field that will be seen on the delivered email         |
+| **`defaultFromAddress`** \* | The email address part of the From field that will be used when delivering email |
 
 ### Official Email Adapters
 
@@ -97,13 +96,11 @@ export default buildConfig({
 
 You also have the ability to bring your own nodemailer transport. This is an example of using the SendGrid nodemailer transport.
 
-
 ```ts
 import { buildConfig } from 'payload'
 import { nodemailerAdapter } from '@payloadcms/email-nodemailer'
 import nodemailerSendgrid from 'nodemailer-sendgrid'
 
-
 export default buildConfig({
   email: nodemailerAdapter({
     defaultFromAddress: 'info@payloadcms.com',

docs/fields/array.mdx

@@ -41,9 +41,9 @@ export const MyArrayField: Field = {
 
 | Option                 | Description                                                                                                                                                                                                                                                                        |
 | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                                                                                                                             |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                                                                                                                             |
 | **`label`**            | Text used as the heading in the [Admin Panel](../admin/overview) or an object with keys for each language. Auto-generated from name if not defined.                                                                                                                                |
-| **`fields`** *        | Array of field types to correspond to each row of the Array.                                                                                                                                                                                                                       |
+| **`fields`** \*        | Array of field types to correspond to each row of the Array.                                                                                                                                                                                                                       |
 | **`validate`**         | Provide a custom validation function that will be executed on both the [Admin Panel](../admin/overview) and the backend. [More](/docs/fields/overview#validation)                                                                                                                  |
 | **`minRows`**          | A number for the fewest allowed items during validation when a value is present.                                                                                                                                                                                                   |
 | **`maxRows`**          | A number for the most allowed items during validation when a value is present.                                                                                                                                                                                                     |
@@ -62,7 +62,7 @@ export const MyArrayField: Field = {
 | **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                                                                                                                        |
 | **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)                                                                                                                   |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Admin Options
 
@@ -73,7 +73,8 @@ import type { Field } from 'payload'
 
 export const MyArrayField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -81,11 +82,11 @@ export const MyArrayField: Field = {
 
 The Array Field inherits all of the default options from the base [Field Admin Config](./overview#admin-options), plus the following additional options:
 
-| Option                    | Description                                                                                                                                     |
-| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`initCollapsed`**       | Set the initial collapsed state                                                                                                                 |
-| **`components.RowLabel`** | React component to be rendered as the label on the array row. [Example](#row-label)                                                             |
-| **`isSortable`**          | Disable order sorting by setting this value to `false`                                                                                          |
+| Option                    | Description                                                                         |
+| ------------------------- | ----------------------------------------------------------------------------------- |
+| **`initCollapsed`**       | Set the initial collapsed state                                                     |
+| **`components.RowLabel`** | React component to be rendered as the label on the array row. [Example](#row-label) |
+| **`isSortable`**          | Disable order sorting by setting this value to `false`                              |
 
 ## Example
 
@@ -145,7 +146,7 @@ export const CustomArrayFieldServer: ArrayFieldServerComponent = ({
   clientField,
   path,
   schemaPath,
-  permissions
+  permissions,
 }) => {
   return (
     <ArrayField
@@ -205,7 +206,7 @@ import React from 'react'
 
 export const CustomArrayFieldLabelClient: ArrayFieldLabelClientComponent = ({
   field,
-  path
+  path,
 }) => {
   return (
     <FieldLabel

docs/fields/blocks.mdx

@@ -41,9 +41,9 @@ export const MyBlocksField: Field = {
 
 | Option                 | Description                                                                                                                                                                                                                                                                        |
 | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                                                                                                                             |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                                                                                                                             |
 | **`label`**            | Text used as the heading in the Admin Panel or an object with keys for each language. Auto-generated from name if not defined.                                                                                                                                                     |
-| **`blocks`** *        | Array of [block configs](/docs/fields/blocks#block-configs) to be made available to this field.                                                                                                                                                                                    |
+| **`blocks`** \*        | Array of [block configs](/docs/fields/blocks#block-configs) to be made available to this field.                                                                                                                                                                                    |
 | **`validate`**         | Provide a custom validation function that will be executed on both the Admin Panel and the backend. [More](/docs/fields/overview#validation)                                                                                                                                       |
 | **`minRows`**          | A number for the fewest allowed items during validation when a value is present.                                                                                                                                                                                                   |
 | **`maxRows`**          | A number for the most allowed items during validation when a value is present.                                                                                                                                                                                                     |
@@ -60,7 +60,7 @@ export const MyBlocksField: Field = {
 | **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                                                                                                                        |
 | **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)                                                                                                                   |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Admin Options
 
@@ -71,7 +71,8 @@ import type { Field } from 'payload'
 
 export const MyBlocksField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -79,10 +80,12 @@ export const MyBlocksField: Field = {
 
 The Blocks Field inherits all of the default options from the base [Field Admin Config](./overview#admin-options), plus the following additional options:
 
-| Option              | Description                        |
-| ------------------- | ---------------------------------- |
-| **`initCollapsed`**    | Set the initial collapsed state |
-| **`isSortable`**       | Disable order sorting by setting this value to `false` |
+| Option                 | Description                                                                |
+| ---------------------- | -------------------------------------------------------------------------- |
+| **`group`**            | Text or localization object used to group this Block in the Blocks Drawer. |
+| **`initCollapsed`**    | Set the initial collapsed state                                            |
+| **`isSortable`**       | Disable order sorting by setting this value to `false`                     |
+| **`disableBlockName`** | Hide the blockName field by setting this value to `true`                   |
 
 #### Customizing the way your block is rendered in Lexical
 
@@ -96,8 +99,9 @@ This is super handy if you'd like to present your editors with a very deliberate
 For example, if you have a `gallery` block, you might want to actually render the gallery of images directly in your Lexical block. With the `admin.components.Block` property, you can do exactly that!
 
 <Banner type="success">
-  **Tip:**
-  If you customize the way your block is rendered in Lexical, you can import utility components to easily edit / remove your block - so that you don't have to build all of this yourself.
+  **Tip:** If you customize the way your block is rendered in Lexical, you can
+  import utility components to easily edit / remove your block - so that you
+  don't have to build all of this yourself.
 </Banner>
 
 To import these utility components for one of your custom blocks, you can import the following:
@@ -125,7 +129,6 @@ import {
   // The default "collapsible" UI that is rendered for a regular block
   // if you want to re-use it
   BlockCollapsible,
-
 } from '@payloadcms/richtext-lexical/client'
 ```
 
@@ -134,18 +137,18 @@ import {
 Blocks are defined as separate configs of their own.
 
 <Banner type="success">
-  **Tip:**
-  Best practice is to define each block config in its own file, and then import them into your
-  Blocks field as necessary. This way each block config can be easily shared between fields. For
-  instance, using the "layout builder" example, you might want to feature a few of the same blocks
-  in a Post collection as well as a Page collection. Abstracting into their own files trivializes
-  their reusability.
+  **Tip:** Best practice is to define each block config in its own file, and
+  then import them into your Blocks field as necessary. This way each block
+  config can be easily shared between fields. For instance, using the "layout
+  builder" example, you might want to feature a few of the same blocks in a Post
+  collection as well as a Page collection. Abstracting into their own files
+  trivializes their reusability.
 </Banner>
 
 | Option                     | Description                                                                                                                                                                         |
 | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`slug`** *               | Identifier for this block type. Will be saved on each block as the `blockType` property.                                                                                            |
-| **`fields`** *             | Array of fields to be stored in this block.                                                                                                                                         |
+| **`slug`** \*              | Identifier for this block type. Will be saved on each block as the `blockType` property.                                                                                            |
+| **`fields`** \*            | Array of fields to be stored in this block.                                                                                                                                         |
 | **`labels`**               | Customize the block labels that appear in the Admin dashboard. Auto-generated from slug if not defined.                                                                             |
 | **`imageURL`**             | Provide a custom image thumbnail to help editors identify this block in the Admin UI.                                                                                               |
 | **`imageAltText`**         | Customize this block's image thumbnail alt text.                                                                                                                                    |
@@ -164,7 +167,7 @@ The `blockType` is saved as the slug of the block that has been selected.
 
 **`blockName`**
 
-The Admin Panel provides each block with a `blockName` field which optionally allows editors to label their blocks for better editability and readability.
+The Admin Panel provides each block with a `blockName` field which optionally allows editors to label their blocks for better editability and readability. This can be visually hidden via `admin.disableBlockName`.
 
 ## Example
 
@@ -224,10 +227,11 @@ export const CustomBlocksFieldServer: BlocksFieldServerComponent = ({
   clientField,
   path,
   schemaPath,
-  permissions
+  permissions,
 }) => {
   return (
-    <BlocksField field={clientField}
+    <BlocksField
+      field={clientField}
       path={path}
       schemaPath={schemaPath}
       permissions={permissions}
@@ -295,6 +299,22 @@ export const CustomBlocksFieldLabelClient: BlocksFieldLabelClientComponent = ({
 }
 ```
 
+### Row Label
+
+```tsx
+'use client'
+
+import { useRowLabel } from '@payloadcms/ui'
+
+export const BlockRowLabel = () => {
+  const { data, rowNumber } = useRowLabel<{ title?: string }>()
+
+  const customLabel = `${data.type} ${String(rowNumber).padStart(2, '0')} `
+
+  return <div>Custom Label: {customLabel}</div>
+}
+```
+
 ## Block References
 
 If you have multiple blocks used in multiple places, your Payload Config can grow in size, potentially sending more data to the client and requiring more processing on the server. However, you can optimize performance by defining each block **once** in your Payload Config and then referencing its slug wherever it's used instead of passing the entire block config.
@@ -355,9 +375,9 @@ const config = buildConfig({
   **Reminder:**
   Blocks referenced in the `blockReferences` array are treated as isolated from the collection / global config. This has the following implications:
 
-  1. The block config cannot be modified or extended in the collection config. It will be identical everywhere it's referenced.
-  2. Access control for blocks referenced in the `blockReferences` are run only once - data from the collection will not be available in the block's access control.
-</Banner>
+1. The block config cannot be modified or extended in the collection config. It will be identical everywhere it's referenced.
+2. Access control for blocks referenced in the `blockReferences` are run only once - data from the collection will not be available in the block's access control.
+   </Banner>
 
 ## TypeScript
 

docs/fields/checkbox.mdx

@@ -30,7 +30,7 @@ export const MyCheckboxField: Field = {
 
 | Option                 | Description                                                                                                                                                                 |
 | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
 | **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                     |
 | **`validate`**         | Provide a custom validation function that will be executed on both the Admin Panel and the backend. [More](/docs/fields/overview#validation)                                |
 | **`index`**            | Build an [index](/docs/database/overview) for this field to produce faster queries. Set this field to `true` if your users will perform queries on this field's data often. |
@@ -41,12 +41,12 @@ export const MyCheckboxField: Field = {
 | **`defaultValue`**     | Provide data to be used for this field's default value, will default to false if field is also `required`. [More](/docs/fields/overview#default-values)                     |
 | **`localized`**        | Enable localization for this field. Requires [localization to be enabled](/docs/configuration/localization) in the Base config.                                             |
 | **`required`**         | Require this field to have a value.                                                                                                                                         |
-| **`admin`**            | Admin-specific configuration. [More details](./overview#admin-options).                                                                                                |
+| **`admin`**            | Admin-specific configuration. [More details](./overview#admin-options).                                                                                                     |
 | **`custom`**           | Extension point for adding custom data (e.g. for plugins)                                                                                                                   |
 | **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                 |
 | **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)            |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Example
 
@@ -104,7 +104,9 @@ import React from 'react'
 import { CheckboxField } from '@payloadcms/ui'
 import type { CheckboxFieldClientComponent } from 'payload'
 
-export const CustomCheckboxFieldClient: CheckboxFieldClientComponent = (props) => {
+export const CustomCheckboxFieldClient: CheckboxFieldClientComponent = (
+  props,
+) => {
   return <CheckboxField {...props} />
 }
 ```
@@ -118,18 +120,16 @@ import React from 'react'
 import { FieldLabel } from '@payloadcms/ui'
 import type { CheckboxFieldLabelServerComponent } from 'payload'
 
-export const CustomCheckboxFieldLabelServer: CheckboxFieldLabelServerComponent = ({
-  clientField,
-  path,
-}) => {
-  return (
-    <FieldLabel
-      label={clientField?.label || clientField?.name}
-      path={path}
-      required={clientField?.required}
-    />
-  )
-}
+export const CustomCheckboxFieldLabelServer: CheckboxFieldLabelServerComponent =
+  ({ clientField, path }) => {
+    return (
+      <FieldLabel
+        label={clientField?.label || clientField?.name}
+        path={path}
+        required={clientField?.required}
+      />
+    )
+  }
 ```
 
 #### Client Component
@@ -140,17 +140,14 @@ import React from 'react'
 import { FieldLabel } from '@payloadcms/ui'
 import type { CheckboxFieldLabelClientComponent } from 'payload'
 
-export const CustomCheckboxFieldLabelClient: CheckboxFieldLabelClientComponent = ({
-  label,
-  path,
-  required,
-}) => {
-  return (
-  <FieldLabel
-    label={field?.label || field?.name}
-    path={path}
-    required={field?.required}
-  />
-)
-}
+export const CustomCheckboxFieldLabelClient: CheckboxFieldLabelClientComponent =
+  ({ label, path, required }) => {
+    return (
+      <FieldLabel
+        label={field?.label || field?.name}
+        path={path}
+        required={field?.required}
+      />
+    )
+  }
 ```

docs/fields/code.mdx

@@ -31,7 +31,7 @@ export const MyBlocksField: Field = {
 
 | Option                 | Description                                                                                                                                                                 |
 | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
 | **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                     |
 | **`unique`**           | Enforce that each entry in the Collection has a unique value for this field.                                                                                                |
 | **`index`**            | Build an [index](/docs/database/overview) for this field to produce faster queries. Set this field to `true` if your users will perform queries on this field's data often. |
@@ -50,7 +50,7 @@ export const MyBlocksField: Field = {
 | **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                 |
 | **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)            |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Admin Options
 
@@ -61,7 +61,8 @@ import type { Field } from 'payload'
 
 export const MyCodeField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -114,7 +115,12 @@ export const CustomCodeFieldServer: CodeFieldServerComponent = ({
   permissions,
 }) => {
   return (
-    <CodeField field={clientField} path={path} schemaPath={schemaPath} permissions={permissions} />
+    <CodeField
+      field={clientField}
+      path={path}
+      schemaPath={schemaPath}
+      permissions={permissions}
+    />
   )
 }
 ```
@@ -176,4 +182,3 @@ export const CustomCodeFieldLabelClient: CodeFieldLabelClientComponent = ({
   )
 }
 ```
-

docs/fields/collapsible.mdx

@@ -35,12 +35,12 @@ export const MyCollapsibleField: Field = {
 
 | Option          | Description                                                                                                                                                                  |
 | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`label`** *  | A label to render within the header of the collapsible component. This can be a string, function or react component. Function/components receive `({ data, path })` as args. |
-| **`fields`** * | Array of field types to nest within this Collapsible.                                                                                                                        |
-| **`admin`**     | Admin-specific configuration. [More details](#admin-options).                                                                                                    |
+| **`label`** \*  | A label to render within the header of the collapsible component. This can be a string, function or react component. Function/components receive `({ data, path })` as args. |
+| **`fields`** \* | Array of field types to nest within this Collapsible.                                                                                                                        |
+| **`admin`**     | Admin-specific configuration. [More details](#admin-options).                                                                                                                |
 | **`custom`**    | Extension point for adding custom data (e.g. for plugins)                                                                                                                    |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Admin Options
 
@@ -51,7 +51,8 @@ import type { Field } from 'payload'
 
 export const MyCollapsibleField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }

docs/fields/date.mdx

@@ -30,7 +30,7 @@ export const MyDateField: Field = {
 
 | Option                 | Description                                                                                                                                                                 |
 | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
 | **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                     |
 | **`index`**            | Build an [index](/docs/database/overview) for this field to produce faster queries. Set this field to `true` if your users will perform queries on this field's data often. |
 | **`validate`**         | Provide a custom validation function that will be executed on both the Admin Panel and the backend. [More](/docs/fields/overview#validation)                                |
@@ -43,11 +43,11 @@ export const MyDateField: Field = {
 | **`required`**         | Require this field to have a value.                                                                                                                                         |
 | **`admin`**            | Admin-specific configuration. [More details](#admin-options).                                                                                                               |
 | **`custom`**           | Extension point for adding custom data (e.g. for plugins)                                                                                                                   |
-| **`timezone`** *           | Set to `true` to enable timezone selection on this field. [More details](#timezones).                                                                                                                                                                |
+| **`timezone`** \*      | Set to `true` to enable timezone selection on this field. [More details](#timezones).                                                                                       |
 | **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                 |
 | **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)            |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Admin Options
 
@@ -58,7 +58,8 @@ import type { Field } from 'payload'
 
 export const MyDateField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -71,17 +72,17 @@ The Date Field inherits all of the default options from the base [Field Admin Co
 | **`placeholder`**              | Placeholder text for the field.                                                                                                        |
 | **`date`**                     | Pass options to customize date field appearance.                                                                                       |
 | **`date.displayFormat`**       | Format date to be shown in field **cell**.                                                                                             |
-| **`date.pickerAppearance`** * | Determines the appearance of the datepicker: `dayAndTime` `timeOnly` `dayOnly` `monthOnly`.                                            |
-| **`date.monthsToShow`** *     | Number of months to display max is 2. Defaults to 1.                                                                                   |
-| **`date.minDate`** *          | Min date value to allow.                                                                                                               |
-| **`date.maxDate`** *          | Max date value to allow.                                                                                                               |
-| **`date.minTime`** *          | Min time value to allow.                                                                                                               |
-| **`date.maxTime`** *          | Max date value to allow.                                                                                                               |
-| **`date.overrides`** *        | Pass any valid props directly to the [react-datepicker](https://github.com/Hacker0x01/react-datepicker/blob/master/docs/datepicker.md) |
-| **`date.timeIntervals`** *    | Time intervals to display. Defaults to 30 minutes.                                                                                     |
-| **`date.timeFormat`** *       | Determines time format. Defaults to `'h:mm aa'`.                                                                                       |
+| **`date.pickerAppearance`** \* | Determines the appearance of the datepicker: `dayAndTime` `timeOnly` `dayOnly` `monthOnly`.                                            |
+| **`date.monthsToShow`** \*     | Number of months to display max is 2. Defaults to 1.                                                                                   |
+| **`date.minDate`** \*          | Min date value to allow.                                                                                                               |
+| **`date.maxDate`** \*          | Max date value to allow.                                                                                                               |
+| **`date.minTime`** \*          | Min time value to allow.                                                                                                               |
+| **`date.maxTime`** \*          | Max date value to allow.                                                                                                               |
+| **`date.overrides`** \*        | Pass any valid props directly to the [react-datepicker](https://github.com/Hacker0x01/react-datepicker/blob/master/docs/datepicker.md) |
+| **`date.timeIntervals`** \*    | Time intervals to display. Defaults to 30 minutes.                                                                                     |
+| **`date.timeFormat`** \*       | Determines time format. Defaults to `'h:mm aa'`.                                                                                       |
 
-_* This property is passed directly to [react-datepicker](https://github.com/Hacker0x01/react-datepicker/blob/master/docs/datepicker.md)._
+_\* This property is passed directly to [react-datepicker](https://github.com/Hacker0x01/react-datepicker/blob/master/docs/datepicker.md)._
 
 ### Display Format and Picker Appearance
 
@@ -243,5 +244,6 @@ You can customise the available list of timezones in the [global admin config](.
   **Good to know:**
   The date itself will be stored in UTC so it's up to you to handle the conversion to the user's timezone when displaying the date in your frontend.
 
-  Dates without a specific time are normalised to 12:00 in the selected timezone.
+Dates without a specific time are normalised to 12:00 in the selected timezone.
+
 </Banner>

docs/fields/email.mdx

@@ -30,7 +30,7 @@ export const MyEmailField: Field = {
 
 | Option                 | Description                                                                                                                                                                 |
 | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
 | **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                     |
 | **`unique`**           | Enforce that each entry in the Collection has a unique value for this field.                                                                                                |
 | **`index`**            | Build an [index](/docs/database/overview) for this field to produce faster queries. Set this field to `true` if your users will perform queries on this field's data often. |
@@ -47,7 +47,7 @@ export const MyEmailField: Field = {
 | **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                 |
 | **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)            |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Admin Options
 
@@ -58,7 +58,8 @@ import type { Field } from 'payload'
 
 export const MyEmailField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -66,10 +67,10 @@ export const MyEmailField: Field = {
 
 The Email Field inherits all of the default options from the base [Field Admin Config](./overview#admin-options), plus the following additional options:
 
-| Property                       | Description                                                                                                                            |
-| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
-| **`placeholder`**              | Set this property to define a placeholder string for the field.                                                                         |
-| **`autoComplete`**             | Set this property to a string that will be used for browser autocomplete.                                                               |
+| Property           | Description                                                               |
+| ------------------ | ------------------------------------------------------------------------- |
+| **`placeholder`**  | Set this property to define a placeholder string for the field.           |
+| **`autoComplete`** | Set this property to a string that will be used for browser autocomplete. |
 
 ## Example
 
@@ -109,7 +110,12 @@ export const CustomEmailFieldServer: EmailFieldServerComponent = ({
   permissions,
 }) => {
   return (
-    <EmailField field={clientField} path={path} schemaPath={schemaPath} permissions={permissions} />
+    <EmailField
+      field={clientField}
+      path={path}
+      schemaPath={schemaPath}
+      permissions={permissions}
+    />
   )
 }
 ```
@@ -168,5 +174,6 @@ export const CustomEmailFieldLabelClient: EmailFieldLabelClientComponent = ({
       path={path}
       required={field?.required}
     />
-  )}
+  )
+}
 ```

docs/fields/group.mdx

@@ -35,8 +35,8 @@ export const MyGroupField: Field = {
 
 | Option                 | Description                                                                                                                                                                                                                                                                        |
 | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                                                                                                                             |
-| **`fields`** *        | Array of field types to nest within this Group.                                                                                                                                                                                                                                    |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                                                                                                                             |
+| **`fields`** \*        | Array of field types to nest within this Group.                                                                                                                                                                                                                                    |
 | **`label`**            | Used as a heading in the Admin Panel and to name the generated GraphQL type.                                                                                                                                                                                                       |
 | **`validate`**         | Provide a custom validation function that will be executed on both the Admin Panel and the backend. [More](/docs/fields/overview#validation)                                                                                                                                       |
 | **`saveToJWT`**        | If this field is top-level and nested in a config supporting [Authentication](/docs/authentication/overview), include its data in the user JWT.                                                                                                                                    |
@@ -51,7 +51,7 @@ export const MyGroupField: Field = {
 | **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                                                                                                                        |
 | **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)                                                                                                                   |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Admin Options
 
@@ -62,7 +62,8 @@ import type { Field } from 'payload'
 
 export const MyGroupField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -70,9 +71,9 @@ export const MyGroupField: Field = {
 
 The Group Field inherits all of the default options from the base [Field Admin Config](./overview#admin-options), plus the following additional options:
 
-| Option              | Description                                                                                                                                                                                                                   |
-| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`hideGutter`**    | Set this property to `true` to hide this field's gutter within the Admin Panel. The field gutter is rendered as a vertical line and padding, but often if this field is nested within a Group, Block, or Array, you may want to hide the gutter. |
+| Option           | Description                                                                                                                                                                                                                                      |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| **`hideGutter`** | Set this property to `true` to hide this field's gutter within the Admin Panel. The field gutter is rendered as a vertical line and padding, but often if this field is nested within a Group, Block, or Array, you may want to hide the gutter. |
 
 ## Example
 

docs/fields/join.mdx

@@ -21,10 +21,10 @@ The Join field is useful in scenarios including:
 - Displaying where a document or upload is used in other documents
 
 <LightDarkImage
-srcLight="https://payloadcms.com/images/docs/fields/join.png"
-srcDark="https://payloadcms.com/images/docs/fields/join-dark.png"
-alt="Shows Join field in the Payload Admin Panel"
-caption="Admin Panel screenshot of Join field"
+  srcLight="https://payloadcms.com/images/docs/fields/join.png"
+  srcDark="https://payloadcms.com/images/docs/fields/join-dark.png"
+  alt="Shows Join field in the Payload Admin Panel"
+  caption="Admin Panel screenshot of Join field"
 />
 
 For the Join field to work, you must have an existing [relationship](./relationship) or [upload](./upload) field in the
@@ -59,7 +59,18 @@ are related to the Category are populated for you. This is extremely powerful an
 of relationship types in an easy manner.
 
 <Banner type="success">
-  The Join field is extremely performant and does not add additional query overhead to your API responses until you add depth of 1 or above. It works in all database adapters. In MongoDB, we use **aggregations** to automatically join in related documents, and in relational databases, we use joins.
+  The Join field is extremely performant and does not add additional query
+  overhead to your API responses until you add depth of 1 or above. It works in
+  all database adapters. In MongoDB, we use **aggregations** to automatically
+  join in related documents, and in relational databases, we use joins.
+</Banner>
+
+<Banner type="warning">
+  The Join Field is not supported in
+  [DocumentDB](https://aws.amazon.com/documentdb/) and [Azure Cosmos
+  DB](https://azure.microsoft.com/en-us/products/cosmos-db), as we internally
+  use MongoDB aggregations to query data for that field, which are limited
+  there. This can be changed in the future.
 </Banner>
 
 ### Schema advice
@@ -95,7 +106,8 @@ architecture. You might not want to have that `_rels` table, and would prefer to
 table design.
 
 <Banner type="success">
-  With the Join field, you can control your own junction table design, and avoid Payload's automatic _rels table creation.
+  With the Join field, you can control your own junction table design, and avoid
+  Payload's automatic _rels table creation.
 </Banner>
 
 The `join` field can be used in conjunction with _any_ collection - and if you wanted to define your own "junction"
@@ -123,9 +135,9 @@ powerful Admin UI.
 
 | Option                 | Description                                                                                                                                                                                                                            |
 | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *           | To be used as the property name when retrieved from the database. [More](./overview#field-names)                                                                                                                                       |
-| **`collection`** *     | The `slug`s having the relationship field or an array of collection slugs.                                                                                                                                                             |
-| **`on`** *             | The name of the relationship or upload field that relates to the collection document. Use dot notation for nested paths, like 'myGroup.relationName'. If `collection` is an array, this field must exist for all specified collections |
+| **`name`** \*          | To be used as the property name when retrieved from the database. [More](./overview#field-names)                                                                                                                                       |
+| **`collection`** \*    | The `slug`s having the relationship field or an array of collection slugs.                                                                                                                                                             |
+| **`on`** \*            | The name of the relationship or upload field that relates to the collection document. Use dot notation for nested paths, like 'myGroup.relationName'. If `collection` is an array, this field must exist for all specified collections |
 | **`where`**            | A `Where` query to hide related documents from appearing. Will be merged with any `where` specified in the request.                                                                                                                    |
 | **`maxDepth`**         | Default is 1, Sets a maximum population depth for this field, regardless of the remaining depth when this field is reached. [Max Depth](../queries/depth#max-depth).                                                                   |
 | **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                                                                                |
@@ -138,18 +150,17 @@ powerful Admin UI.
 | **`typescriptSchema`** | Override field type generation with providing a JSON schema.                                                                                                                                                                           |
 | **`graphQL`**          | Custom graphQL configuration for the field. [More details](/docs/graphql/overview#field-complexity)                                                                                                                                    |
 
-_* An asterisk denotes that a property is required._
-
+_\* An asterisk denotes that a property is required._
 
 ## Admin Config Options
 
 You can control the user experience of the join field using the `admin` config properties. The following options are supported:
 
-| Option                 | Description                                                                                                               |
-|------------------------|---------------------------------------------------------------------------------------------------------------------------|
+| Option                 | Description                                                                                                                |
+| ---------------------- | -------------------------------------------------------------------------------------------------------------------------- |
 | **`defaultColumns`**   | Array of field names that correspond to which columns to show in the relationship table. Default is the collection config. |
-| **`allowCreate`**      | Set to `false` to remove the controls for making new related documents from this field.                                   |
-| **`components.Label`** | Override the default Label of the Field Component. [More details](./overview#label)                                  |
+| **`allowCreate`**      | Set to `false` to remove the controls for making new related documents from this field.                                    |
+| **`components.Label`** | Override the default Label of the Field Component. [More details](./overview#label)                                        |
 
 ## Join Field Data
 
@@ -158,6 +169,7 @@ object with:
 
 - `docs` an array of related documents or only IDs if the depth is reached
 - `hasNextPage` a boolean indicating if there are additional documents
+- `totalDocs` a total number of documents, exists only if `count: true` is passed to the join query
 
 ```json
 {
@@ -171,7 +183,8 @@ object with:
       }
       // { ... }
     ],
-    "hasNextPage": false
+    "hasNextPage": false,
+    "totalDocs": 10 // if count: true is passed
   }
   // other fields...
 }
@@ -184,6 +197,7 @@ object with:
 
 - `docs` an array of `relationTo` - the collection slug of the document and `value` - the document itself or the ID if the depth is reached
 - `hasNextPage` a boolean indicating if there are additional documents
+- `totalDocs` a total number of documents, exists only if `count: true` is passed to the join query
 
 ```json
 {
@@ -194,13 +208,14 @@ object with:
         "relationTo": "posts",
         "value": {
           "id": "66e3431a3f23e684075aaeb9",
-           // other fields...
+          // other fields...
           "category": "66e3431a3f23e684075aae9c"
         }
       }
       // { ... }
     ],
-    "hasNextPage": false
+    "hasNextPage": false,
+    "totalDocs": 10 // if count: true is passed
   }
   // other fields...
 }
@@ -215,41 +230,44 @@ returning. This is useful for performance reasons when you don't need the relate
 The following query options are supported:
 
 | Property    | Description                                                                                         |
-|-------------|-----------------------------------------------------------------------------------------------------|
+| ----------- | --------------------------------------------------------------------------------------------------- |
 | **`limit`** | The maximum related documents to be returned, default is 10.                                        |
 | **`where`** | An optional `Where` query to filter joined documents. Will be merged with the field `where` object. |
 | **`sort`**  | A string used to order related results                                                              |
+| **`count`** | Whether include the count of related documents or not. Not included by default                      |
 
-These can be applied to the local API, GraphQL, and REST API.
+These can be applied to the Local API, GraphQL, and REST API.
 
 ### Local API
 
-By adding `joins` to the local API you can customize the request for each join field by the `name` of the field.
+By adding `joins` to the Local API you can customize the request for each join field by the `name` of the field.
 
 ```js
 const result = await payload.find({
   collection: 'categories',
   where: {
     title: {
-      equals: 'My Category'
-    }
+      equals: 'My Category',
+    },
   },
   joins: {
     relatedPosts: {
       limit: 5,
       where: {
         title: {
-          equals: 'My Post'
-        }
+          equals: 'My Post',
+        },
       },
-      sort: 'title'
-    }
-  }
+      sort: 'title',
+    },
+  },
 })
 ```
 
 <Banner type="warning">
-  Currently, `Where` query support on joined documents for join fields with an array of `collection` is limited and not supported for fields inside arrays and blocks.
+  Currently, `Where` query support on joined documents for join fields with an
+  array of `collection` is limited and not supported for fields inside arrays
+  and blocks.
 </Banner>
 
 <Banner type="warning">
@@ -269,7 +287,7 @@ const result = await payload.find({
 
 ### Rest API
 
-The rest API supports the same query options as the local API. You can use the `joins` query parameter to customize the
+The REST API supports the same query options as the Local API. You can use the `joins` query parameter to customize the
 request for each join field by the `name` of the field. For example, an API call to get a document with the related
 posts limited to 5 and sorted by title:
 
@@ -291,11 +309,7 @@ query {
       relatedPosts(
         sort: "createdAt"
         limit: 5
-        where: {
-          author: {
-            equals: "66e3431a3f23e684075aaeb9"
-          }
-        }
+        where: { author: { equals: "66e3431a3f23e684075aaeb9" } }
       ) {
         docs {
           title

docs/fields/json.mdx

@@ -31,7 +31,7 @@ export const MyJSONField: Field = {
 
 | Option                 | Description                                                                                                                                                                 |
 | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
 | **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                     |
 | **`unique`**           | Enforce that each entry in the Collection has a unique value for this field.                                                                                                |
 | **`index`**            | Build an [index](/docs/database/overview) for this field to produce faster queries. Set this field to `true` if your users will perform queries on this field's data often. |
@@ -49,7 +49,7 @@ export const MyJSONField: Field = {
 | **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                 |
 | **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)            |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Admin Options
 
@@ -60,7 +60,8 @@ import type { Field } from 'payload'
 
 export const MyJSONField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -90,13 +91,13 @@ export const ExampleCollection: CollectionConfig = {
   ],
 }
 ```
+
 ## JSON Schema Validation
 
 Payload JSON fields fully support the [JSON schema](https://json-schema.org/) standard. By providing a schema in your field config, the editor will be guided in the admin UI, getting typeahead for properties and their formats automatically. When the document is saved, the default validation will prevent saving any invalid data in the field according to the schema in your config.
 
 If you only provide a URL to a schema, Payload will fetch the desired schema if it is publicly available. If not, it is recommended to add the schema directly to your config or import it from another file so that it can be implemented consistently in your project.
 
-
 ### Local JSON Schema
 
 `collections/ExampleCollection.ts`
@@ -118,11 +119,10 @@ export const ExampleCollection: CollectionConfig = {
           properties: {
             foo: {
               enum: ['bar', 'foobar'],
-            }
+            },
           },
         },
       },
-
     },
   ],
 }

docs/fields/number.mdx

@@ -30,7 +30,7 @@ export const MyNumberField: Field = {
 
 | Option                 | Description                                                                                                                                                                 |
 | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
 | **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                     |
 | **`min`**              | Minimum value accepted. Used in the default `validation` function.                                                                                                          |
 | **`max`**              | Maximum value accepted. Used in the default `validation` function.                                                                                                          |
@@ -52,7 +52,7 @@ export const MyNumberField: Field = {
 | **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                 |
 | **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)            |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Admin Options
 
@@ -63,7 +63,8 @@ import type { Field } from 'payload'
 
 export const MyNumberField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -71,11 +72,11 @@ export const MyNumberField: Field = {
 
 The Number Field inherits all of the default options from the base [Field Admin Config](./overview#admin-options), plus the following additional options:
 
-| Property                       | Description                                                                                                                            |
-| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
-| **`step`**                     | Set a value for the number field to increment / decrement using browser controls.                                                      |
-| **`placeholder`**              | Set this property to define a placeholder string for the field.                                                                       |
-| **`autoComplete`**             | Set this property to a string that will be used for browser autocomplete.                                                             |
+| Property           | Description                                                                       |
+| ------------------ | --------------------------------------------------------------------------------- |
+| **`step`**         | Set a value for the number field to increment / decrement using browser controls. |
+| **`placeholder`**  | Set this property to define a placeholder string for the field.                   |
+| **`autoComplete`** | Set this property to a string that will be used for browser autocomplete.         |
 
 ## Example
 

docs/fields/overview.mdx

@@ -19,9 +19,10 @@ import type { CollectionConfig } from 'payload'
 
 export const Page: CollectionConfig = {
   // ...
-  fields: [ // highlight-line
+  fields: [
+    // highlight-line
     // ...
-  ]
+  ],
 }
 ```
 
@@ -41,14 +42,16 @@ export const Page: CollectionConfig = {
     {
       name: 'field',
       type: 'text',
-    }
-  ]
+    },
+  ],
   // highlight-end
 }
 ```
 
 <Banner type="warning">
-  **Reminder:** Each field is an object with at least the `type` property. This matches the field to its corresponding Field Type. [More details](#field-options).
+  **Reminder:** Each field is an object with at least the `type` property. This
+  matches the field to its corresponding Field Type. [More
+  details](#field-options).
 </Banner>
 
 There are three main categories of fields in Payload:
@@ -104,7 +107,11 @@ Here are the available Virtual Fields:
 - [Join](../fields/join) - achieves two-way data binding between fields
 
 <Banner type="success">
-  **Tip:** Don't see a built-in field type that you need? Build it! Using a combination of [Field Validations](#validation) and [Custom Components](../custom-components/overview), you can override the entirety of how a component functions within the [Admin Panel](../admin/overview) to effectively create your own field type.
+  **Tip:** Don't see a built-in field type that you need? Build it! Using a
+  combination of [Field Validations](#validation) and [Custom
+  Components](../custom-components/overview), you can override the entirety of
+  how a component functions within the [Admin Panel](../admin/overview) to
+  effectively create your own field type.
 </Banner>
 
 ## Field Options
@@ -123,7 +130,8 @@ export const MyField: Field = {
 ```
 
 <Banner type="warning">
-  For a full list of configuration options, see the documentation for each [Field Type](#field-types).
+  For a full list of configuration options, see the documentation for each
+  [Field Type](#field-types).
 </Banner>
 
 ### Field Names
@@ -165,7 +173,7 @@ export const MyField: Field = {
   // highlight-start
   hooks: {
     // ...
-  }
+  },
   // highlight-end
 }
 ```
@@ -187,7 +195,7 @@ export const MyField: Field = {
   // highlight-start
   access: {
     // ...
-  }
+  },
   // highlight-end
 }
 ```
@@ -239,7 +247,8 @@ export const myField: Field = {
 ```
 
 <Banner type="success">
-  **Tip:** You can use async `defaultValue` functions to fill fields with data from API requests or Local API using `req.payload`.
+  **Tip:** You can use async `defaultValue` functions to fill fields with data
+  from API requests or Local API using `req.payload`.
 </Banner>
 
 ### Validation
@@ -254,7 +263,7 @@ import type { Field } from 'payload'
 export const MyField: Field = {
   type: 'text',
   name: 'myField',
-  validate: value => Boolean(value) || 'This field is required' // highlight-line
+  validate: (value) => Boolean(value) || 'This field is required', // highlight-line
 }
 ```
 
@@ -262,10 +271,10 @@ Custom validation functions should return either `true` or a `string` representi
 
 The following arguments are provided to the `validate` function:
 
-|    Argument    |    Description                                                                                      |
-| --- | --- |
-|    `value`     |    The value of the field being validated.                                                           |
-|    `ctx`      |    An object with additional data and context. [More details](#validation-context)    |
+| Argument | Description                                                                     |
+| -------- | ------------------------------------------------------------------------------- |
+| `value`  | The value of the field being validated.                                         |
+| `ctx`    | An object with additional data and context. [More details](#validation-context) |
 
 #### Validation Context
 
@@ -286,14 +295,15 @@ export const MyField: Field = {
 
 The following additional properties are provided in the `ctx` object:
 
-|    Property         |    Description                                                                                                                              |
-| --- | --- |
-|    `data`           |    An object containing the full collection or global document currently being edited.                                                      |
-|    `siblingData`    |    An object containing document data that is scoped to only fields within the same parent of this field.                                   |
-|    `operation`      |    Will be `create` or `update` depending on the UI action or API call.                                                                     |
-|    `id`             |    The `id` of the current document being edited. `id` is `undefined` during the `create` operation.                                        |
-|    `req`            |    The current HTTP request object. Contains `payload`, `user`, etc.                                                                        |
-|    `event`          |    Either `onChange` or `submit` depending on the current action. Used as a performance opt-in. [More details](#async-field-validations).    |
+| Property      | Description                                                                                                                                                  |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `data`        | An object containing the full collection or global document currently being edited.                                                                          |
+| `siblingData` | An object containing document data that is scoped to only fields within the same parent of this field.                                                       |
+| `operation`   | Will be `create` or `update` depending on the UI action or API call.                                                                                         |
+| `path`        | The full path to the field in the schema, represented as an array of string segments, including array indexes. I.e `['group', 'myArray', '1', 'textField']`. |
+| `id`          | The `id` of the current document being edited. `id` is `undefined` during the `create` operation.                                                            |
+| `req`         | The current HTTP request object. Contains `payload`, `user`, etc.                                                                                            |
+| `event`       | Either `onChange` or `submit` depending on the current action. Used as a performance opt-in. [More details](#async-field-validations).                       |
 
 #### Reusing Default Field Validations
 
@@ -399,7 +409,9 @@ export const MyCollection: CollectionConfig = {
 ```
 
 <Banner type="warning">
-  **Reminder:** The Custom ID Fields can only be of type [`Number`](./number) or [`Text`](./text). Custom ID fields with type `text` must not contain `/` or `.` characters.
+  **Reminder:** The Custom ID Fields can only be of type [`Number`](./number) or
+  [`Text`](./text). Custom ID fields with type `text` must not contain `/` or
+  `.` characters.
 </Banner>
 
 ## Admin Options
@@ -416,31 +428,32 @@ export const CollectionConfig: CollectionConfig = {
     {
       name: 'myField',
       type: 'text',
-      admin: { // highlight-line
+      admin: {
+        // highlight-line
         // ...
       },
-    }
-  ]
+    },
+  ],
 }
 ```
 
 The following options are available:
 
-|    Option                     |    Description                                                                                                                                                                                                                         |
-| --- | --- |
-|    **`condition`**            |    Programmatically show / hide fields based on other fields. [More details](#conditional-logic).                                                                                                                       |
-|    **`components`**           |    All Field Components can be swapped out for [Custom Components](../custom-components/overview) that you define.                                                                                              |
-|    **`description`**          |    Helper text to display alongside the field to provide more information for the editor. [More details](#description).                                                                                                 |
-|    **`position`**             |    Specify if the field should be rendered in the sidebar by defining `position: 'sidebar'`.                                                                                                                                           |
-|    **`width`**                |    Restrict the width of a field. You can pass any string-based value here, be it pixels, percentages, etc. This property is especially useful when fields are nested within a `Row` type where they can be organized horizontally.    |
-|    **`style`**                |    [CSS Properties](https://developer.mozilla.org/en-US/docs/Web/CSS) to inject into the root element of the field.                                                                                                                    |
-|    **`className`**            |    Attach a [CSS class attribute](https://developer.mozilla.org/en-US/docs/Web/CSS/Class_selectors) to the root DOM element of a field.                                                                                                |
-|    **`readOnly`**             |    Setting a field to `readOnly` has no effect on the API whatsoever but disables the admin component's editability to prevent editors from modifying the field's value.                                                               |
-|    **`disabled`**             |    If a field is `disabled`, it is completely omitted from the [Admin Panel](../admin/overview) entirely.                                                                                                                              |
-|    **`disableBulkEdit`**      |    Set `disableBulkEdit` to `true` to prevent fields from appearing in the select options when making edits for multiple documents. Defaults to `true` for UI fields.                                                                  |
-|    **`disableListColumn`**    |    Set `disableListColumn` to `true` to prevent fields from appearing in the list view column selector.                                                                                                                                |
-|    **`disableListFilter`**    |    Set `disableListFilter` to `true` to prevent fields from appearing in the list view filter options.                                                                                                                                 |
-|    **`hidden`**               |    Will transform the field into a `hidden` input type. Its value will still submit with requests in the Admin Panel, but the field itself will not be visible to editors.                                                             |
+| Option                  | Description                                                                                                                                                                                                                      |
+| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`condition`**         | Programmatically show / hide fields based on other fields. [More details](#conditional-logic).                                                                                                                                   |
+| **`components`**        | All Field Components can be swapped out for [Custom Components](../custom-components/overview) that you define.                                                                                                                  |
+| **`description`**       | Helper text to display alongside the field to provide more information for the editor. [More details](#description).                                                                                                             |
+| **`position`**          | Specify if the field should be rendered in the sidebar by defining `position: 'sidebar'`.                                                                                                                                        |
+| **`width`**             | Restrict the width of a field. You can pass any string-based value here, be it pixels, percentages, etc. This property is especially useful when fields are nested within a `Row` type where they can be organized horizontally. |
+| **`style`**             | [CSS Properties](https://developer.mozilla.org/en-US/docs/Web/CSS) to inject into the root element of the field.                                                                                                                 |
+| **`className`**         | Attach a [CSS class attribute](https://developer.mozilla.org/en-US/docs/Web/CSS/Class_selectors) to the root DOM element of a field.                                                                                             |
+| **`readOnly`**          | Setting a field to `readOnly` has no effect on the API whatsoever but disables the admin component's editability to prevent editors from modifying the field's value.                                                            |
+| **`disabled`**          | If a field is `disabled`, it is completely omitted from the [Admin Panel](../admin/overview) entirely.                                                                                                                           |
+| **`disableBulkEdit`**   | Set `disableBulkEdit` to `true` to prevent fields from appearing in the select options when making edits for multiple documents. Defaults to `true` for UI fields.                                                               |
+| **`disableListColumn`** | Set `disableListColumn` to `true` to prevent fields from appearing in the list view column selector.                                                                                                                             |
+| **`disableListFilter`** | Set `disableListFilter` to `true` to prevent fields from appearing in the list view filter options.                                                                                                                              |
+| **`hidden`**            | Will transform the field into a `hidden` input type. Its value will still submit with requests in the Admin Panel, but the field itself will not be visible to editors.                                                          |
 
 ### Field Descriptions
 
@@ -465,22 +478,24 @@ export const MyCollectionConfig: CollectionConfig = {
       name: 'myField',
       type: 'text',
       admin: {
-        description: 'Hello, world!' // highlight-line
+        description: 'Hello, world!', // highlight-line
       },
     },
-  ]
+  ],
 }
 ```
 
 <Banner type="warning">
-  **Reminder:** To replace the Field Description with a [Custom Component](../custom-components/overview), use the `admin.components.Description` property. [More details](#description).
+  **Reminder:** To replace the Field Description with a [Custom
+  Component](../custom-components/overview), use the
+  `admin.components.Description` property. [More details](#description).
 </Banner>
 
 #### Description Functions
 
 Custom Descriptions can also be defined as a function. Description Functions are executed on the server and can be used to format simple descriptions based on the user's current [Locale](../configuration/localization).
 
-To add a Description Function to a field, set the `admin.description` property to a *function* in your Field Config:
+To add a Description Function to a field, set the `admin.description` property to a _function_ in your Field Config:
 
 ```ts
 import type { CollectionConfig } from 'payload'
@@ -493,30 +508,41 @@ export const MyCollectionConfig: CollectionConfig = {
       name: 'myField',
       type: 'text',
       admin: {
-        description: ({ t }) => `${t('Hello, world!')}` // highlight-line
+        description: ({ t }) => `${t('Hello, world!')}`, // highlight-line
       },
     },
-  ]
+  ],
 }
 ```
 
 All Description Functions receive the following arguments:
 
-|    Argument          |    Description                                                         |
-| --- | --- |
-|    **`t`**           |    The `t` function used to internationalize the Admin Panel. [More details](../configuration/i18n)    |
+| Argument | Description                                                                                      |
+| -------- | ------------------------------------------------------------------------------------------------ |
+| **`t`**  | The `t` function used to internationalize the Admin Panel. [More details](../configuration/i18n) |
 
 <Banner type="info">
-  **Note:** If you need to subscribe to live updates within your form, use a Description Component instead. [More details](#description).
+  **Note:** If you need to subscribe to live updates within your form, use a
+  Description Component instead. [More details](#description).
 </Banner>
 
 ### Conditional Logic
 
-You can show and hide fields based on what other fields are doing by utilizing conditional logic on a field by field basis. The `condition` property on a field's admin config accepts a function which takes three arguments:
+You can show and hide fields based on what other fields are doing by utilizing conditional logic on a field by field basis. The `condition` property on a field's admin config accepts a function which takes the following arguments:
 
-- `data` - the entire document's data that is currently being edited
-- `siblingData` - only the fields that are direct siblings to the field with the condition
-- `{ user }` - the final argument is an object containing the currently authenticated user
+| Argument          | Description                                                                      |
+| ----------------- | -------------------------------------------------------------------------------- |
+| **`data`**        | The entire document's data that is currently being edited.                       |
+| **`siblingData`** | Only the fields that are direct siblings to the field with the condition.        |
+| **`ctx`**         | An object containing additional information about the field’s location and user. |
+
+The `ctx` object:
+
+| Property        | Description                                                                                                                                                  |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| **`blockData`** | The nearest parent block's data. If the field is not inside a block, this will be `undefined`.                                                               |
+| **`path`**      | The full path to the field in the schema, represented as an array of string segments, including array indexes. I.e `['group', 'myArray', '1', 'textField']`. |
+| **`user`**      | The currently authenticated user object.                                                                                                                     |
 
 The `condition` function should return a boolean that will control if the field should be displayed or not.
 
@@ -535,7 +561,7 @@ The `condition` function should return a boolean that will control if the field
       type: 'text',
       admin: {
         // highlight-start
-        condition: (data, siblingData, { user }) => {
+        condition: (data, siblingData, { blockData, path, user }) => {
           if (data.enableGreeting) {
             return true
           } else {
@@ -570,28 +596,29 @@ export const CollectionConfig: CollectionConfig = {
     {
       // ...
       admin: {
-        components: { // highlight-line
+        components: {
+          // highlight-line
           // ...
         },
       },
-    }
-  ]
+    },
+  ],
 }
 ```
 
 The following options are available:
 
-|    Component       |    Description                                                                                                                    |
-| --- | --- |
-|    **`Field`**     |    The form field rendered of the Edit View. [More details](#field).                                                   |
-|    **`Cell`**      |    The table cell rendered of the List View. [More details](#cell).                 |
-|    **`Filter`**    |    The filter component rendered in the List View. [More details](#filter).    |
-|    **`Label`**          |    Override the default Label of the Field Component. [More details](#label).                                       |
-|    **`Error`**          |    Override the default Error of the Field Component. [More details](#error).                                       |
-|   **`Diff`**   |   Override the default Diff component rendered in the Version Diff View. [More details](#diff).                 |
-|    **`Description`**    |    Override the default Description of the Field Component. [More details](#description).                         |
-|    **`beforeInput`**    |    An array of elements that will be added before the input of the Field Component. [More details](#afterinput-and-beforeinput).   |
-|    **`afterInput`**     |    An array of elements that will be added after the input of the Field Component. [More details](#afterinput-and-beforeinput).    |
+| Component         | Description                                                                                                                   |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| **`Field`**       | The form field rendered of the Edit View. [More details](#field).                                                             |
+| **`Cell`**        | The table cell rendered of the List View. [More details](#cell).                                                              |
+| **`Filter`**      | The filter component rendered in the List View. [More details](#filter).                                                      |
+| **`Label`**       | Override the default Label of the Field Component. [More details](#label).                                                    |
+| **`Error`**       | Override the default Error of the Field Component. [More details](#error).                                                    |
+| **`Diff`**        | Override the default Diff component rendered in the Version Diff View. [More details](#diff).                                 |
+| **`Description`** | Override the default Description of the Field Component. [More details](#description).                                        |
+| **`beforeInput`** | An array of elements that will be added before the input of the Field Component. [More details](#afterinput-and-beforeinput). |
+| **`afterInput`**  | An array of elements that will be added after the input of the Field Component. [More details](#afterinput-and-beforeinput).  |
 
 #### Field
 
@@ -613,52 +640,55 @@ export const CollectionConfig: CollectionConfig = {
           Field: '/path/to/MyFieldComponent', // highlight-line
         },
       },
-    }
-  ]
+    },
+  ],
 }
 ```
 
-*For details on how to build Custom Components, see [Building Custom Components](../custom-components/overview#building-custom-components).*
+_For details on how to build Custom Components, see [Building Custom Components](../custom-components/overview#building-custom-components)._
 
 <Banner type="warning">
-  Instead of replacing the entire Field Component, you can alternately replace or slot-in only specific parts by using the [`Label`](#label), [`Error`](#error), [`beforeInput`](#afterinput-and-beforinput), and [`afterInput`](#afterinput-and-beforinput) properties.
+  Instead of replacing the entire Field Component, you can alternately replace
+  or slot-in only specific parts by using the [`Label`](#label),
+  [`Error`](#error), [`beforeInput`](#afterinput-and-beforinput), and
+  [`afterInput`](#afterinput-and-beforinput) properties.
 </Banner>
 
 ##### Default Props
 
 All Field Components receive the following props by default:
 
-|    Property                |    Description                                                                                                                                                                                                                            |
-| --- | --- |
-|    **`docPreferences`**    |    An object that contains the [Preferences](../admin/preferences) for the document.                                                                                                                                                             |
-|    **`field`**             |    In Client Components, this is the sanitized Client Field Config. In Server Components, this is the original Field Config. Server Components will also receive the sanitized field config through the`clientField` prop (see below).    |
-|    **`locale`**            |    The locale of the field. [More details](../configuration/localization).                                                                                                                                                                |
-|    **`readOnly`**          |    A boolean value that represents if the field is read-only or not.                                                                                                                                                                      |
-|    **`user`**              |    The currently authenticated user. [More details](../authentication/overview).                                                                                                                                                          |
-|    **`validate`**          |    A function that can be used to validate the field.                                                                                                                                                                                     |
-|    **`path`**              |    A string representing the direct, dynamic path to the field at runtime, i.e. `myGroup.myArray.0.myField`.                                                                                                                              |
-|    **`schemaPath`**        |    A string representing the direct, static path to the Field Config, i.e. `posts.myGroup.myArray.myField`.                                                                                                         |
-|    **`indexPath`**         |    A hyphen-notated string representing the path to the field *within the nearest named ancestor field*, i.e. `0-0`                                                                                                                       |
+| Property             | Description                                                                                                                                                                                                                         |
+| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`docPreferences`** | An object that contains the [Preferences](../admin/preferences) for the document.                                                                                                                                                   |
+| **`field`**          | In Client Components, this is the sanitized Client Field Config. In Server Components, this is the original Field Config. Server Components will also receive the sanitized field config through the`clientField` prop (see below). |
+| **`locale`**         | The locale of the field. [More details](../configuration/localization).                                                                                                                                                             |
+| **`readOnly`**       | A boolean value that represents if the field is read-only or not.                                                                                                                                                                   |
+| **`user`**           | The currently authenticated user. [More details](../authentication/overview).                                                                                                                                                       |
+| **`validate`**       | A function that can be used to validate the field.                                                                                                                                                                                  |
+| **`path`**           | A string representing the direct, dynamic path to the field at runtime, i.e. `myGroup.myArray.0.myField`.                                                                                                                           |
+| **`schemaPath`**     | A string representing the direct, static path to the Field Config, i.e. `posts.myGroup.myArray.myField`.                                                                                                                            |
+| **`indexPath`**      | A hyphen-notated string representing the path to the field _within the nearest named ancestor field_, i.e. `0-0`                                                                                                                    |
 
 In addition to the above props, all Server Components will also receive the following props:
 
-|    Property             |    Description                                                                      |
-| --- | --- |
-|    **`clientField`**    |    The serializable Client Field Config.                                            |
-|    **`field`**          |    The Field Config.                                                                |
-|    **`data`**           |    The current document being edited.                                               |
-|    **`i18n`**           |    The [i18n](../configuration/i18n) object.                                        |
-|    **`payload`**        |    The [Payload](../local-api/overview) class.                                      |
-|    **`permissions`**    |    The field permissions based on the currently authenticated user.                 |
-|    **`siblingData`**    |    The data of the field's siblings.                                                |
-|    **`user`**           |    The currently authenticated user. [More details](../authentication/overview).    |
-|    **`value`**          |    The value of the field at render-time.                                           |
+| Property          | Description                                                                   |
+| ----------------- | ----------------------------------------------------------------------------- |
+| **`clientField`** | The serializable Client Field Config.                                         |
+| **`field`**       | The Field Config.                                                             |
+| **`data`**        | The current document being edited.                                            |
+| **`i18n`**        | The [i18n](../configuration/i18n) object.                                     |
+| **`payload`**     | The [Payload](../local-api/overview) class.                                   |
+| **`permissions`** | The field permissions based on the currently authenticated user.              |
+| **`siblingData`** | The data of the field's siblings.                                             |
+| **`user`**        | The currently authenticated user. [More details](../authentication/overview). |
+| **`value`**       | The value of the field at render-time.                                        |
 
 ##### Sending and receiving values from the form
 
 When swapping out the `Field` component, you are responsible for sending and receiving the field's `value` from the form itself.
 
-To do so, import the [`useField`](../admin/hooks#usefield) hook from `@payloadcms/ui` and use it to manage the field's value:
+To do so, import the [`useField`](../admin/react-hooks#usefield) hook from `@payloadcms/ui` and use it to manage the field's value:
 
 ```tsx
 'use client'
@@ -667,17 +697,14 @@ import { useField } from '@payloadcms/ui'
 export const CustomTextField: React.FC = () => {
   const { value, setValue } = useField() // highlight-line
 
-  return (
-    <input
-      onChange={(e) => setValue(e.target.value)}
-      value={value}
-    />
-  )
+  return <input onChange={(e) => setValue(e.target.value)} value={value} />
 }
 ```
 
 <Banner type="success">
-  For a complete list of all available React hooks, see the [Payload React Hooks](../admin/hooks) documentation. For additional help, see [Building Custom Components](../custom-components/overview#building-custom-components).
+  For a complete list of all available React hooks, see the [Payload React
+  Hooks](../admin/react-hooks) documentation. For additional help, see [Building
+  Custom Components](../custom-components/overview#building-custom-components).
 </Banner>
 
 ##### TypeScript#field-component-types
@@ -718,10 +745,10 @@ export const myField: Field = {
 
 All Cell Components receive the same [Default Field Component Props](#field), plus the following:
 
-|    Property            |    Description                                                          |
-| --- | --- |
-|    **`link`**    |    A boolean representing whether this cell should be wrapped in a link.    |
-|    **`onClick`**    |    A function that is called when the cell is clicked.    |
+| Property      | Description                                                           |
+| ------------- | --------------------------------------------------------------------- |
+| **`link`**    | A boolean representing whether this cell should be wrapped in a link. |
+| **`onClick`** | A function that is called when the cell is clicked.                   |
 
 For details on how to build Custom Components themselves, see [Building Custom Components](../custom-components/overview#building-custom-components).
 
@@ -804,10 +831,10 @@ export const MyCollectionConfig: CollectionConfig = {
       admin: {
         components: {
           Description: '/path/to/MyCustomDescriptionComponent', // highlight-line
-        }
-      }
-    }
-  ]
+        },
+      },
+    },
+  ],
 }
 ```
 
@@ -901,7 +928,7 @@ import type {
 
 #### afterInput and beforeInput
 
-With these properties you can add multiple components *before* and *after* the input element, as their name suggests. This is useful when you need to render additional elements alongside the field without replacing the entire field component.
+With these properties you can add multiple components _before_ and _after_ the input element, as their name suggests. This is useful when you need to render additional elements alongside the field without replacing the entire field component.
 
 To add components before and after the input element, use the `admin.components.beforeInput` and `admin.components.afterInput` properties in your Field Config:
 
@@ -921,10 +948,10 @@ export const MyCollectionConfig: CollectionConfig = {
           beforeInput: ['/path/to/MyCustomComponent'],
           afterInput: ['/path/to/MyOtherCustomComponent'],
           // highlight-end
-        }
-      }
-    }
-  ]
+        },
+      },
+    },
+  ],
 }
 ```
 

docs/fields/point.mdx

@@ -27,15 +27,14 @@ export const MyPointField: Field = {
 ```
 
 <Banner type="warning">
-  **Important:**
-  The Point Field currently is not supported in SQLite.
+  **Important:** The Point Field currently is not supported in SQLite.
 </Banner>
 
 ## Config
 
 | Option                 | Description                                                                                                                                                                               |
 | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                                    |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                                    |
 | **`label`**            | Used as a field label in the Admin Panel and to name the generated GraphQL type.                                                                                                          |
 | **`unique`**           | Enforce that each entry in the Collection has a unique value for this field.                                                                                                              |
 | **`index`**            | Build an [index](/docs/database/overview) for this field to produce faster queries. To support location queries, point index defaults to `2dsphere`, to disable the index set to `false`. |
@@ -47,12 +46,12 @@ export const MyPointField: Field = {
 | **`defaultValue`**     | Provide data to be used for this field's default value. [More](/docs/fields/overview#default-values)                                                                                      |
 | **`localized`**        | Enable localization for this field. Requires [localization to be enabled](/docs/configuration/localization) in the Base config.                                                           |
 | **`required`**         | Require this field to have a value.                                                                                                                                                       |
-| **`admin`**            | Admin-specific configuration. [More details](./overview#admin-options).                                                                                                              |
+| **`admin`**            | Admin-specific configuration. [More details](./overview#admin-options).                                                                                                                   |
 | **`custom`**           | Extension point for adding custom data (e.g. for plugins)                                                                                                                                 |
 | **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                               |
 | **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)                          |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Example
 
@@ -81,6 +80,7 @@ In order to do query based on the distance to another point, you can use the `ne
 
 In order to do query based on whether points are within a specific area defined in GeoJSON, you can use the `within` operator.
 Example:
+
 ```ts
 const polygon: Point[] = [
   [9.0, 19.0], // bottom-left
@@ -91,7 +91,7 @@ const polygon: Point[] = [
 ]
 
 payload.find({
-  collection: "points",
+  collection: 'points',
   where: {
     point: {
       within: {
@@ -103,11 +103,11 @@ payload.find({
 })
 ```
 
-
 ## Querying - intersects
 
 In order to do query based on whether points intersect a specific area defined in GeoJSON, you can use the `intersects` operator.
 Example:
+
 ```ts
 const polygon: Point[] = [
   [9.0, 19.0], // bottom-left
@@ -118,7 +118,7 @@ const polygon: Point[] = [
 ]
 
 payload.find({
-  collection: "points",
+  collection: 'points',
   where: {
     point: {
       intersects: {
@@ -148,7 +148,12 @@ export const CustomPointFieldServer: PointFieldServerComponent = ({
   permissions,
 }) => {
   return (
-    <PointField field={clientField} path={path} schemaPath={schemaPath} permissions={permissions} />
+    <PointField
+      field={clientField}
+      path={path}
+      schemaPath={schemaPath}
+      permissions={permissions}
+    />
   )
 }
 ```

docs/fields/radio.mdx

@@ -26,43 +26,44 @@ export const MyRadioField: Field = {
   type: 'radio',
   options: [
     // ...
-  ]
+  ],
   // highlight-end
 }
 ```
 
 ## Config Options
 
-| Option                 | Description                                                                                                                                                                 |
-| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
-| **`options`** *       | Array of options to allow the field to store. Can either be an array of strings, or an array of objects containing an `label` string and a `value` string.                  |
-| **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                     |
-| **`validate`**         | Provide a custom validation function that will be executed on both the Admin Panel and the backend. [More](/docs/fields/overview#validation)                                |
-| **`index`**            | Build an [index](/docs/database/overview) for this field to produce faster queries. Set this field to `true` if your users will perform queries on this field's data often. |
-| **`saveToJWT`**        | If this field is top-level and nested in a config supporting [Authentication](/docs/authentication/overview), include its data in the user JWT.                             |
-| **`hooks`**            | Provide Field Hooks to control logic for this field. [More details](../hooks/fields).                                                                                       |
-| **`access`**           | Provide Field Access Control to denote what users can see and do with this field's data. [More details](../access-control/fields).                                          |
-| **`hidden`**           | Restrict this field's visibility from all APIs entirely. Will still be saved to the database, but will not appear in any API or the Admin Panel.                            |
-| **`defaultValue`**     | Provide data to be used for this field's default value. The default value must exist within provided values in `options`. [More](/docs/fields/overview#default-values)      |
-| **`localized`**        | Enable localization for this field. Requires [localization to be enabled](/docs/configuration/localization) in the Base config.                                             |
-| **`required`**         | Require this field to have a value.                                                                                                                                         |
-| **`admin`**            | Admin-specific configuration. [More details](#admin-options).                                                                                                               |
-| **`custom`**           | Extension point for adding custom data (e.g. for plugins)                                                                                                                   |
-| **`enumName`**         | Custom enum name for this field when using SQL Database Adapter ([Postgres](/docs/database/postgres)). Auto-generated from name if not defined.                             |
-| **`interfaceName`**    | Create a top level, reusable [Typescript interface](/docs/typescript/generating-types#custom-field-interfaces) & [GraphQL type](/docs/graphql/graphql-schema#custom-field-schemas).                                                                                                |
-| **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                 |
-| **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)            |
+| Option                 | Description                                                                                                                                                                         |
+| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                              |
+| **`options`** \*       | Array of options to allow the field to store. Can either be an array of strings, or an array of objects containing an `label` string and a `value` string.                          |
+| **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                             |
+| **`validate`**         | Provide a custom validation function that will be executed on both the Admin Panel and the backend. [More](/docs/fields/overview#validation)                                        |
+| **`index`**            | Build an [index](/docs/database/overview) for this field to produce faster queries. Set this field to `true` if your users will perform queries on this field's data often.         |
+| **`saveToJWT`**        | If this field is top-level and nested in a config supporting [Authentication](/docs/authentication/overview), include its data in the user JWT.                                     |
+| **`hooks`**            | Provide Field Hooks to control logic for this field. [More details](../hooks/fields).                                                                                               |
+| **`access`**           | Provide Field Access Control to denote what users can see and do with this field's data. [More details](../access-control/fields).                                                  |
+| **`hidden`**           | Restrict this field's visibility from all APIs entirely. Will still be saved to the database, but will not appear in any API or the Admin Panel.                                    |
+| **`defaultValue`**     | Provide data to be used for this field's default value. The default value must exist within provided values in `options`. [More](/docs/fields/overview#default-values)              |
+| **`localized`**        | Enable localization for this field. Requires [localization to be enabled](/docs/configuration/localization) in the Base config.                                                     |
+| **`required`**         | Require this field to have a value.                                                                                                                                                 |
+| **`admin`**            | Admin-specific configuration. [More details](#admin-options).                                                                                                                       |
+| **`custom`**           | Extension point for adding custom data (e.g. for plugins)                                                                                                                           |
+| **`enumName`**         | Custom enum name for this field when using SQL Database Adapter ([Postgres](/docs/database/postgres)). Auto-generated from name if not defined.                                     |
+| **`interfaceName`**    | Create a top level, reusable [Typescript interface](/docs/typescript/generating-types#custom-field-interfaces) & [GraphQL type](/docs/graphql/graphql-schema#custom-field-schemas). |
+| **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                         |
+| **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)                    |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 <Banner type="warning">
   **Important:**
 
-  Option values should be strings that do not contain hyphens or special characters due to GraphQL
-  enumeration naming constraints. Underscores are allowed. If you determine you need your option
-  values to be non-strings or contain special characters, they will be formatted accordingly before
-  being used as a GraphQL enum.
+Option values should be strings that do not contain hyphens or special characters due to GraphQL
+enumeration naming constraints. Underscores are allowed. If you determine you need your option
+values to be non-strings or contain special characters, they will be formatted accordingly before
+being used as a GraphQL enum.
+
 </Banner>
 
 ## Admin Options
@@ -74,7 +75,8 @@ import type { Field } from 'payload'
 
 export const MyRadioField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -82,9 +84,9 @@ export const MyRadioField: Field = {
 
 The Radio Field inherits all of the default options from the base [Field Admin Config](./overview#admin-options), plus the following additional options:
 
-| Property                       | Description                                                                                                                            |
-| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
-| **`layout`**                   | Allows for the radio group to be styled as a horizontally or vertically distributed list. The default value is `horizontal`.          |
+| Property     | Description                                                                                                                  |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------- |
+| **`layout`** | Allows for the radio group to be styled as a horizontally or vertically distributed list. The default value is `horizontal`. |
 
 ## Example
 

docs/fields/relationship.mdx

@@ -37,40 +37,41 @@ export const MyRelationshipField: Field = {
 
 ## Config Options
 
-| Option                 | Description                                                                                                                                                                     |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                           |
-| **`relationTo`** *    | Provide one or many collection `slug`s to be able to assign relationships to.                                                                                                    |
-| **`filterOptions`**    | A query to filter which options appear in the UI and validate against. [More](#filtering-relationship-options).                                                                 |
-| **`hasMany`**          | Boolean when, if set to `true`, allows this field to have many relations instead of only one.                                                                                   |
-| **`minRows`**          | A number for the fewest allowed items during validation when a value is present. Used with `hasMany`.                                                                           |
-| **`maxRows`**          | A number for the most allowed items during validation when a value is present. Used with `hasMany`.                                                                             |
-| **`maxDepth`**         | Sets a maximum population depth for this field, regardless of the remaining depth when this field is reached. [Max Depth](/docs/queries/depth#max-depth)                        |
-| **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                         |
-| **`unique`**           | Enforce that each entry in the Collection has a unique value for this field.                                                                                                    |
-| **`validate`**         | Provide a custom validation function that will be executed on both the Admin Panel and the backend. [More](/docs/fields/overview#validation)                                    |
-| **`index`**            | Build an [index](/docs/database/overview) for this field to produce faster queries. Set this field to `true` if your users will perform queries on this field's data often.     |
-| **`saveToJWT`**        | If this field is top-level and nested in a config supporting [Authentication](/docs/authentication/overview), include its data in the user JWT.                                 |
-| **`hooks`**            | Provide Field Hooks to control logic for this field. [More details](../hooks/fields).                                                                                           |
-| **`access`**           | Provide Field Access Control to denote what users can see and do with this field's data. [More details](../access-control/fields).                                              |
-| **`hidden`**           | Restrict this field's visibility from all APIs entirely. Will still be saved to the database, but will not appear in any API or the Admin Panel.                                |
-| **`defaultValue`**     | Provide data to be used for this field's default value. [More](/docs/fields/overview#default-values)                                                                            |
-| **`localized`**        | Enable localization for this field. Requires [localization to be enabled](/docs/configuration/localization) in the Base config.                                                 |
-| **`required`**         | Require this field to have a value.                                                                                                                                             |
-| **`admin`**            | Admin-specific configuration. [More details](#admin-options).                                                                                                                   |
-| **`custom`**           | Extension point for adding custom data (e.g. for plugins)                                                                                                                       |
-| **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                     |
-| **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)                |
-| **`graphQL`**          | Custom graphQL configuration for the field. [More details](/docs/graphql/overview#field-complexity)                                                                             |
+| Option                 | Description                                                                                                                                                                 |
+| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
+| **`relationTo`** \*    | Provide one or many collection `slug`s to be able to assign relationships to.                                                                                               |
+| **`filterOptions`**    | A query to filter which options appear in the UI and validate against. [More](#filtering-relationship-options).                                                             |
+| **`hasMany`**          | Boolean when, if set to `true`, allows this field to have many relations instead of only one.                                                                               |
+| **`minRows`**          | A number for the fewest allowed items during validation when a value is present. Used with `hasMany`.                                                                       |
+| **`maxRows`**          | A number for the most allowed items during validation when a value is present. Used with `hasMany`.                                                                         |
+| **`maxDepth`**         | Sets a maximum population depth for this field, regardless of the remaining depth when this field is reached. [Max Depth](/docs/queries/depth#max-depth)                    |
+| **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                     |
+| **`unique`**           | Enforce that each entry in the Collection has a unique value for this field.                                                                                                |
+| **`validate`**         | Provide a custom validation function that will be executed on both the Admin Panel and the backend. [More](/docs/fields/overview#validation)                                |
+| **`index`**            | Build an [index](/docs/database/overview) for this field to produce faster queries. Set this field to `true` if your users will perform queries on this field's data often. |
+| **`saveToJWT`**        | If this field is top-level and nested in a config supporting [Authentication](/docs/authentication/overview), include its data in the user JWT.                             |
+| **`hooks`**            | Provide Field Hooks to control logic for this field. [More details](../hooks/fields).                                                                                       |
+| **`access`**           | Provide Field Access Control to denote what users can see and do with this field's data. [More details](../access-control/fields).                                          |
+| **`hidden`**           | Restrict this field's visibility from all APIs entirely. Will still be saved to the database, but will not appear in any API or the Admin Panel.                            |
+| **`defaultValue`**     | Provide data to be used for this field's default value. [More](/docs/fields/overview#default-values)                                                                        |
+| **`localized`**        | Enable localization for this field. Requires [localization to be enabled](/docs/configuration/localization) in the Base config.                                             |
+| **`required`**         | Require this field to have a value.                                                                                                                                         |
+| **`admin`**            | Admin-specific configuration. [More details](#admin-options).                                                                                                               |
+| **`custom`**           | Extension point for adding custom data (e.g. for plugins)                                                                                                                   |
+| **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                 |
+| **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)            |
+| **`graphQL`**          | Custom graphQL configuration for the field. [More details](/docs/graphql/overview#field-complexity)                                                                         |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 <Banner type="success">
-  **Tip:**
-  The [Depth](../queries/depth) parameter can be used to automatically populate related documents that are returned by the API.
+  **Tip:** The [Depth](../queries/depth) parameter can be used to automatically
+  populate related documents that are returned by the API.
 </Banner>
 
 ## Admin Options
+
 To the appearance and behavior of the Relationship Field in the [Admin Panel](../admin/overview), you can use the `admin` option:
 
 ```ts
@@ -78,7 +79,8 @@ import type { Field } from 'payload'
 
 export const MyRelationshipField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -86,12 +88,12 @@ export const MyRelationshipField: Field = {
 
 The Relationship Field inherits all of the default options from the base [Field Admin Config](./overview#admin-options), plus the following additional options:
 
-| Property                       | Description                                                                                                                                 |
-| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`isSortable`**               | Set to `true` if you'd like this field to be sortable within the Admin UI using drag and drop (only works when `hasMany` is set to `true`). |
-| **`allowCreate`**              | Set to `false` if you'd like to disable the ability to create new documents from within the relationship field.                             |
-| **`allowEdit`**                | Set to `false` if you'd like to disable the ability to edit documents from within the relationship field.                                   |
-| **`sortOptions`**              | Define a default sorting order for the options within a Relationship field's dropdown. [More](#sort-options)                                |
+| Property          | Description                                                                                                                                 |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`isSortable`**  | Set to `true` if you'd like this field to be sortable within the Admin UI using drag and drop (only works when `hasMany` is set to `true`). |
+| **`allowCreate`** | Set to `false` if you'd like to disable the ability to create new documents from within the relationship field.                             |
+| **`allowEdit`**   | Set to `false` if you'd like to disable the ability to edit documents from within the relationship field.                                   |
+| **`sortOptions`** | Define a default sorting order for the options within a Relationship field's dropdown. [More](#sort-options)                                |
 
 ### Sort Options
 
@@ -141,7 +143,7 @@ The `filterOptions` property can either be a `Where` query, or a function return
 
 | Property      | Description                                                                                                                                                                              |
 | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `blockData`        | The data of the nearest parent block. Will be `undefined` if the field is not within a block or when called on a `Filter` component within the list view.                           |
+| `blockData`   | The data of the nearest parent block. Will be `undefined` if the field is not within a block or when called on a `Filter` component within the list view.                                |
 | `data`        | An object containing the full collection or global document currently being edited. Will be an empty object when called on a `Filter` component within the list view.                    |
 | `id`          | The `id` of the current document being edited. Will be `undefined` during the `create` operation or when called on a `Filter` component within the list view.                            |
 | `relationTo`  | The collection `slug` to filter against, limited to this field's `relationTo` property.                                                                                                  |
@@ -185,10 +187,11 @@ You can learn more about writing queries [here](/docs/queries/overview).
 <Banner type="warning">
   **Note:**
 
-  When a relationship field has both **filterOptions** and a custom
-  **validate** function, the api will not validate **filterOptions**
-  unless you call the default relationship field validation function imported from
-  **payload/shared** in your validate function.
+When a relationship field has both **filterOptions** and a custom
+**validate** function, the api will not validate **filterOptions**
+unless you call the default relationship field validation function imported from
+**payload/shared** in your validate function.
+
 </Banner>
 
 ## Bi-directional relationships
@@ -367,8 +370,9 @@ Since we are referencing multiple collections, the field you are querying on may
 <Banner type="warning">
   **Note:**
 
-  You **cannot** query on a field within a polymorphic relationship as you would with a
-  non-polymorphic relationship.
+You **cannot** query on a field within a polymorphic relationship as you would with a
+non-polymorphic relationship.
+
 </Banner>
 
 ## Custom Components
@@ -382,21 +386,17 @@ import type React from 'react'
 import { RelationshipField } from '@payloadcms/ui'
 import type { RelationshipFieldServerComponent } from 'payload'
 
-export const CustomRelationshipFieldServer: RelationshipFieldServerComponent = ({
-  clientField,
-  path,
-  schemaPath,
-  permissions,
-}) => {
-  return (
-    <RelationshipField
-      field={clientField}
-      path={path}
-      schemaPath={schemaPath}
-      permissions={permissions}
-    />
-  )
-}
+export const CustomRelationshipFieldServer: RelationshipFieldServerComponent =
+  ({ clientField, path, schemaPath, permissions }) => {
+    return (
+      <RelationshipField
+        field={clientField}
+        path={path}
+        schemaPath={schemaPath}
+        permissions={permissions}
+      />
+    )
+  }
 ```
 
 #### Client Component
@@ -407,7 +407,9 @@ import React from 'react'
 import { RelationshipField } from '@payloadcms/ui'
 import type { RelationshipFieldClientComponent } from 'payload'
 
-export const CustomRelationshipFieldClient: RelationshipFieldClientComponent = (props) => {
+export const CustomRelationshipFieldClient: RelationshipFieldClientComponent = (
+  props,
+) => {
   return <RelationshipField {...props} />
 }
 ```
@@ -421,18 +423,16 @@ import React from 'react'
 import { FieldLabel } from '@payloadcms/ui'
 import type { RelationshipFieldLabelServerComponent } from 'payload'
 
-export const CustomRelationshipFieldLabelServer: RelationshipFieldLabelServerComponent = (
-  clientField,
-  path
-) => {
-  return (
-    <FieldLabel
-      label={clientField?.label || clientField?.name}
-      path={path}
-      required={clientField?.required}
-    />
-  )
-}
+export const CustomRelationshipFieldLabelServer: RelationshipFieldLabelServerComponent =
+  (clientField, path) => {
+    return (
+      <FieldLabel
+        label={clientField?.label || clientField?.name}
+        path={path}
+        required={clientField?.required}
+      />
+    )
+  }
 ```
 
 #### Client Component
@@ -443,16 +443,14 @@ import React from 'react'
 import { FieldLabel } from '@payloadcms/ui'
 import type { RelationshipFieldLabelClientComponent } from 'payload'
 
-export const CustomRelationshipFieldLabelClient: RelationshipFieldLabelClientComponent = ({
-  field,
-  path,
-}) => {
-  return (
-    <FieldLabel
-      label={field?.label || field?.name}
-      path={path}
-      required={field?.required}
-    />
-  )
-}
+export const CustomRelationshipFieldLabelClient: RelationshipFieldLabelClientComponent =
+  ({ field, path }) => {
+    return (
+      <FieldLabel
+        label={field?.label || field?.name}
+        path={path}
+        required={field?.required}
+      />
+    )
+  }
 ```

docs/fields/rich-text.mdx

@@ -12,29 +12,34 @@ Consistent with Payload's goal of making you learn as little of Payload as possi
 
 Instead, you can invest your time and effort into learning the underlying open-source tools that will allow you to apply your learnings elsewhere as well.
 
-<LightDarkImage alt="Shows a Rich Text field in the Payload Admin Panel" caption="Admin Panel screenshot of a Rich Text field" srcDark="https://payloadcms.com/images/docs/fields/richtext-dark.png" srcLight="https://payloadcms.com/images/docs/fields/richtext.png"/>
+<LightDarkImage
+  alt="Shows a Rich Text field in the Payload Admin Panel"
+  caption="Admin Panel screenshot of a Rich Text field"
+  srcDark="https://payloadcms.com/images/docs/fields/richtext-dark.png"
+  srcLight="https://payloadcms.com/images/docs/fields/richtext.png"
+/>
 
 ## Config Options
 
-|   Option                   |   Description                                                                                                                                                        |
-| --- | --- |
-|   **`name`** *            |   To be used as the property name when stored and retrieved from the database. [More](./overview#field-names)                                             |
-|   **`label`**              |   Text used as a field label in the Admin Panel or an object with keys for each language.                                                                            |
-|   **`validate`**           |   Provide a custom validation function that will be executed on both the Admin Panel and the backend. [More](./overview#validation)                       |
-|   **`saveToJWT`**          |   If this field is top-level and nested in a config supporting [Authentication](../authentication/overview), include its data in the user JWT.                    |
-|   **`hooks`**              |   Provide Field Hooks to control logic for this field. [More details](../hooks/fields).                                                                              |
-|   **`access`**             |   Provide Field Access Control to denote what users can see and do with this field's data. [More details](../access-control/fields).                                 |
-|   **`hidden`**             |   Restrict this field's visibility from all APIs entirely. Will still be saved to the database, but will not appear in any API or the Admin Panel.                   |
-|   **`defaultValue`**       |   Provide data to be used for this field's default value. [More](./overview#default-values)                                                               |
-|   **`localized`**          |   Enable localization for this field. Requires [localization to be enabled](../configuration/localization) in the Base config.                                    |
-|   **`required`**           |   Require this field to have a value.                                                                                                                                |
-|   **`admin`**              |   Admin-specific configuration. [More details](#admin-options).                                                                                                      |
-|   **`editor`**             |   Customize or override the rich text editor. [More details](../rich-text/overview).                                                                                 |
-|   **`custom`**             |   Extension point for adding custom data (e.g. for plugins)                                                                                                          |
-|   **`typescriptSchema`**   |   Override field type generation with providing a JSON schema                                                                                                        |
-|   **`virtual`**            |   Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)   |
+| Option                 | Description                                                                                                                                                      |
+| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](./overview#field-names)                                                      |
+| **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                          |
+| **`validate`**         | Provide a custom validation function that will be executed on both the Admin Panel and the backend. [More](./overview#validation)                                |
+| **`saveToJWT`**        | If this field is top-level and nested in a config supporting [Authentication](../authentication/overview), include its data in the user JWT.                     |
+| **`hooks`**            | Provide Field Hooks to control logic for this field. [More details](../hooks/fields).                                                                            |
+| **`access`**           | Provide Field Access Control to denote what users can see and do with this field's data. [More details](../access-control/fields).                               |
+| **`hidden`**           | Restrict this field's visibility from all APIs entirely. Will still be saved to the database, but will not appear in any API or the Admin Panel.                 |
+| **`defaultValue`**     | Provide data to be used for this field's default value. [More](./overview#default-values)                                                                        |
+| **`localized`**        | Enable localization for this field. Requires [localization to be enabled](../configuration/localization) in the Base config.                                     |
+| **`required`**         | Require this field to have a value.                                                                                                                              |
+| **`admin`**            | Admin-specific configuration. [More details](#admin-options).                                                                                                    |
+| **`editor`**           | Customize or override the rich text editor. [More details](../rich-text/overview).                                                                               |
+| **`custom`**           | Extension point for adding custom data (e.g. for plugins)                                                                                                        |
+| **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                      |
+| **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges) |
 
-** An asterisk denotes that a property is required.*
+\*_ An asterisk denotes that a property is required._
 
 ## Admin Options
 
@@ -45,7 +50,8 @@ import type { Field } from 'payload'
 
 export const MyRichTextField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }

docs/fields/row.mdx

@@ -26,20 +26,20 @@ export const MyRowField: Field = {
   type: 'row',
   fields: [
     // ...
-  ]
+  ],
   // highlight-end
 }
 ```
 
 ## Config Options
 
-| Option          | Description                                                                                                                                                                |
-| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`fields`** * | Array of field types to nest within this Row.                                                                                                                              |
+| Option          | Description                                                                                                               |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------- |
+| **`fields`** \* | Array of field types to nest within this Row.                                                                             |
 | **`admin`**     | Admin-specific configuration excluding `description`, `readOnly`, and `hidden`. [More details](./overview#admin-options). |
-| **`custom`**    | Extension point for adding custom data (e.g. for plugins)                                                                                                                  |
+| **`custom`**    | Extension point for adding custom data (e.g. for plugins)                                                                 |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Example
 

docs/fields/select.mdx

@@ -26,45 +26,45 @@ export const MySelectField: Field = {
   type: 'select',
   options: [
     // ...
-  ]
+  ],
   // highlight-end
 }
 ```
 
 ## Config Options
 
-| Option                 | Description                                                                                                                                                                                  |
-| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                                       |
-| **`options`** *       | Array of options to allow the field to store. Can either be an array of strings, or an array of objects containing a `label` string and a `value` string.                                    |
-| **`hasMany`**          | Boolean when, if set to `true`, allows this field to have many selections instead of only one.                                                                                               |
-| **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                                      |
-| **`unique`**           | Enforce that each entry in the Collection has a unique value for this field.                                                                                                                 |
-| **`validate`**         | Provide a custom validation function that will be executed on both the Admin Panel and the backend. [More](/docs/fields/overview#validation)                                                 |
-| **`index`**            | Build an [index](/docs/database/overview) for this field to produce faster queries. Set this field to `true` if your users will perform queries on this field's data often.                  |
-| **`saveToJWT`**        | If this field is top-level and nested in a config supporting [Authentication](/docs/authentication/overview), include its data in the user JWT.                                              |
-| **`hooks`**            | Provide Field Hooks to control logic for this field. [More details](../hooks/fields).                                                                                                        |
-| **`access`**           | Provide Field Access Control to denote what users can see and do with this field's data. [More details](../access-control/fields).                                                           |
-| **`hidden`**           | Restrict this field's visibility from all APIs entirely. Will still be saved to the database, but will not appear in any API or the Admin Panel.                                             |
-| **`defaultValue`**     | Provide data to be used for this field's default value. [More](/docs/fields/overview#default-values)                                                                                         |
-| **`localized`**        | Enable localization for this field. Requires [localization to be enabled](/docs/configuration/localization) in the Base config.                                                              |
-| **`required`**         | Require this field to have a value.                                                                                                                                                          |
-| **`admin`**            | Admin-specific configuration. See the [default field admin config](/docs/fields/overview#admin-options) for more details.                                                                    |
-| **`custom`**           | Extension point for adding custom data (e.g. for plugins)                                                                                                                                    |
-| **`enumName`**         | Custom enum name for this field when using SQL Database Adapter ([Postgres](/docs/database/postgres)). Auto-generated from name if not defined.                                              |
-| **`dbName`**           | Custom table name (if `hasMany` set to `true`) for this field when using SQL Database Adapter ([Postgres](/docs/database/postgres)). Auto-generated from name if not defined.                |
-| **`interfaceName`**    | Create a top level, reusable [Typescript interface](/docs/typescript/generating-types#custom-field-interfaces) & [GraphQL type](/docs/graphql/graphql-schema#custom-field-schemas).                                                                                                |
-| **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                                  |
-| **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)                             |
+| Option                 | Description                                                                                                                                                                         |
+| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                              |
+| **`options`** \*       | Array of options to allow the field to store. Can either be an array of strings, or an array of objects containing a `label` string and a `value` string.                           |
+| **`hasMany`**          | Boolean when, if set to `true`, allows this field to have many selections instead of only one.                                                                                      |
+| **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                             |
+| **`unique`**           | Enforce that each entry in the Collection has a unique value for this field.                                                                                                        |
+| **`validate`**         | Provide a custom validation function that will be executed on both the Admin Panel and the backend. [More](/docs/fields/overview#validation)                                        |
+| **`index`**            | Build an [index](/docs/database/overview) for this field to produce faster queries. Set this field to `true` if your users will perform queries on this field's data often.         |
+| **`saveToJWT`**        | If this field is top-level and nested in a config supporting [Authentication](/docs/authentication/overview), include its data in the user JWT.                                     |
+| **`hooks`**            | Provide Field Hooks to control logic for this field. [More details](../hooks/fields).                                                                                               |
+| **`access`**           | Provide Field Access Control to denote what users can see and do with this field's data. [More details](../access-control/fields).                                                  |
+| **`hidden`**           | Restrict this field's visibility from all APIs entirely. Will still be saved to the database, but will not appear in any API or the Admin Panel.                                    |
+| **`defaultValue`**     | Provide data to be used for this field's default value. [More](/docs/fields/overview#default-values)                                                                                |
+| **`localized`**        | Enable localization for this field. Requires [localization to be enabled](/docs/configuration/localization) in the Base config.                                                     |
+| **`required`**         | Require this field to have a value.                                                                                                                                                 |
+| **`admin`**            | Admin-specific configuration. See the [default field admin config](/docs/fields/overview#admin-options) for more details.                                                           |
+| **`custom`**           | Extension point for adding custom data (e.g. for plugins)                                                                                                                           |
+| **`enumName`**         | Custom enum name for this field when using SQL Database Adapter ([Postgres](/docs/database/postgres)). Auto-generated from name if not defined.                                     |
+| **`dbName`**           | Custom table name (if `hasMany` set to `true`) for this field when using SQL Database Adapter ([Postgres](/docs/database/postgres)). Auto-generated from name if not defined.       |
+| **`interfaceName`**    | Create a top level, reusable [Typescript interface](/docs/typescript/generating-types#custom-field-interfaces) & [GraphQL type](/docs/graphql/graphql-schema#custom-field-schemas). |
+| **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                         |
+| **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)                    |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 <Banner type="warning">
-  **Important:**
-  Option values should be strings that do not contain hyphens or special characters due to GraphQL
-  enumeration naming constraints. Underscores are allowed. If you determine you need your option
-  values to be non-strings or contain special characters, they will be formatted accordingly before
-  being used as a GraphQL enum.
+  **Important:** Option values should be strings that do not contain hyphens or
+  special characters due to GraphQL enumeration naming constraints. Underscores
+  are allowed. If you determine you need your option values to be non-strings or
+  contain special characters, they will be formatted accordingly before being
+  used as a GraphQL enum.
 </Banner>
 
 ## Admin Options
@@ -76,7 +76,8 @@ import type { Field } from 'payload'
 
 export const MySelectField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -84,10 +85,10 @@ export const MySelectField: Field = {
 
 The Select Field inherits all of the default options from the base [Field Admin Config](./overview#admin-options), plus the following additional options:
 
-| Property                       | Description                                                                                                                              |
-| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
-| **`isClearable`**              | Set to `true` if you'd like this field to be clearable within the Admin UI.                                                              |
-| **`isSortable`**               | Set to `true` if you'd like this field to be sortable within the Admin UI using drag and drop. (Only works when `hasMany` is set to `true`) |
+| Property          | Description                                                                                                                                 |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`isClearable`** | Set to `true` if you'd like this field to be clearable within the Admin UI.                                                                 |
+| **`isSortable`**  | Set to `true` if you'd like this field to be sortable within the Admin UI using drag and drop. (Only works when `hasMany` is set to `true`) |
 
 ## Example
 

docs/fields/tabs.mdx

@@ -26,18 +26,18 @@ export const MyTabsField: Field = {
   type: 'tabs',
   tabs: [
     // ...
-  ]
+  ],
   // highlight-end
 }
 ```
 
 ## Config Options
 
-| Option        | Description                                                                                                              |
-| ------------- | ------------------------------------------------------------------------------------------------------------------------ |
-| **`tabs`** * | Array of tabs to render within this Tabs field.                                                                          |
+| Option        | Description                                                             |
+| ------------- | ----------------------------------------------------------------------- |
+| **`tabs`** \* | Array of tabs to render within this Tabs field.                         |
 | **`admin`**   | Admin-specific configuration. [More details](./overview#admin-options). |
-| **`custom`**  | Extension point for adding custom data (e.g. for plugins)                                                                |
+| **`custom`**  | Extension point for adding custom data (e.g. for plugins)               |
 
 ### Tab-specific Config
 
@@ -47,12 +47,12 @@ Each tab must have either a `name` or `label` and the required `fields` array. Y
 | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | **`name`**          | Groups field data into an object when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                                                      |
 | **`label`**         | The label to render on the tab itself. Required when name is undefined, defaults to name converted to words.                                                                                                 |
-| **`fields`** *     | The fields to render within this tab.                                                                                                                                                                        |
+| **`fields`** \*     | The fields to render within this tab.                                                                                                                                                                        |
 | **`description`**   | Optionally render a description within this tab to describe the contents of the tab itself.                                                                                                                  |
 | **`interfaceName`** | Create a top level, reusable [Typescript interface](/docs/typescript/generating-types#custom-field-interfaces) & [GraphQL type](/docs/graphql/graphql-schema#custom-field-schemas). (`name` must be present) |
 | **`virtual`**       | Provide `true` to disable field in the database (`name` must be present). See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)                    |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Example
 

docs/fields/text.mdx

@@ -30,7 +30,7 @@ export const MyTextField: Field = {
 
 | Option                 | Description                                                                                                                                                                 |
 | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
 | **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                     |
 | **`unique`**           | Enforce that each entry in the Collection has a unique value for this field.                                                                                                |
 | **`minLength`**        | Used by the default validation function to ensure values are of a minimum character length.                                                                                 |
@@ -52,7 +52,7 @@ export const MyTextField: Field = {
 | **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                 |
 | **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)            |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Admin Options
 
@@ -63,7 +63,8 @@ import type { Field } from 'payload'
 
 export const MyTextField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -71,11 +72,11 @@ export const MyTextField: Field = {
 
 The Text Field inherits all of the default options from the base [Field Admin Config](./overview#admin-options), plus the following additional options:
 
-| Option         | Description                                                                                                      |
-| -------------- | ---------------------------------------------------------------------------------------------------------------- |
-| **`placeholder`** | Set this property to define a placeholder string in the text input.                                              |
-| **`autoComplete`** | Set this property to a string that will be used for browser autocomplete.                                        |
-| **`rtl`**        | Override the default text direction of the Admin Panel for this field. Set to `true` to force right-to-left text direction. |
+| Option             | Description                                                                                                                 |
+| ------------------ | --------------------------------------------------------------------------------------------------------------------------- |
+| **`placeholder`**  | Set this property to define a placeholder string in the text input.                                                         |
+| **`autoComplete`** | Set this property to a string that will be used for browser autocomplete.                                                   |
+| **`rtl`**          | Override the default text direction of the Admin Panel for this field. Set to `true` to force right-to-left text direction. |
 
 ## Example
 
@@ -114,7 +115,12 @@ export const CustomTextFieldServer: TextFieldServerComponent = ({
   permissions,
 }) => {
   return (
-    <TextField field={clientField} path={path} schemaPath={schemaPath} permissions={permissions} />
+    <TextField
+      field={clientField}
+      path={path}
+      schemaPath={schemaPath}
+      permissions={permissions}
+    />
   )
 }
 ```

docs/fields/textarea.mdx

@@ -30,7 +30,7 @@ export const MyTextareaField: Field = {
 
 | Option                 | Description                                                                                                                                                                 |
 | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
 | **`label`**            | Text used as a field label in the Admin Panel or an object with keys for each language.                                                                                     |
 | **`unique`**           | Enforce that each entry in the Collection has a unique value for this field.                                                                                                |
 | **`minLength`**        | Used by the default validation function to ensure values are of a minimum character length.                                                                                 |
@@ -49,7 +49,7 @@ export const MyTextareaField: Field = {
 | **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                 |
 | **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)            |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Admin Options
 
@@ -60,7 +60,8 @@ import type { Field } from 'payload'
 
 export const MyTextareaField: Field = {
   // ...
-  admin: { // highlight-line
+  admin: {
+    // highlight-line
     // ...
   },
 }
@@ -130,7 +131,9 @@ import React from 'react'
 import { TextareaField } from '@payloadcms/ui'
 import type { TextareaFieldClientComponent } from 'payload'
 
-export const CustomTextareaFieldClient: TextareaFieldClientComponent = (props) => {
+export const CustomTextareaFieldClient: TextareaFieldClientComponent = (
+  props,
+) => {
   return <TextareaField {...props} />
 }
 ```
@@ -144,18 +147,16 @@ import React from 'react'
 import { FieldLabel } from '@payloadcms/ui'
 import type { TextareaFieldLabelServerComponent } from 'payload'
 
-export const CustomTextareaFieldLabelServer: TextareaFieldLabelServerComponent = ({
-  clientField,
-  path,
-}) => {
-  return (
-    <FieldLabel
-      label={clientField?.label || clientField?.name}
-      path={path}
-      required={clientField?.required}
-    />
-  )
-}
+export const CustomTextareaFieldLabelServer: TextareaFieldLabelServerComponent =
+  ({ clientField, path }) => {
+    return (
+      <FieldLabel
+        label={clientField?.label || clientField?.name}
+        path={path}
+        required={clientField?.required}
+      />
+    )
+  }
 ```
 
 #### Client Component
@@ -166,16 +167,14 @@ import React from 'react'
 import { FieldLabel } from '@payloadcms/ui'
 import type { TextareaFieldLabelClientComponent } from 'payload'
 
-export const CustomTextareaFieldLabelClient: TextareaFieldLabelClientComponent = ({
-  field,
-  path,
-}) => {
-  return (
-    <FieldLabel
-      label={field?.label || field?.name}
-      path={path}
-      required={field?.required}
-    />
-  )
-}
+export const CustomTextareaFieldLabelClient: TextareaFieldLabelClientComponent =
+  ({ field, path }) => {
+    return (
+      <FieldLabel
+        label={field?.label || field?.name}
+        path={path}
+        required={field?.required}
+      />
+    )
+  }
 ```

docs/fields/ui.mdx

@@ -28,16 +28,16 @@ export const MyUIField: Field = {
 
 ## Config Options
 
-| Option                          | Description                                                                                                         |
-| ------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
-| **`name`** *                    | A unique identifier for this field.                                                                                 |
-| **`label`**                     | Human-readable label for this UI field.                                                                             |
-| **`admin.components.Field`** *  | React component to be rendered for this field within the Edit View. [More](./overview#field)                   |
-| **`admin.components.Cell`**     | React component to be rendered as a Cell within collection List views. [More](./overview#cell)                 |
-| **`admin.disableListColumn`**   | Set `disableListColumn` to `true` to prevent the UI field from appearing in the list view column selector.          |
-| **`custom`**                    | Extension point for adding custom data (e.g. for plugins)                                                           |
+| Option                          | Description                                                                                                |
+| ------------------------------- | ---------------------------------------------------------------------------------------------------------- |
+| **`name`** \*                   | A unique identifier for this field.                                                                        |
+| **`label`**                     | Human-readable label for this UI field.                                                                    |
+| **`admin.components.Field`** \* | React component to be rendered for this field within the Edit View. [More](./overview#field)               |
+| **`admin.components.Cell`**     | React component to be rendered as a Cell within collection List views. [More](./overview#cell)             |
+| **`admin.disableListColumn`**   | Set `disableListColumn` to `true` to prevent the UI field from appearing in the list view column selector. |
+| **`custom`**                    | Extension point for adding custom data (e.g. for plugins)                                                  |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Example
 

docs/fields/upload.mdx

@@ -16,10 +16,10 @@ Upload fields are useful for a variety of use cases, such as:
 - To give a layout building block the ability to feature a background image
 
 <LightDarkImage
-srcLight="https://payloadcms.com/images/docs/fields/upload.png"
-srcDark="https://payloadcms.com/images/docs/fields/upload-dark.png"
-alt="Shows an upload field in the Payload Admin Panel"
-caption="Admin Panel screenshot of an Upload field"
+  srcLight="https://payloadcms.com/images/docs/fields/upload.png"
+  srcDark="https://payloadcms.com/images/docs/fields/upload-dark.png"
+  alt="Shows an upload field in the Payload Admin Panel"
+  caption="Admin Panel screenshot of an Upload field"
 />
 
 To create an Upload Field, set the `type` to `upload` in your [Field Config](./overview):
@@ -37,16 +37,17 @@ export const MyUploadField: Field = {
 ```
 
 <Banner type="warning">
-  **Important:**
-  To use the Upload Field, you must have a [Collection](../configuration/collections) configured to allow [Uploads](../upload/overview).
+  **Important:** To use the Upload Field, you must have a
+  [Collection](../configuration/collections) configured to allow
+  [Uploads](../upload/overview).
 </Banner>
 
 ## Config Options
 
 | Option                 | Description                                                                                                                                                                 |
-|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **`name`** *          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
-| **`relationTo`** *    | Provide a single collection `slug` to allow this field to accept a relation to. **Note: the related collection must be configured to support Uploads.**        |
+| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`name`** \*          | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                      |
+| **`relationTo`** \*    | Provide a single collection `slug` to allow this field to accept a relation to. **Note: the related collection must be configured to support Uploads.**                     |
 | **`filterOptions`**    | A query to filter which options appear in the UI and validate against. [More](#filtering-upload-options).                                                                   |
 | **`hasMany`**          | Boolean which, if set to true, allows this field to have many relations instead of only one.                                                                                |
 | **`minRows`**          | A number for the fewest allowed items during validation when a value is present. Used with hasMany.                                                                         |
@@ -64,13 +65,13 @@ export const MyUploadField: Field = {
 | **`displayPreview`**   | Enable displaying preview of the uploaded file. Overrides related Collection's `displayPreview` option. [More](/docs/upload/overview#collection-upload-options).            |
 | **`localized`**        | Enable localization for this field. Requires [localization to be enabled](/docs/configuration/localization) in the Base config.                                             |
 | **`required`**         | Require this field to have a value.                                                                                                                                         |
-| **`admin`**            | Admin-specific configuration. [Admin Options](./overview#admin-options).                                                                                               |
+| **`admin`**            | Admin-specific configuration. [Admin Options](./overview#admin-options).                                                                                                    |
 | **`custom`**           | Extension point for adding custom data (e.g. for plugins)                                                                                                                   |
 | **`typescriptSchema`** | Override field type generation with providing a JSON schema                                                                                                                 |
 | **`virtual`**          | Provide `true` to disable field in the database. See [Virtual Fields](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges)            |
 | **`graphQL`**          | Custom graphQL configuration for the field. [More details](/docs/graphql/overview#field-complexity)                                                                         |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 ## Example
 
@@ -102,7 +103,7 @@ prevent all, or a `Where` query. When using a function, it will be
 called with an argument object with the following properties:
 
 | Property      | Description                                                                                           |
-|---------------|-------------------------------------------------------------------------------------------------------|
+| ------------- | ----------------------------------------------------------------------------------------------------- |
 | `relationTo`  | The collection `slug` to filter against, limited to this field's `relationTo` property                |
 | `data`        | An object containing the full collection or global document currently being edited                    |
 | `siblingData` | An object containing document data that is scoped to only fields within the same parent of this field |
@@ -128,10 +129,11 @@ You can learn more about writing queries [here](/docs/queries/overview).
 <Banner type="warning">
   **Note:**
 
-  When an upload field has both **filterOptions** and a custom
-  **validate** function, the api will not validate **filterOptions**
-  unless you call the default upload field validation function imported from
-  **payload/shared** in your validate function.
+When an upload field has both **filterOptions** and a custom
+**validate** function, the api will not validate **filterOptions**
+unless you call the default upload field validation function imported from
+**payload/shared** in your validate function.
+
 </Banner>
 
 ## Bi-directional relationships

docs/getting-started/concepts.mdx

@@ -53,8 +53,8 @@ Everything Payload does (create, read, update, delete, login, logout, etc.) is e
 - [GraphQL](#graphql-api) - A full GraphQL API with a GraphQL Playground
 
 <Banner type="success">
-  **Note:**
-  All of these APIs share the exact same query language. [More details](../queries/overview).
+  **Note:** All of these APIs share the exact same query language. [More
+  details](../queries/overview).
 </Banner>
 
 ### Local API
@@ -127,8 +127,9 @@ You can use any GraphQL client with Payload's GraphQL endpoint. Here are a few p
 Payload is abstracted into a set of dedicated packages to keep the core `payload` package as lightweight as possible. This allows you to only install the parts of Payload based on your unique project requirements.
 
 <Banner type="warning">
-  **Important:**
-  Version numbers of all official Payload packages are always published in sync. You should make sure that you always use matching versions for all official Payload packages.
+  **Important:** Version numbers of all official Payload packages are always
+  published in sync. You should make sure that you always use matching versions
+  for all official Payload packages.
 </Banner>
 
 `payload`
@@ -166,6 +167,6 @@ You can choose which Database Adapter you'd like to use for your project, and no
 Payload's Rich Text functionality is abstracted into separate packages and if you want to enable Rich Text in your project, you'll need to install one of these packages. We recommend Lexical for all new projects, and this is where Payload will focus its efforts on from this point, but Slate is still supported if you have already built with it.
 
 <Banner type="info">
-  **Note:**
-  Rich Text is entirely optional and you may not need it for your project.
+  **Note:** Rich Text is entirely optional and you may not need it for your
+  project.
 </Banner>

docs/getting-started/installation.mdx

@@ -15,8 +15,8 @@ Payload requires the following software:
 - Any [compatible database](/docs/database/overview) (MongoDB, Postgres or SQLite)
 
 <Banner type="warning">
-  **Important:**
-  Before proceeding any further, please ensure that you have the above requirements met.
+  **Important:** Before proceeding any further, please ensure that you have the
+  above requirements met.
 </Banner>
 
 ## Quickstart with create-payload-app
@@ -48,8 +48,8 @@ pnpm i payload @payloadcms/next @payloadcms/richtext-lexical sharp graphql
 ```
 
 <Banner type="warning">
-  **Note:**
-  Swap out `pnpm` for your package manager. If you are using npm, you might need to install using legacy peer deps: `npm i --legacy-peer-deps`.
+  **Note:** Swap out `pnpm` for your package manager. If you are using npm, you
+  might need to install using legacy peer deps: `npm i --legacy-peer-deps`.
 </Banner>
 
 Next, install a [Database Adapter](/docs/database/overview). Payload requires a Database Adapter to establish a database connection. Payload works with all types of databases, but the most common are MongoDB and Postgres.
@@ -57,23 +57,25 @@ Next, install a [Database Adapter](/docs/database/overview). Payload requires a
 To install a Database Adapter, you can run **one** of the following commands:
 
 - To install the [MongoDB Adapter](../database/mongodb), run:
-    ```bash
-    pnpm i @payloadcms/db-mongodb
-    ```
+
+  ```bash
+  pnpm i @payloadcms/db-mongodb
+  ```
 
 - To install the [Postgres Adapter](../database/postgres), run:
-    ```bash
-    pnpm i @payloadcms/db-postgres
-    ```
+  ```bash
+  pnpm i @payloadcms/db-postgres
+  ```
 
 <Banner type="success">
-  **Note:**
-  New [Database Adapters](/docs/database/overview) are becoming available every day. Check the docs for the most up-to-date list of what's available.
+  **Note:** New [Database Adapters](/docs/database/overview) are becoming
+  available every day. Check the docs for the most up-to-date list of what's
+  available.
 </Banner>
 
 #### 2. Copy Payload files into your Next.js app folder
 
-Payload installs directly in your Next.js `/app` folder, and you'll need to place some files into that folder for Payload to run. You can copy these files from the [Blank Template](https://github.com/payloadcms/payload/tree/main/templates/blank/src/app/(payload)) on GitHub. Once you have the required Payload files in place in your `/app` folder, you should have something like this:
+Payload installs directly in your Next.js `/app` folder, and you'll need to place some files into that folder for Payload to run. You can copy these files from the [Blank Template](<https://github.com/payloadcms/payload/tree/main/templates/blank/src/app/(payload)>) on GitHub. Once you have the required Payload files in place in your `/app` folder, you should have something like this:
 
 ```plaintext
 app/
@@ -86,7 +88,10 @@ app/
 _For an exact reference of the `(payload)` directory, see [Project Structure](../admin/overview#project-structure)._
 
 <Banner type="warning">
-  You may need to copy all of your existing frontend files, including your existing root layout, into its own newly created [Route Group](https://nextjs.org/docs/app/building-your-application/routing/route-groups), i.e. `(my-app)`.
+  You may need to copy all of your existing frontend files, including your
+  existing root layout, into its own newly created [Route
+  Group](https://nextjs.org/docs/app/building-your-application/routing/route-groups),
+  i.e. `(my-app)`.
 </Banner>
 
 The files that Payload needs to have in your `/app` folder do not regenerate, and will never change. Once you slot them in, you never have to revisit them. They are not meant to be edited and simply import Payload dependencies from `@payloadcms/next` for the REST / GraphQL API and Admin Panel.
@@ -106,8 +111,8 @@ import { withPayload } from '@payloadcms/next/withPayload'
 const nextConfig = {
   // Your Next.js config here
   experimental: {
-    reactCompiler: false
-  }
+    reactCompiler: false,
+  },
 }
 
 // Make sure you wrap your `nextConfig`
@@ -116,8 +121,8 @@ export default withPayload(nextConfig) // highlight-line
 ```
 
 <Banner type="warning">
-  **Important:**
-  Payload is a fully ESM project, and that means the `withPayload` function is an ECMAScript module.
+  **Important:** Payload is a fully ESM project, and that means the
+  `withPayload` function is an ECMAScript module.
 </Banner>
 
 To import the Payload Plugin, you need to make sure your `next.config` file is set up to use ESM.
@@ -171,11 +176,9 @@ Once you have a Payload Config, update your `tsconfig` to include a `path` that
 {
   "compilerOptions": {
     "paths": {
-      "@payload-config": [
-        "./payload.config.ts"
-      ]
+      "@payload-config": ["./payload.config.ts"]
     }
-  },
+  }
 }
 ```
 

docs/getting-started/what-is-payload.mdx

@@ -53,7 +53,10 @@ Payload has restored a little love back into the dev / marketer equation with fe
 If you're building a website and your frontend is on Next.js, then Payload is a no-brainer.
 
 <Banner type="success">
-  Instead of going out and signing up for a SaaS vendor that makes it so you have to manage two completely separate concerns, with little to no native connection back and forth, just install Payload in your existing Next.js repo and instantly get a full CMS.
+  Instead of going out and signing up for a SaaS vendor that makes it so you
+  have to manage two completely separate concerns, with little to no native
+  connection back and forth, just install Payload in your existing Next.js repo
+  and instantly get a full CMS.
 </Banner>
 
 Get started with Payload as a CMS using our official Website template:

docs/graphql/extending.mdx

@@ -70,7 +70,7 @@ export default buildConfig({
 
 ## Resolver function
 
-In your resolver, make sure you set `depth: 0` if you're returning data directly from the local API so that GraphQL can correctly resolve queries to nested values such as relationship data.
+In your resolver, make sure you set `depth: 0` if you're returning data directly from the Local API so that GraphQL can correctly resolve queries to nested values such as relationship data.
 
 Your function will receive four arguments you can make use of:
 
@@ -115,10 +115,10 @@ import { GraphQL } from '@payloadcms/graphql/types'
 ```
 
 <Banner type="warning">
-  For queries, mutations and handlers make sure you use the `GraphQL` and `payload` instances provided via arguments.
+  For queries, mutations and handlers make sure you use the `GraphQL` and
+  `payload` instances provided via arguments.
 </Banner>
 
-
 **`buildPaginatedListType`**
 
 This is a utility function that allows you to build a new GraphQL type for a paginated result similar to the Payload's generated schema.
@@ -134,7 +134,10 @@ export const getMyPosts = (GraphQL, payload) => {
     args: {},
     resolve: Resolver,
     // The name of your new type has to be unique
-    type: buildPaginatedListType('AuthorPosts', payload.collections['posts'].graphQL?.type),
+    type: buildPaginatedListType(
+      'AuthorPosts',
+      payload.collections['posts'].graphQL?.type,
+    ),
   }
 }
 ```

docs/graphql/graphql-schema.mdx

@@ -60,14 +60,15 @@ type Collection1 {
 }
 ```
 
-The above example outputs all your definitions to a file relative from your payload config as `./graphql/schema.graphql`. By default, the file will be output to your current working directory as `schema.graphql`.
+The above example outputs all your definitions to a file relative from your Payload config as `./graphql/schema.graphql`. By default, the file will be output to your current working directory as `schema.graphql`.
 
 ### Adding an npm script
 
 <Banner type="warning">
   **Important**
 
-  Payload needs to be able to find your config to generate your GraphQL schema.
+Payload needs to be able to find your config to generate your GraphQL schema.
+
 </Banner>
 
 Payload will automatically try and locate your config, but might not always be able to find it. For example, if you are working in a `/src` directory or similar, you need to tell Payload where to find your config manually by using an environment variable.

docs/graphql/overview.mdx

@@ -43,17 +43,17 @@ export const PublicUser: CollectionConfig = {
 
 **Payload will automatically open up the following queries:**
 
-| Query Name          | Operation           |
-| ------------------- | ------------------- |
-| `PublicUser`        | `findByID`          |
-| `PublicUsers`       | `find`              |
-| `countPublicUsers`  | `count`             |
-| `mePublicUser`      | `me` auth operation |
+| Query Name         | Operation           |
+| ------------------ | ------------------- |
+| `PublicUser`       | `findByID`          |
+| `PublicUsers`      | `find`              |
+| `countPublicUsers` | `count`             |
+| `mePublicUser`     | `me` auth operation |
 
 **And the following mutations:**
 
-| Query Name                     | Operation                       |
-| ------------------------------ | ------------------------------- |
+| Query Name                 | Operation                       |
+| -------------------------- | ------------------------------- |
 | `createPublicUser`         | `create`                        |
 | `updatePublicUser`         | `update`                        |
 | `deletePublicUser`         | `delete`                        |
@@ -82,14 +82,14 @@ const Header: GlobalConfig = {
 
 **Payload will open the following query:**
 
-| Query Name   | Operation |
-| ------------ | --------- |
-| `Header` | `findOne` |
+| Query Name | Operation |
+| ---------- | --------- |
+| `Header`   | `findOne` |
 
 **And the following mutation:**
 
-| Query Name         | Operation |
-| ------------------ | --------- |
+| Query Name     | Operation |
+| -------------- | --------- |
 | `updateHeader` | `update`  |
 
 ## Preferences
@@ -98,14 +98,14 @@ User [preferences](../admin/preferences) for the [Admin Panel](../admin/overview
 
 **Payload will open the following query:**
 
-| Query Name       | Operation |
-| ---------------- | --------- |
+| Query Name   | Operation |
+| ------------ | --------- |
 | `Preference` | `findOne` |
 
 **And the following mutations:**
 
-| Query Name             | Operation |
-| ---------------------- | --------- |
+| Query Name         | Operation |
+| ------------------ | --------- |
 | `updatePreference` | `update`  |
 | `deletePreference` | `delete`  |
 
@@ -118,11 +118,12 @@ You can even log in using the `login[collection-singular-label-here]` mutation t
 <Banner type="success">
   **Tip:**
 
-  To see more regarding how the above queries and mutations are used, visit your GraphQL playground
-  (by default at
-  [`${SERVER_URL}/api/graphql-playground`](http://localhost:3000/api/graphql-playground))
-  while your server is running. There, you can use the "Schema" and "Docs" buttons on the right to
-  see a ton of detail about how GraphQL operates within Payload.
+To see more regarding how the above queries and mutations are used, visit your GraphQL playground
+(by default at
+[`${SERVER_URL}/api/graphql-playground`](http://localhost:3000/api/graphql-playground))
+while your server is running. There, you can use the "Schema" and "Docs" buttons on the right to
+see a ton of detail about how GraphQL operates within Payload.
+
 </Banner>
 
 ## Custom Validation Rules
@@ -136,9 +137,7 @@ import { buildConfig } from 'payload'
 export default buildConfig({
   // ...
   graphQL: {
-    validationRules: (args) => [
-      NoProductionIntrospection
-    ]
+    validationRules: (args) => [NoProductionIntrospection],
   },
   // ...
 })
@@ -150,12 +149,12 @@ const NoProductionIntrospection: GraphQL.ValidationRule = (context) => ({
         context.reportError(
           new GraphQL.GraphQLError(
             'GraphQL introspection is not allowed, but the query contained __schema or __type',
-            { nodes: [node] }
-          )
-        );
+            { nodes: [node] },
+          ),
+        )
       }
     }
-  }
+  },
 })
 ```
 
@@ -174,6 +173,6 @@ const fieldWithComplexity = {
   relationship: 'authors',
   graphQL: {
     complexity: 100, // highlight-line
-  }
+  },
 }
 ```

docs/hooks/collections.mdx

@@ -11,19 +11,20 @@ Collection Hooks are [Hooks](./overview) that run on Documents within a specific
 To add Hooks to a Collection, use the `hooks` property in your [Collection Config](../configuration/collections):
 
 ```ts
-import type { CollectionConfig } from 'payload';
+import type { CollectionConfig } from 'payload'
 
 export const CollectionWithHooks: CollectionConfig = {
   // ...
-  hooks: { // highlight-line
+  hooks: {
+    // highlight-line
     // ...
   },
 }
 ```
 
 <Banner type="info">
-  **Tip:**
-  You can also set hooks on the field-level to isolate hook logic to specific fields. [More details](./fields).
+  **Tip:** You can also set hooks on the field-level to isolate hook logic to
+  specific fields. [More details](./fields).
 </Banner>
 
 ## Config Options
@@ -82,12 +83,12 @@ const beforeOperationHook: CollectionBeforeOperationHook = async ({
 
 The following arguments are provided to the `beforeOperation` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`collection`**         | The [Collection](../configuration/collections) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between Hooks. [More details](./context).                                                                                                                              |
-| **`operation`**          | The name of the operation that this hook is running within. |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
+| Option           | Description                                                                                                                                           |
+| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`collection`** | The [Collection](../configuration/collections) in which this Hook is running against.                                                                 |
+| **`context`**    | Custom context passed between Hooks. [More details](./context).                                                                                       |
+| **`operation`**  | The name of the operation that this hook is running within.                                                                                           |
+| **`req`**        | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
 
 ### beforeValidate
 
@@ -102,23 +103,21 @@ Please do note that this does not run before client-side validation. If you rend
 ```ts
 import type { CollectionBeforeValidateHook } from 'payload'
 
-const beforeValidateHook: CollectionBeforeValidateHook = async ({
-  data,
-}) => {
+const beforeValidateHook: CollectionBeforeValidateHook = async ({ data }) => {
   return data
 }
 ```
 
 The following arguments are provided to the `beforeValidate` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`collection`**         | The [Collection](../configuration/collections) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between Hooks. [More details](./context).                                                                                                                              |
-| **`data`**               | The incoming data passed through the operation.                                                                                 |
-| **`operation`**          | The name of the operation that this hook is running within. |
-| **`originalDoc`**        | The Document before changes are applied.                                                                                        |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
+| Option            | Description                                                                                                                                           |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`collection`**  | The [Collection](../configuration/collections) in which this Hook is running against.                                                                 |
+| **`context`**     | Custom context passed between Hooks. [More details](./context).                                                                                       |
+| **`data`**        | The incoming data passed through the operation.                                                                                                       |
+| **`operation`**   | The name of the operation that this hook is running within.                                                                                           |
+| **`originalDoc`** | The Document before changes are applied.                                                                                                              |
+| **`req`**         | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
 
 ### beforeChange
 
@@ -127,23 +126,21 @@ Immediately following validation, `beforeChange` hooks will run within `create`
 ```ts
 import type { CollectionBeforeChangeHook } from 'payload'
 
-const beforeChangeHook: CollectionBeforeChangeHook = async ({
-  data,
-}) => {
+const beforeChangeHook: CollectionBeforeChangeHook = async ({ data }) => {
   return data
 }
 ```
 
 The following arguments are provided to the `beforeChange` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`collection`**         | The [Collection](../configuration/collections) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between hooks. [More details](./context).                                                                                                                              |
-| **`data`**               | The incoming data passed through the operation.                                                                                 |
-| **`operation`**          | The name of the operation that this hook is running within. |
-| **`originalDoc`**        | The Document before changes are applied.                                                                                        |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
+| Option            | Description                                                                                                                                           |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`collection`**  | The [Collection](../configuration/collections) in which this Hook is running against.                                                                 |
+| **`context`**     | Custom context passed between hooks. [More details](./context).                                                                                       |
+| **`data`**        | The incoming data passed through the operation.                                                                                                       |
+| **`operation`**   | The name of the operation that this hook is running within.                                                                                           |
+| **`originalDoc`** | The Document before changes are applied.                                                                                                              |
+| **`req`**         | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
 
 ### afterChange
 
@@ -152,23 +149,21 @@ After a document is created or updated, the `afterChange` hook runs. This hook i
 ```ts
 import type { CollectionAfterChangeHook } from 'payload'
 
-const afterChangeHook: CollectionAfterChangeHook = async ({
-  doc,
-}) => {
+const afterChangeHook: CollectionAfterChangeHook = async ({ doc }) => {
   return doc
 }
 ```
 
 The following arguments are provided to the `afterChange` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`collection`**         | The [Collection](../configuration/collections) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between hooks. [More details](./context).                                                                                                                              |
-| **`doc`**               | The resulting Document after changes are applied. |
-| **`operation`**          | The name of the operation that this hook is running within. |
-| **`previousDoc`**        | The Document before changes were applied. |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
+| Option            | Description                                                                                                                                           |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`collection`**  | The [Collection](../configuration/collections) in which this Hook is running against.                                                                 |
+| **`context`**     | Custom context passed between hooks. [More details](./context).                                                                                       |
+| **`doc`**         | The resulting Document after changes are applied.                                                                                                     |
+| **`operation`**   | The name of the operation that this hook is running within.                                                                                           |
+| **`previousDoc`** | The Document before changes were applied.                                                                                                             |
+| **`req`**         | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
 
 ### beforeRead
 
@@ -177,9 +172,7 @@ Runs before `find` and `findByID` operations are transformed for output by `afte
 ```ts
 import type { CollectionBeforeReadHook } from 'payload'
 
-const beforeReadHook: CollectionBeforeReadHook = async ({
-  doc,
-}) => {
+const beforeReadHook: CollectionBeforeReadHook = async ({ doc }) => {
   return doc
 }
 ```
@@ -201,9 +194,7 @@ Runs as the last step before documents are returned. Flattens locales, hides pro
 ```ts
 import type { CollectionAfterReadHook } from 'payload'
 
-const afterReadHook: CollectionAfterReadHook = async ({
-  doc,
-}) => {
+const afterReadHook: CollectionAfterReadHook = async ({ doc }) => {
   return doc
 }
 ```
@@ -233,12 +224,12 @@ const beforeDeleteHook: CollectionBeforeDeleteHook = async ({
 
 The following arguments are provided to the `beforeDelete` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`collection`**         | The [Collection](../configuration/collections) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between hooks. [More details](./context).                                                                                                                              |
-| **`id`**               | The ID of the Document being deleted. |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
+| Option           | Description                                                                                                                                           |
+| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`collection`** | The [Collection](../configuration/collections) in which this Hook is running against.                                                                 |
+| **`context`**    | Custom context passed between hooks. [More details](./context).                                                                                       |
+| **`id`**         | The ID of the Document being deleted.                                                                                                                 |
+| **`req`**        | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
 
 ### afterDelete
 
@@ -256,13 +247,13 @@ const afterDeleteHook: CollectionAfterDeleteHook = async ({
 
 The following arguments are provided to the `afterDelete` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`collection`**         | The [Collection](../configuration/collections) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between hooks. [More details](./context).                                                                                                                              |
-| **`doc`**               | The resulting Document after changes are applied. |
-| **`id`**          | The ID of the Document that was deleted. |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
+| Option           | Description                                                                                                                                           |
+| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`collection`** | The [Collection](../configuration/collections) in which this Hook is running against.                                                                 |
+| **`context`**    | Custom context passed between hooks. [More details](./context).                                                                                       |
+| **`doc`**        | The resulting Document after changes are applied.                                                                                                     |
+| **`id`**         | The ID of the Document that was deleted.                                                                                                              |
+| **`req`**        | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
 
 ### afterOperation
 
@@ -273,22 +264,20 @@ Available Collection operations include `create`, `find`, `findByID`, `update`,
 ```ts
 import type { CollectionAfterOperationHook } from 'payload'
 
-const afterOperationHook: CollectionAfterOperationHook = async ({
-  result,
-}) => {
+const afterOperationHook: CollectionAfterOperationHook = async ({ result }) => {
   return result
 }
 ```
 
 The following arguments are provided to the `afterOperation` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`args`**               | The arguments passed into the operation.                                                                                 |
-| **`collection`**         | The [Collection](../configuration/collections) in which this Hook is running against.                                                                                                                       |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
-| **`operation`**          | The name of the operation that this hook is running within. |
-| **`result`**          |  The result of the operation, before modifications. |
+| Option           | Description                                                                                                                                           |
+| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`args`**       | The arguments passed into the operation.                                                                                                              |
+| **`collection`** | The [Collection](../configuration/collections) in which this Hook is running against.                                                                 |
+| **`req`**        | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
+| **`operation`**  | The name of the operation that this hook is running within.                                                                                           |
+| **`result`**     | The result of the operation, before modifications.                                                                                                    |
 
 ### afterError
 
@@ -297,12 +286,13 @@ The `afterError` Hook is triggered when an error occurs in the Payload applicati
 ```ts
 import type { CollectionAfterErrorHook } from 'payload';
 
-const afterDeleteHook: CollectionAfterErrorHook = async ({
+const afterErrorHook: CollectionAfterErrorHook = async ({
   req,
   id,
   doc,
 }) => {...}
 ```
+
 The following arguments are provided to the `afterError` Hook:
 
 | Argument            | Description                                                                                                                                                                                     |
@@ -321,21 +311,19 @@ For [Auth-enabled Collections](../authentication/overview), this hook runs durin
 ```ts
 import type { CollectionBeforeLoginHook } from 'payload'
 
-const beforeLoginHook: CollectionBeforeLoginHook = async ({
-  user,
-}) => {
+const beforeLoginHook: CollectionBeforeLoginHook = async ({ user }) => {
   return user
 }
 ```
 
 The following arguments are provided to the `beforeLogin` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`collection`**         | The [Collection](../configuration/collections) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between hooks. [More details](./context).                                                                                                                              |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
-| **`user`**               | The user being logged in. |
+| Option           | Description                                                                                                                                           |
+| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`collection`** | The [Collection](../configuration/collections) in which this Hook is running against.                                                                 |
+| **`context`**    | Custom context passed between hooks. [More details](./context).                                                                                       |
+| **`req`**        | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
+| **`user`**       | The user being logged in.                                                                                                                             |
 
 ### afterLogin
 
@@ -352,13 +340,13 @@ const afterLoginHook: CollectionAfterLoginHook = async ({
 
 The following arguments are provided to the `afterLogin` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`collection`**         | The [Collection](../configuration/collections) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between hooks. [More details](./context).                                                                                                                              |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
-| **`token`**              | The token generated for the user. |
-| **`user`**               | The user being logged in. |
+| Option           | Description                                                                                                                                           |
+| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`collection`** | The [Collection](../configuration/collections) in which this Hook is running against.                                                                 |
+| **`context`**    | Custom context passed between hooks. [More details](./context).                                                                                       |
+| **`req`**        | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
+| **`token`**      | The token generated for the user.                                                                                                                     |
+| **`user`**       | The user being logged in.                                                                                                                             |
 
 ### afterLogout
 
@@ -374,11 +362,11 @@ const afterLogoutHook: CollectionAfterLogoutHook = async ({
 
 The following arguments are provided to the `afterLogout` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`collection`**         | The [Collection](../configuration/collections) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between hooks. [More details](./context).                                                                                                                              |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
+| Option           | Description                                                                                                                                           |
+| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`collection`** | The [Collection](../configuration/collections) in which this Hook is running against.                                                                 |
+| **`context`**    | Custom context passed between hooks. [More details](./context).                                                                                       |
+| **`req`**        | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
 
 ### afterMe
 
@@ -395,12 +383,12 @@ const afterMeHook: CollectionAfterMeHook = async ({
 
 The following arguments are provided to the `afterMe` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`collection`**         | The [Collection](../configuration/collections) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between hooks. [More details](./context).                                                                                                                              |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
-| **`response`**           | The response to return. |
+| Option           | Description                                                                                                                                           |
+| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`collection`** | The [Collection](../configuration/collections) in which this Hook is running against.                                                                 |
+| **`context`**    | Custom context passed between hooks. [More details](./context).                                                                                       |
+| **`req`**        | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
+| **`response`**   | The response to return.                                                                                                                               |
 
 ### afterRefresh
 
@@ -416,13 +404,13 @@ const afterRefreshHook: CollectionAfterRefreshHook = async ({
 
 The following arguments are provided to the `afterRefresh` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`collection`**         | The [Collection](../configuration/collections) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between hooks. [More details](./context).                                                                                                                              |
-| **`exp`**                | The expiration time of the token. |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
-| **`token`**              | The newly refreshed user token. |
+| Option           | Description                                                                                                                                           |
+| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`collection`** | The [Collection](../configuration/collections) in which this Hook is running against.                                                                 |
+| **`context`**    | Custom context passed between hooks. [More details](./context).                                                                                       |
+| **`exp`**        | The expiration time of the token.                                                                                                                     |
+| **`req`**        | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
+| **`token`**      | The newly refreshed user token.                                                                                                                       |
 
 ### afterForgotPassword
 
@@ -440,11 +428,11 @@ const afterForgotPasswordHook: CollectionAfterForgotPasswordHook = async ({
 
 The following arguments are provided to the `afterForgotPassword` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`args`**               | The arguments passed into the operation.                                                                                 |
-| **`collection`**         | The [Collection](../configuration/collections) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between hooks. [More details](./context).                                                                                                                              |
+| Option           | Description                                                                           |
+| ---------------- | ------------------------------------------------------------------------------------- |
+| **`args`**       | The arguments passed into the operation.                                              |
+| **`collection`** | The [Collection](../configuration/collections) in which this Hook is running against. |
+| **`context`**    | Custom context passed between hooks. [More details](./context).                       |
 
 ### refresh
 
@@ -461,10 +449,10 @@ const myRefreshHook: CollectionRefreshHook = async ({
 
 The following arguments are provided to the `afterRefresh` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`args`**               | The arguments passed into the operation.                                                                                 |
-| **`user`**               | The user being logged in. |
+| Option     | Description                              |
+| ---------- | ---------------------------------------- |
+| **`args`** | The arguments passed into the operation. |
+| **`user`** | The user being logged in.                |
 
 ### me
 
@@ -481,10 +469,10 @@ const meHook: CollectionMeHook = async ({
 
 The following arguments are provided to the `me` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`args`**               | The arguments passed into the operation.                                                                                 |
-| **`user`**               | The user being logged in. |
+| Option     | Description                              |
+| ---------- | ---------------------------------------- |
+| **`args`** | The arguments passed into the operation. |
+| **`user`** | The user being logged in.                |
 
 ## TypeScript
 

docs/hooks/context.mdx

@@ -14,7 +14,7 @@ Context gives you a way forward on otherwise difficult problems such as:
 
 1. **Passing data between Hooks**: Needing data in multiple Hooks from a 3rd party API, it could be retrieved and used in `beforeChange` and later used again in an `afterChange` hook without having to fetch it twice.
 2. **Preventing infinite loops**: Calling `payload.update()` on the same document that triggered an `afterChange` hook will create an infinite loop, control the flow by assigning a no-op condition to context
-3. **Passing data to local API**: Setting values on the `req.context` and pass it to `payload.create()` you can provide additional data to hooks without adding extraneous fields.
+3. **Passing data to Local API**: Setting values on the `req.context` and pass it to `payload.create()` you can provide additional data to hooks without adding extraneous fields.
 4. **Passing data between hooks and middleware or custom endpoints**: Hooks could set context across multiple collections and then be used in a final `postMiddleware`.
 
 ## How To Use Context

docs/hooks/fields.mdx

@@ -11,11 +11,12 @@ Field Hooks are [Hooks](./overview) that run on Documents on a per-field basis.
 To add Hooks to a Field, use the `hooks` property in your [Field Config](../fields/overview):
 
 ```ts
-import type { Field } from 'payload';
+import type { Field } from 'payload'
 
 export const FieldWithHooks: Field = {
   // ...
-  hooks: { // highlight-line
+  hooks: {
+    // highlight-line
     // ...
   },
 }
@@ -26,8 +27,11 @@ export const FieldWithHooks: Field = {
 All Field Hooks accept an array of synchronous or asynchronous functions. These functions can optionally modify the return value of the field before the operation continues. All Field Hooks are formatted to accept the same arguments, although some arguments may be `undefined` based the specific hook type.
 
 <Banner type="warning">
-  **Important:**
-  Due to GraphQL's typed nature, changing the type of data that you return from a field will produce errors in the [GraphQL API](../graphql/overview). If you need to change the shape or type of data, consider [Collection Hooks](./collections) or [Global Hooks](./globals) instead.
+  **Important:** Due to GraphQL's typed nature, changing the type of data that
+  you return from a field will produce errors in the [GraphQL
+  API](../graphql/overview). If you need to change the shape or type of data,
+  consider [Collection Hooks](./collections) or [Global Hooks](./globals)
+  instead.
 </Banner>
 
 To add hooks to a Field, use the `hooks` property in your [Field Config](../fields/overview):
@@ -52,31 +56,33 @@ const FieldWithHooks: Field = {
 
 The following arguments are provided to all Field Hooks:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`collection`**         | The [Collection](../configuration/collections) in which this Hook is running against. If the field belongs to a Global, this will be `null`.                                                                                                                       |
-| **`context`**            | Custom context passed between Hooks. [More details](./context).                                                                                                                              |
-| **`data`**               | In the `afterRead` hook this is the full Document. In the `create` and `update` operations, this is the incoming data passed through the operation.                                                                                 |
-| **`field`**              | The [Field](../fields/overview) which the Hook is running against.                                                                                                                                                                          |
-| **`findMany`**           | Boolean to denote if this hook is running against finding one, or finding many within the `afterRead` hook.                                                                                                           |
-| **`global`**             | The [Global](../configuration/globals) in which this Hook is running against. If the field belongs to a Collection, this will be `null`.                                                                                                                       |
-| **`operation`**          | The name of the operation that this hook is running within. Useful within `beforeValidate`, `beforeChange`, and `afterChange` hooks to differentiate between `create` and `update` operations. |
-| **`originalDoc`**        | In the `update` operation, this is the Document before changes were applied. In the `afterChange` hook, this is the resulting Document.                                                                                        |
-| **`overrideAccess`**        | A boolean to denote if the current operation is overriding [Access Control](../access-control/overview).                                                                                                                                                                          |
-| **`path`**             | The path to the [Field](../fields/overview) in the schema.                                                                                                                                                                          |
-| **`previousDoc`**        | In the `afterChange` Hook, this is the Document before changes were applied.                                                                                                                                                |
-| **`previousSiblingDoc`** | The sibling data of the Document before changes being applied, only in `beforeChange` and `afterChange` hook.                                                                                                         |
-| **`previousValue`**      | The previous value of the field, before changes, only in `beforeChange` and `afterChange` hooks.                                                                                                                      |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
-| **`schemaPath`**         | The path of the [Field](../fields/overview) in the schema.                                                                                                                                                                                  |
-| **`siblingData`**        | The data of sibling fields adjacent to the field that the Hook is running against.        |
-| **`siblingDocWithLocales`**      | The sibling data of the Document with all [Locales](../configuration/localization).        |
-| **`siblingFields`**      | The sibling fields of the field which the hook is running against.        |
-| **`value`**              | The value of the [Field](../fields/overview).                                                                                                                                                                                               |
+| Option                      | Description                                                                                                                                                                                    |
+| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`collection`**            | The [Collection](../configuration/collections) in which this Hook is running against. If the field belongs to a Global, this will be `null`.                                                   |
+| **`context`**               | Custom context passed between Hooks. [More details](./context).                                                                                                                                |
+| **`data`**                  | In the `afterRead` hook this is the full Document. In the `create` and `update` operations, this is the incoming data passed through the operation.                                            |
+| **`field`**                 | The [Field](../fields/overview) which the Hook is running against.                                                                                                                             |
+| **`findMany`**              | Boolean to denote if this hook is running against finding one, or finding many within the `afterRead` hook.                                                                                    |
+| **`global`**                | The [Global](../configuration/globals) in which this Hook is running against. If the field belongs to a Collection, this will be `null`.                                                       |
+| **`operation`**             | The name of the operation that this hook is running within. Useful within `beforeValidate`, `beforeChange`, and `afterChange` hooks to differentiate between `create` and `update` operations. |
+| **`originalDoc`**           | In the `update` operation, this is the Document before changes were applied. In the `afterChange` hook, this is the resulting Document.                                                        |
+| **`overrideAccess`**        | A boolean to denote if the current operation is overriding [Access Control](../access-control/overview).                                                                                       |
+| **`path`**                  | The path to the [Field](../fields/overview) in the schema.                                                                                                                                     |
+| **`previousDoc`**           | In the `afterChange` Hook, this is the Document before changes were applied.                                                                                                                   |
+| **`previousSiblingDoc`**    | The sibling data of the Document before changes being applied, only in `beforeChange` and `afterChange` hook.                                                                                  |
+| **`previousValue`**         | The previous value of the field, before changes, only in `beforeChange` and `afterChange` hooks.                                                                                               |
+| **`req`**                   | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                          |
+| **`schemaPath`**            | The path of the [Field](../fields/overview) in the schema.                                                                                                                                     |
+| **`siblingData`**           | The data of sibling fields adjacent to the field that the Hook is running against.                                                                                                             |
+| **`siblingDocWithLocales`** | The sibling data of the Document with all [Locales](../configuration/localization).                                                                                                            |
+| **`siblingFields`**         | The sibling fields of the field which the hook is running against.                                                                                                                             |
+| **`value`**                 | The value of the [Field](../fields/overview).                                                                                                                                                  |
 
 <Banner type="success">
-  **Tip:**
-  It's a good idea to conditionally scope your logic based on which operation is executing. For example, if you are writing a `beforeChange` hook, you may want to perform different logic based on if the current `operation` is `create` or `update`.
+  **Tip:** It's a good idea to conditionally scope your logic based on which
+  operation is executing. For example, if you are writing a `beforeChange` hook,
+  you may want to perform different logic based on if the current `operation` is
+  `create` or `update`.
 </Banner>
 
 ### beforeValidate
@@ -220,10 +226,12 @@ const numberField: Field = {
   type: 'number',
   hooks: {
     // increment existing value by 1
-    beforeDuplicate: [({ value }) => {
-      return (value ?? 0) + 1
-    }],
-  }
+    beforeDuplicate: [
+      ({ value }) => {
+        return (value ?? 0) + 1
+      },
+    ],
+  },
 }
 ```
 

docs/hooks/globals.mdx

@@ -11,19 +11,20 @@ Global Hooks are [Hooks](./overview) that run on [Global](../configuration/globa
 To add Hooks to a Global, use the `hooks` property in your [Global Config](../configuration/globals):
 
 ```ts
-import type { GlobalConfig } from 'payload';
+import type { GlobalConfig } from 'payload'
 
 export const GlobalWithHooks: GlobalConfig = {
   // ...
-  hooks: { // highlight-line
+  hooks: {
+    // highlight-line
     // ...
   },
 }
 ```
 
 <Banner type="info">
-  **Tip:**
-  You can also set hooks on the field-level to isolate hook logic to specific fields. [More details](./fields).
+  **Tip:** You can also set hooks on the field-level to isolate hook logic to
+  specific fields. [More details](./fields).
 </Banner>
 
 ## Config Options
@@ -71,13 +72,13 @@ const beforeValidateHook: GlobalBeforeValidateHook = async ({
 
 The following arguments are provided to the `beforeValidate` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`global`**         | The [Global](../configuration/globals) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between Hooks. [More details](./context).                                                                                                                              |
-| **`data`**               | The incoming data passed through the operation.                                                                                 |
-| **`originalDoc`**        | The Document before changes are applied.                                                                                        |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
+| Option            | Description                                                                                                                                           |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`global`**      | The [Global](../configuration/globals) in which this Hook is running against.                                                                         |
+| **`context`**     | Custom context passed between Hooks. [More details](./context).                                                                                       |
+| **`data`**        | The incoming data passed through the operation.                                                                                                       |
+| **`originalDoc`** | The Document before changes are applied.                                                                                                              |
+| **`req`**         | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
 
 ### beforeChange
 
@@ -97,13 +98,13 @@ const beforeChangeHook: GlobalBeforeChangeHook = async ({
 
 The following arguments are provided to the `beforeChange` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`global`**         | The [Global](../configuration/globals) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between hooks. [More details](./context).                                                                                                                              |
-| **`data`**               | The incoming data passed through the operation.                                                                                 |
-| **`originalDoc`**        | The Document before changes are applied.                                                                                        |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
+| Option            | Description                                                                                                                                           |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`global`**      | The [Global](../configuration/globals) in which this Hook is running against.                                                                         |
+| **`context`**     | Custom context passed between hooks. [More details](./context).                                                                                       |
+| **`data`**        | The incoming data passed through the operation.                                                                                                       |
+| **`originalDoc`** | The Document before changes are applied.                                                                                                              |
+| **`req`**         | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
 
 ### afterChange
 
@@ -123,13 +124,13 @@ const afterChangeHook: GlobalAfterChangeHook = async ({
 
 The following arguments are provided to the `afterChange` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`global`**         | The [Global](../configuration/globals) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between hooks. [More details](./context).                                                                                                                              |
-| **`doc`**               | The resulting Document after changes are applied. |
-| **`previousDoc`**        | The Document before changes were applied. |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
+| Option            | Description                                                                                                                                           |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`global`**      | The [Global](../configuration/globals) in which this Hook is running against.                                                                         |
+| **`context`**     | Custom context passed between hooks. [More details](./context).                                                                                       |
+| **`doc`**         | The resulting Document after changes are applied.                                                                                                     |
+| **`previousDoc`** | The Document before changes were applied.                                                                                                             |
+| **`req`**         | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
 
 ### beforeRead
 
@@ -146,12 +147,12 @@ const beforeReadHook: GlobalBeforeReadHook = async ({
 
 The following arguments are provided to the `beforeRead` hook:
 
-| Option                   | Description                                                                                                                                                                                                           |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`global`**         | The [Global](../configuration/globals) in which this Hook is running against.                                                                                                                       |
-| **`context`**            | Custom context passed between hooks. [More details](./context).                                                                                                                              |
-| **`doc`**               | The resulting Document after changes are applied. |
-| **`req`**                | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations.                                                                                                                                                  |
+| Option        | Description                                                                                                                                           |
+| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`global`**  | The [Global](../configuration/globals) in which this Hook is running against.                                                                         |
+| **`context`** | Custom context passed between hooks. [More details](./context).                                                                                       |
+| **`doc`**     | The resulting Document after changes are applied.                                                                                                     |
+| **`req`**     | The [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. This is mocked for [Local API](../local-api/overview) operations. |
 
 ### afterRead
 

docs/hooks/overview.mdx

@@ -26,8 +26,10 @@ There are four main types of Hooks in Payload:
 - [Field Hooks](/docs/hooks/fields)
 
 <Banner type="warning">
-  **Reminder:**
-  Payload also ships a set of _React_ hooks that you can use in your frontend application. Although they share a common name, these are very different things and should not be confused. [More details](../admin/hooks).
+  **Reminder:** Payload also ships a set of _React_ hooks that you can use in
+  your frontend application. Although they share a common name, these are very
+  different things and should not be confused. [More
+  details](../admin/react-hooks).
 </Banner>
 
 ## Root Hooks
@@ -51,9 +53,9 @@ export default buildConfig({
 
 The following options are available:
 
-| Option       | Description                                                                                   |
-|--------------|-----------------------------------------------------------------------------------------------|
-| **`afterError`** | Runs after an error occurs in the Payload application.                                         |
+| Option           | Description                                            |
+| ---------------- | ------------------------------------------------------ |
+| **`afterError`** | Runs after an error occurs in the Payload application. |
 
 ### afterError
 
@@ -65,9 +67,11 @@ import { buildConfig } from 'payload'
 export default buildConfig({
   // ...
   hooks: {
-    afterError: [async ({ error }) => {
-      // Do something
-    }]
+    afterError: [
+      async ({ error }) => {
+        // Do something
+      },
+    ],
   },
 })
 ```
@@ -82,6 +86,7 @@ The following arguments are provided to the `afterError` Hook:
 | **`req`**           | The `PayloadRequest` object that extends [Web Request](https://developer.mozilla.org/en-US/docs/Web/API/Request). Contains currently authenticated `user` and the Local API instance `payload`. |
 | **`collection`**    | The [Collection](../configuration/collections) in which this Hook is running against. This will be `undefined` if the hook is executed from a non-collection endpoint or GraphQL.               |
 | **`result`**        | The formatted error result object, available if the hook is executed from a REST context.                                                                                                       |
+
 ## Async vs. Synchronous
 
 All Hooks can be written as either synchronous or asynchronous functions. Choosing the right type depends on your use case, but switching between the two is as simple as adding or removing the `async` keyword.

docs/integrations/vercel-content-link.mdx

@@ -11,9 +11,10 @@ keywords: vercel, vercel content link, content link, visual editing, content sou
 ![Versions](/images/docs/vercel-visual-editing.jpg)
 
 <Banner type="warning">
-  Vercel Content Link is an enterprise-only feature and only available for deployments hosted on
-  Vercel. If you are an existing enterprise customer, [contact our sales
-  team](https://payloadcms.com/for-enterprise) for help with your integration.
+  Vercel Content Link is an enterprise-only feature and only available for
+  deployments hosted on Vercel. If you are an existing enterprise customer,
+  [contact our sales team](https://payloadcms.com/for-enterprise) for help with
+  your integration.
 </Banner>
 
 ## How it works

docs/jobs-queue/jobs.mdx

@@ -9,7 +9,9 @@ keywords: jobs queue, application framework, typescript, node, react, nextjs
 Now that we have covered Tasks and Workflows, we can tie them together with a concept called a Job.
 
 <Banner type="default">
-  Whereas you define Workflows and Tasks, which control your business logic, a **Job** is an individual instance of either a Task or a Workflow which contains many tasks.
+  Whereas you define Workflows and Tasks, which control your business logic, a
+  **Job** is an individual instance of either a Task or a Workflow which
+  contains many tasks.
 </Banner>
 
 For example, let's say we have a Workflow or Task that describes the logic to sync information from Payload to a third-party system. This is how you'd declare how to sync that info, but it wouldn't do anything on its own. In order to run that task or workflow, you'd create a Job that references the corresponding Task or Workflow.
@@ -44,3 +46,31 @@ const createdJob = await payload.jobs.queue({
   },
 })
 ```
+
+#### Cancelling Jobs
+
+Payload allows you to cancel jobs that are either queued or currently running. When cancelling a running job, the current task will finish executing, but no subsequent tasks will run. This happens because the job checks its cancellation status between tasks.
+
+##### Cancel a Single Job
+
+To cancel a specific job, use the `payload.jobs.cancelByID` method with the job's ID:
+
+```ts
+await payload.jobs.cancelByID({
+  id: createdJob.id,
+})
+```
+
+##### Cancel Multiple Jobs
+
+To cancel multiple jobs at once, use the `payload.jobs.cancel` method with a `Where` query:
+
+```ts
+await payload.jobs.cancel({
+  where: {
+    workflowSlug: {
+      equals: 'createPost',
+    },
+  },
+})
+```

docs/jobs-queue/queues.mdx

@@ -9,7 +9,8 @@ keywords: jobs queue, application framework, typescript, node, react, nextjs
 Queues are the final aspect of Payload's Jobs Queue and deal with how to _run your jobs_. Up to this point, all we've covered is how to queue up jobs to run, but so far, we aren't actually running any jobs.
 
 <Banner type="default">
-  A **Queue** is a grouping of jobs that should be executed in order of when they were added.
+  A **Queue** is a grouping of jobs that should be executed in order of when
+  they were added.
 </Banner>
 
 When you go to run jobs, Payload will query for any jobs that are added to the queue and then run them. By default, all queued jobs are added to the `default` queue.
@@ -38,7 +39,7 @@ export default buildConfig({
     tasks: [
       // your tasks here
     ],
-    // autoRun can optionally be a function that receives payload as an argument
+    // autoRun can optionally be a function that receives `payload` as an argument
     autoRun: [
       {
         cron: '0 * * * *', // every hour at minute 0
@@ -52,12 +53,15 @@ export default buildConfig({
       // This function will be invoked each time Payload goes to pick up and run jobs.
       // If this function ever returns false, the cron schedule will be stopped.
       return true
-    }
+    },
   },
 })
 ```
 
-<Banner type="warning">autoRun is intended for use with a dedicated server that is always running, and should not be used on serverless platforms like Vercel.</Banner>
+<Banner type="warning">
+  autoRun is intended for use with a dedicated server that is always running,
+  and should not be used on serverless platforms like Vercel.
+</Banner>
 
 #### Endpoint
 
@@ -69,9 +73,9 @@ You can execute jobs by making a fetch request to the `/api/payload-jobs/run` en
 await fetch('/api/payload-jobs/run?limit=100&queue=nightly', {
   method: 'GET',
   headers: {
-    'Authorization': `Bearer ${token}`,
+    Authorization: `Bearer ${token}`,
   },
-});
+})
 ```
 
 This endpoint is automatically mounted for you and is helpful in conjunction with serverless platforms like Vercel, where you might want to use Vercel Cron to invoke a serverless function that executes your jobs.
@@ -113,12 +117,12 @@ export default buildConfig({
         // If there is no logged in user, then check
         // for the Vercel Cron secret to be present as an
         // Authorization header:
-        const authHeader = req.headers.get('authorization');
-        return authHeader === `Bearer ${process.env.CRON_SECRET}`;
+        const authHeader = req.headers.get('authorization')
+        return authHeader === `Bearer ${process.env.CRON_SECRET}`
       },
     },
     // Other job configurations...
-  }
+  },
 })
 ```
 
@@ -139,14 +143,16 @@ const results = await payload.jobs.run()
 await payload.jobs.run({ queue: 'nightly', limit: 100 })
 
 // You can provide a where clause to filter the jobs that should be run:
-await payload.jobs.run({ where: { 'input.message': { equals: 'secret' } } })
+await payload.jobs.run({
+  where: { 'input.message': { equals: 'secret' } },
+})
 ```
 
 **Run a single job:**
 
 ```ts
 const results = await payload.jobs.runByID({
-  id: myJobID
+  id: myJobID,
 })
 ```
 

docs/jobs-queue/tasks.mdx

@@ -7,30 +7,31 @@ keywords: jobs queue, application framework, typescript, node, react, nextjs
 ---
 
 <Banner type="default">
-  A **"Task"** is a function definition that performs business logic and whose input and output are both strongly typed.
+  A **"Task"** is a function definition that performs business logic and whose
+  input and output are both strongly typed.
 </Banner>
 
 You can register Tasks on the Payload config, and then create [Jobs](/docs/jobs-queue/jobs) or [Workflows](/docs/jobs-queue/workflows) that use them. Think of Tasks like tidy, isolated "functions that do one specific thing".
 
 Payload Tasks can be configured to automatically retried if they fail, which makes them valuable for "durable" workflows like AI applications where LLMs can return non-deterministic results, and might need to be retried.
 
-Tasks can either be defined within the `jobs.tasks` array in your payload config, or they can be defined inline within a workflow.
+Tasks can either be defined within the `jobs.tasks` array in your Payload config, or they can be defined inline within a workflow.
 
 ### Defining tasks in the config
 
 Simply add a task to the `jobs.tasks` array in your Payload config. A task consists of the following fields:
 
-| Option                      | Description                                                                      |
-| --------------------------- | -------------------------------------------------------------------------------- |
-| `slug` | Define a slug-based name for this job. This slug needs to be unique among both tasks and workflows.|
-| `handler`   | The function that should be responsible for running the job. You can either pass a string-based path to the job function file, or the job function itself. If you are using large dependencies within your job, you might prefer to pass the string path because that will avoid bundling large dependencies in your Next.js app. Passing a string path is an advanced feature that may require a sophisticated build pipeline in order to work.         |
-| `inputSchema` | Define the input field schema - payload will generate a type for this schema. |
-| `interfaceName` | You can use interfaceName to change the name of the interface that is generated for this task. By default, this is "Task" + the capitalized task slug. |
-| `outputSchema` | Define the output field schema - payload will generate a type for this schema. |
-| `label` | Define a human-friendly label for this task. |
-| `onFail` | Function to be executed if the task fails. |
-| `onSuccess` | Function to be executed if the task succeeds. |
-| `retries` | Specify the number of times that this step should be retried if it fails. If this is undefined, the task will either inherit the retries from the workflow or have no retries. If this is 0, the task will not be retried. By default, this is undefined. |
+| Option          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `slug`          | Define a slug-based name for this job. This slug needs to be unique among both tasks and workflows.                                                                                                                                                                                                                                                                                                                                              |
+| `handler`       | The function that should be responsible for running the job. You can either pass a string-based path to the job function file, or the job function itself. If you are using large dependencies within your job, you might prefer to pass the string path because that will avoid bundling large dependencies in your Next.js app. Passing a string path is an advanced feature that may require a sophisticated build pipeline in order to work. |
+| `inputSchema`   | Define the input field schema - Payload will generate a type for this schema.                                                                                                                                                                                                                                                                                                                                                                    |
+| `interfaceName` | You can use interfaceName to change the name of the interface that is generated for this task. By default, this is "Task" + the capitalized task slug.                                                                                                                                                                                                                                                                                           |
+| `outputSchema`  | Define the output field schema - Payload will generate a type for this schema.                                                                                                                                                                                                                                                                                                                                                                   |
+| `label`         | Define a human-friendly label for this task.                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `onFail`        | Function to be executed if the task fails.                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `onSuccess`     | Function to be executed if the task succeeds.                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `retries`       | Specify the number of times that this step should be retried if it fails. If this is undefined, the task will either inherit the retries from the workflow or have no retries. If this is 0, the task will not be retried. By default, this is undefined.                                                                                                                                                                                        |
 
 The logic for the Task is defined in the `handler` - which can be defined as a function, or a path to a function. The `handler` will run once a worker picks picks up a Job that includes this task.
 
@@ -86,8 +87,8 @@ export default buildConfig({
           }
         },
       } as TaskConfig<'createPost'>,
-    ]
-  }
+    ],
+  },
 })
 ```
 
@@ -112,10 +113,12 @@ export default buildConfig({
       {
         // ...
         // The #createPostHandler is a named export within the `createPost.ts` file
-        handler: path.resolve(dirname, 'src/tasks/createPost.ts') + '#createPostHandler',
-      }
-    ]
-  }
+        handler:
+          path.resolve(dirname, 'src/tasks/createPost.ts') +
+          '#createPostHandler',
+      },
+    ],
+  },
 })
 ```
 
@@ -126,7 +129,11 @@ Then, the `createPost` file itself:
 ```ts
 import type { TaskHandler } from 'payload'
 
-export const createPostHandler: TaskHandler<'createPost'> = async ({ input, job, req }) => {
+export const createPostHandler: TaskHandler<'createPost'> = async ({
+  input,
+  job,
+  req,
+}) => {
   const newPost = await req.payload.create({
     collection: 'post',
     req,
@@ -165,11 +172,11 @@ export default buildConfig({
         slug: 'myTask',
         retries: {
           shouldRestore: false,
-        }
+        },
         // ...
       } as TaskConfig<'myTask'>,
-    ]
-  }
+    ],
+  },
 })
 ```
 
@@ -191,16 +198,16 @@ export default buildConfig({
         ],
         retries: {
           shouldRestore: ({ input }) => {
-            if(new Date(input.someDate) > new Date()) {
+            if (new Date(input.someDate) > new Date()) {
               return false
             }
             return true
           },
-        }
+        },
         // ...
       } as TaskConfig<'myTask'>,
-    ]
-  }
+    ],
+  },
 })
 ```
 
@@ -208,7 +215,6 @@ export default buildConfig({
 
 You can run sub-tasks within an existing task, by using the `tasks` or `ìnlineTask` arguments passed to the task `handler` function:
 
-
 ```ts
 export default buildConfig({
   // ...
@@ -222,11 +228,10 @@ export default buildConfig({
         inputSchema: [
           {
             name: 'text',
-            type: 'text'
+            type: 'text',
           },
         ],
         handler: async ({ input, req, tasks, inlineTask }) => {
-
           await inlineTask('Sub Task 1', {
             task: () => {
               // Do something
@@ -243,9 +248,9 @@ export default buildConfig({
           return {
             output: {},
           }
-        }
+        },
       } as TaskConfig<'parentTask'>,
-    ]
-  }
+    ],
+  },
 })
 ```

docs/jobs-queue/workflows.mdx

@@ -7,7 +7,8 @@ keywords: jobs queue, application framework, typescript, node, react, nextjs
 ---
 
 <Banner type="default">
-  A **"Workflow"** is an optional way to *combine multiple tasks together* in a way that can be gracefully retried from the point of failure.
+  A **"Workflow"** is an optional way to *combine multiple tasks together* in a
+  way that can be gracefully retried from the point of failure.
 </Banner>
 
 They're most helpful when you have multiple tasks in a row, and you want to configure each task to be able to be retried if they fail.
@@ -22,15 +23,15 @@ However, importantly, tasks that have successfully been completed will simply re
 
 To define a JS-based workflow, simply add a workflow to the `jobs.workflows` array in your Payload config. A workflow consists of the following fields:
 
-| Option                      | Description                                                                      |
-| --------------------------- | -------------------------------------------------------------------------------- |
-| `slug` | Define a slug-based name for this workflow. This slug needs to be unique among both tasks and workflows.|
-| `handler`   | The function that should be responsible for running the workflow. You can either pass a string-based path to the workflow function file, or workflow job function itself. If you are using large dependencies within your workflow, you might prefer to pass the string path because that will avoid bundling large dependencies in your Next.js app. Passing a string path is an advanced feature that may require a sophisticated build pipeline in order to work.       |
-| `inputSchema` | Define the input field schema - payload will generate a type for this schema. |
-| `interfaceName` | You can use interfaceName to change the name of the interface that is generated for this workflow. By default, this is "Workflow" + the capitalized workflow slug. |
-| `label` | Define a human-friendly label for this workflow. |
-| `queue` | Optionally, define the queue name that this workflow should be tied to. Defaults to "default". |
-| `retries` | You can define `retries` on the workflow level, which will enforce that the workflow can only fail up to that number of retries. If a task does not have retries specified, it will inherit the retry count as specified on the workflow. You can specify `0` as `workflow` retries, which will disregard all `task` retry specifications and fail the entire workflow on any task failure. You can leave `workflow` retries as undefined, in which case, the workflow will respect what each task dictates as their own retry count. By default this is undefined, meaning workflows retries are defined by their tasks |
+| Option          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `slug`          | Define a slug-based name for this workflow. This slug needs to be unique among both tasks and workflows.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `handler`       | The function that should be responsible for running the workflow. You can either pass a string-based path to the workflow function file, or workflow job function itself. If you are using large dependencies within your workflow, you might prefer to pass the string path because that will avoid bundling large dependencies in your Next.js app. Passing a string path is an advanced feature that may require a sophisticated build pipeline in order to work.                                                                                                                                                     |
+| `inputSchema`   | Define the input field schema - Payload will generate a type for this schema.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `interfaceName` | You can use interfaceName to change the name of the interface that is generated for this workflow. By default, this is "Workflow" + the capitalized workflow slug.                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `label`         | Define a human-friendly label for this workflow.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `queue`         | Optionally, define the queue name that this workflow should be tied to. Defaults to "default".                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `retries`       | You can define `retries` on the workflow level, which will enforce that the workflow can only fail up to that number of retries. If a task does not have retries specified, it will inherit the retry count as specified on the workflow. You can specify `0` as `workflow` retries, which will disregard all `task` retry specifications and fail the entire workflow on any task failure. You can leave `workflow` retries as undefined, in which case, the workflow will respect what each task dictates as their own retry count. By default this is undefined, meaning workflows retries are defined by their tasks |
 
 Example:
 

docs/live-preview/client.mdx

@@ -7,7 +7,9 @@ keywords: live preview, frontend, react, next.js, vue, nuxt.js, svelte, hook, us
 ---
 
 <Banner type="info">
-  If your front-end application supports Server Components like the [Next.js App Router](https://nextjs.org/docs/app), etc., we suggest setting up [server-side Live Preview](./server) instead.
+  If your front-end application supports Server Components like the [Next.js App
+  Router](https://nextjs.org/docs/app), etc., we suggest setting up [server-side
+  Live Preview](./server) instead.
 </Banner>
 
 While using Live Preview, the [Admin Panel](../admin/overview) emits a new `window.postMessage` event every time your document has changed. Your front-end application can listen for these events and re-render accordingly.
@@ -18,12 +20,12 @@ By default, all hooks accept the following args:
 
 | Path               | Description                                                                            |
 | ------------------ | -------------------------------------------------------------------------------------- |
-| **`serverURL`** * | The URL of your Payload server.                                                        |
+| **`serverURL`** \* | The URL of your Payload server.                                                        |
 | **`initialData`**  | The initial data of the document. The live data will be merged in as changes are made. |
 | **`depth`**        | The depth of the relationships to fetch. Defaults to `0`.                              |
 | **`apiRoute`**     | The path of your API route as defined in `routes.api`. Defaults to `/api`.             |
 
-_* An asterisk denotes that a property is required._
+_\* An asterisk denotes that a property is required._
 
 And return the following values:
 
@@ -33,15 +35,19 @@ And return the following values:
 | **`isLoading`** | A boolean that indicates whether or not the document is loading. |
 
 <Banner type="info">
-  If your front-end is tightly coupled to required fields, you should ensure that your UI does not
-  break when these fields are removed. For example, if you are rendering something like
-  `data.relatedPosts[0].title`, your page will break once you remove the first related post. To get
-  around this, use conditional logic, optional chaining, or default values in your UI where needed.
-  For example, `data?.relatedPosts?.[0]?.title`.
+  If your front-end is tightly coupled to required fields, you should ensure
+  that your UI does not break when these fields are removed. For example, if you
+  are rendering something like `data.relatedPosts[0].title`, your page will
+  break once you remove the first related post. To get around this, use
+  conditional logic, optional chaining, or default values in your UI where
+  needed. For example, `data?.relatedPosts?.[0]?.title`.
 </Banner>
 
 <Banner type="info">
-  It is important that the `depth` argument matches exactly with the depth of your initial page request. The depth property is used to populated relationships and uploads beyond their IDs. See [Depth](../queries/depth) for more information.
+  It is important that the `depth` argument matches exactly with the depth of
+  your initial page request. The depth property is used to populated
+  relationships and uploads beyond their IDs. See [Depth](../queries/depth) for
+  more information.
 </Banner>
 
 ## Frameworks
@@ -89,8 +95,9 @@ export const PageClient: React.FC<{
 ```
 
 <Banner type="warning">
-  **Reminder:**
-  If you are using [React Server Components](https://react.dev/reference/rsc/server-components), we strongly suggest setting up [server-side Live Preview](./server) instead.
+  **Reminder:** If you are using [React Server
+  Components](https://react.dev/reference/rsc/server-components), we strongly
+  suggest setting up [server-side Live Preview](./server) instead.
 </Banner>
 
 ### Vue
@@ -140,19 +147,19 @@ npm install @payloadcms/live-preview
 
 This package provides the following functions:
 
-| Path                     | Description                                                                                                                |
-| ------------------------ | -------------------------------------------------------------------------------------------------------------------------- |
-| **`subscribe`**          | Subscribes to the Admin Panel's `window.postMessage` events and calls the provided callback function.                      |
-| **`unsubscribe`**        | Unsubscribes from the Admin Panel's `window.postMessage` events.                                                           |
-| **`ready`**              | Sends a `window.postMessage` event to the Admin Panel to indicate that the front-end is ready to receive messages.         |
-| **`isLivePreviewEvent`** | Checks if a `MessageEvent` originates from the Admin Panel and is a Live Preview event, i.e. debounced form state.         |
+| Path                     | Description                                                                                                        |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------ |
+| **`subscribe`**          | Subscribes to the Admin Panel's `window.postMessage` events and calls the provided callback function.              |
+| **`unsubscribe`**        | Unsubscribes from the Admin Panel's `window.postMessage` events.                                                   |
+| **`ready`**              | Sends a `window.postMessage` event to the Admin Panel to indicate that the front-end is ready to receive messages. |
+| **`isLivePreviewEvent`** | Checks if a `MessageEvent` originates from the Admin Panel and is a Live Preview event, i.e. debounced form state. |
 
 The `subscribe` function takes the following args:
 
 | Path               | Description                                                                                 |
 | ------------------ | ------------------------------------------------------------------------------------------- |
-| **`callback`** *  | A callback function that is called with `data` every time a change is made to the document. |
-| **`serverURL`** * | The URL of your Payload server.                                                             |
+| **`callback`** \*  | A callback function that is called with `data` every time a change is made to the document. |
+| **`serverURL`** \* | The URL of your Payload server.                                                             |
 | **`initialData`**  | The initial data of the document. The live data will be merged in as changes are made.      |
 | **`depth`**        | The depth of the relationships to fetch. Defaults to `0`.                                   |
 
@@ -233,22 +240,20 @@ export const useLivePreview = <T extends any>(props: {
 ```
 
 <Banner type="info">
-  When building your own hook, ensure that the args and return values are consistent with the ones
-  listed at the top of this document. This will ensure that all hooks follow the same API.
+  When building your own hook, ensure that the args and return values are
+  consistent with the ones listed at the top of this document. This will ensure
+  that all hooks follow the same API.
 </Banner>
 
 ## Example
 
-For a working demonstration of this, check out the official [Live Preview Example](https://github.com/payloadcms/payload/tree/main/examples/live-preview). There you will find examples of various front-end frameworks and how to integrate each one of them, including:
-
-- [Next.js App Router](https://github.com/payloadcms/payload/tree/main/examples/live-preview/next-app)
-- [Next.js Pages Router](https://github.com/payloadcms/payload/tree/main/examples/live-preview/next-pages)
+For a working demonstration of this, check out the official [Live Preview Example](https://github.com/payloadcms/payload/tree/main/examples/live-preview). There you will find an example of a fully integrated Next.js App Router front-end that runs on the same server as Payload.
 
 ## Troubleshooting
 
 #### Relationships and/or uploads are not populating
 
-If you are using relationships or uploads in your front-end application, and your front-end application runs on a different domain than your Payload server, you may need to configure [CORS](../configuration/overview) to allow requests to be made between the two domains. This includes sites that are running on a different port or subdomain. Similarly, if you are protecting resources behind user authentication, you may also need to configure [CSRF](../authentication/overview#csrf-protection) to allow cookies to be sent between the two domains. For example:
+If you are using relationships or uploads in your front-end application, and your front-end application runs on a different domain than your Payload server, you may need to configure [CORS](../configuration/overview#cors) to allow requests to be made between the two domains. This includes sites that are running on a different port or subdomain. Similarly, if you are protecting resources behind user authentication, you may also need to configure [CSRF](../authentication/cookies#csrf-prevention) to allow cookies to be sent between the two domains. For example:
 
 ```ts
 // payload.config.ts