@lowdefy/docs-content 0.0.0-experimental-20260909201552 → 6.0.0

package/content/container-blocks/modal.md

@@ -1,6 +1,6 @@
 # Modal
 
-Modal dialog overlay for focused content. Add `shortcut: Escape` to the `onClose` event to run custom actions when Escape is pressed. Ant Design's Modal already closes on Escape by default — the shortcut triggers your custom actions in addition to the built-in close.
+Modal dialog overlay for focused content. Add `shortcut: Escape` to the `onClose` event to run custom actions when Escape is pressed. Ant Design's Modal already closes on Escape by default — the shortcut triggers your custom actions in addition to the built-in close.
 
 This is a basic modal dialog with a title, content area, and default Ok/Cancel buttons.
 

package/content/container-blocks/pagesidebarlayout.md

@@ -411,7 +411,6 @@ Dashboard Overview
 | `/mobileMenu` | The PageSidebarLayout mobile menu. |
 | `/header` | The PageSidebarLayout header. |
 | `/headerActions` | The header actions container (notifications, profile, dark mode toggle). |
-| `/headerContent` | The PageSidebarLayout header content area (the header slot row). |
 | `/logo` | The PageSidebarLayout logo. |
 | `/notifications` | The notification bell button. |
 | `/notificationsBadge` | The notification badge wrapper. |

package/content/controls/reject.md

@@ -7,9 +7,7 @@
 The `:reject` control is used to return a user-friendly error to the client when validation fails or business rules are violated.
 Unlike [`:throw`](/:throw), which indicates a system error, `:reject` represents an expected failure condition that should be communicated to the user.
 The control immediately stops routine execution and returns with a `"reject"` status.
-Importantly, `:reject` does not trigger `:catch` blocks in [`:try`](/:try) statements: the reject flows past every enclosing `:try`, so a `:catch` in an outer `:try` never runs either, while `:finally` still runs.
-This makes `:reject` ideal for handling validation and business logic errors separately from system errors.
-Choose [`:throw`](/:throw) when a step failed and the routine may recover; choose `:reject` when the routine decided the request cannot be fulfilled.
+Importantly, `:reject` does not trigger `:catch` blocks in [`:try`](/:try) statements, making it ideal for handling validation and business logic errors separately from system errors.
 
 #### Keys
 

package/content/controls/throw.md

@@ -8,7 +8,6 @@ The `:throw` control creates a system error that immediately stops routine execu
 Unlike [`:reject`](/:reject), which handles expected user errors, `:throw` is designed for unexpected system failures, programming errors, or critical issues that require attention.
 The key difference is that `:throw` can be caught and handled by [`:try`](/:try)/`:catch` blocks, while [`:reject`](/:reject) cannot.
 This makes `:throw` ideal for recoverable system errors where you might want to implement fallback logic.
-Choose `:throw` when a step failed and the routine may recover; choose [`:reject`](/:reject) when the routine decided the request cannot be fulfilled.
 
 #### Keys
 

package/content/controls/try.md

@@ -7,13 +7,12 @@
 If one control in the routine chain defined in the `:try` key fails by throwing an error, the steps in the list following the failed control will not be executed.
 To handle any errors thrown by a routine element, a routine can be provided using `catch` key.
 The routine defined using the `:finally` key will be run regardless of whether or not the routine throws an error.
-A [`:reject`](/:reject) inside the `:try` routine is __not__ caught. `:reject` is the routine's own reply — it stops the routine, returns a `"reject"` status to the caller, and flows past every enclosing `:catch`. `:finally` still runs. Use [`:throw`](/:throw) for failures a `:catch` should handle.
 
 #### Keys
 
 - `:try: routine`: __Required__ - The routine to be run.
-- `:catch: routine`: The routine to execute if any step in the routine defined errors. Runs on a thrown error only — a `:reject` is not caught.
-- `:finally: routine`: The routine to be run regardless of the out come of the initial routine. Runs on success, error and reject.
+- `:catch: routine`: The routine to execute if any step in the routine defined errors.
+- `:finally: routine`: The routine to be run regardless of the out come of the initial routine.
 
 #### Examples
 

package/content/display-blocks/difflist.md

@@ -1,6 +1,6 @@
 # DiffList
 
-`DiffList` renders a polished, user-friendly diff between a `before` and an `after` object as a grouped table of changes. Built on `microdiff` for the diff engine and antd primitives for rendering, it groups changes by top-level key, tags each row as Added / Removed / Changed, and supports per-path value formatters (`date`, `datetime`, `boolean`, `currency`, `enum`, `json`, `code`), humanised `labels`, and `hide` / `show` glob filtering. All colours come from antd's semantic tokens so dark mode and `theme` overrides work automatically.
+`DiffList` renders a polished, user-friendly diff between a `before` and an `after` object as a grouped table of changes. Built on `microdiff` for the diff engine and antd primitives for rendering, it groups changes by top-level key, tags each row as Added / Removed / Changed, and supports per-path value formatters (`date`, `datetime`, `boolean`, `currency`, `enum`, `json`, `code`), humanised `labels`, and `hide` / `show` glob filtering. All colours come from antd's semantic tokens so dark mode and `theme` overrides work automatically.
 
 ```yaml
 - id: diff_list_profile

package/content/display-blocks/difftimeline.md

@@ -1,6 +1,6 @@
 # DiffTimeline
 
-`DiffTimeline` renders a diff as a vertical audit trail using Ant Design's `Timeline` component. Each change becomes a timeline entry with a colour-coded dot (green for added, red for removed, blue for changed) and a breadcrumb-style label that shows the full path to the changed field. Uses the same filtering, labelling, and per-path value formatters as `DiffList`.
+`DiffTimeline` renders a diff as a vertical audit trail using Ant Design's `Timeline` component. Each change becomes a timeline entry with a colour-coded dot (green for added, red for removed, blue for changed) and a breadcrumb-style label that shows the full path to the changed field. Uses the same filtering, labelling, and per-path value formatters as `DiffList`.
 
 ```yaml
 - id: diff_timeline_order

package/content/display-blocks/s3download.md

@@ -1,6 +1,6 @@
 # S3Download
 
-__Deprecated__ — use the provider-neutral <a href="/Download">Download</a> block with `downloadPolicyRequestId` instead. S3Download remains as an alias so existing apps keep working. Download files from AWS S3. Requires an AwsS3Bucket connection and an AwsS3PresignedGetObject request. The s3GetPolicyRequestId property must reference the request id. If files were uploaded with S3Upload, its fileList value can be mapped directly to this block.
+__Deprecated__ — use the provider-neutral &lt;a href=&quot;/Download&quot;&gt;Download&lt;/a&gt; block with `downloadPolicyRequestId` instead. S3Download remains as an alias so existing apps keep working. Download files from AWS S3. Requires an AwsS3Bucket connection and an AwsS3PresignedGetObject request. The s3GetPolicyRequestId property must reference the request id. If files were uploaded with S3Upload, its fileList value can be mapped directly to this block.
 
 > The S3Download block requires an AwsS3Bucket connection and an AwsS3PresignedGetObject request. The examples below show configuration structure but will not download files without a configured connection.
 

package/content/display-blocks/search.md

@@ -356,6 +356,5 @@ See the [MiniSearch API docs](https://lucaong.github.io/minisearch/classes/MiniS
 | `/itemDescription` | The description/snippet in a result item. |
 | `/highlight` | Highlighted match text (<mark> elements). |
 | `/empty` | The empty state message. |
-| `/loading` | The loading spinner container. |
 
 No slots defined.

package/content/input-blocks/checkboxselector.md

@@ -703,89 +703,13 @@ Checkbox group for selecting multiple options.
     valueKey: id
 ```
 
-```yaml
-- id: columns_two
-  type: CheckboxSelector
-  properties:
-    title: Two columns
-    columns: 2
-    options:
-      - Weekday mornings
-      - Weekday afternoons
-      - Weekday evenings
-      - Weekend mornings
-      - Weekend afternoons
-      - Weekend evenings
-- id: columns_four
-  type: CheckboxSelector
-  properties:
-    title: Four columns
-    columns: 4
-    options:
-      - January
-      - February
-      - March
-      - April
-      - May
-      - June
-      - July
-      - August
-- id: columns_responsive
-  type: CheckboxSelector
-  properties:
-    title: One column below md, three from md up
-    columns:
-      xs: 1
-      md: 3
-    options:
-      - Email
-      - SMS
-      - Push notification
-      - Webhook
-      - In-app message
-      - Weekly digest
-- id: columns_gutter
-  type: CheckboxSelector
-  properties:
-    title: Wider gutter
-    columns: 2
-    gutter:
-      - 24
-      - 12
-    options:
-      - Read
-      - Write
-      - Delete
-      - Administer
-- id: columns_per_option_color
-  type: CheckboxSelector
-  properties:
-    title: Coloured options in a grid
-    columns: 2
-    options:
-      - label: Low
-        value: low
-        color: "#16a34a"
-      - label: Medium
-        value: medium
-        color: "#d97706"
-      - label: High
-        value: high
-        color: "#dc2626"
-      - label: Critical
-        value: critical
-        color: "#7e22ce"
-```
-
 | Property | Type | Default | Description |
 | --- | --- | --- | --- |
-| `align` | string | `"start"` | Align options. Ignored when 'columns' is set. Enum: `start`, `end`, `center`, `baseline`. |
+| `align` | string | `"start"` | Align options. Enum: `start`, `end`, `center`, `baseline`. |
 | `color` | string | - | Selected checkbox color. |
-| `columns` | integer \| object | - | Number of columns to lay the options out in, or a responsive breakpoint object. Use a count that divides 24 evenly. |
 | `disabled` | boolean | `false` | Disable the block if true. |
-| `direction` | string | `"horizontal"` | List options horizontally or vertical. Ignored when 'columns' is set. Enum: `horizontal`, `vertical`. |
-| `gutter` | number \| array | - | Gap between options in the grid. Number or [horizontal, vertical] array. Applies when 'columns' is set. |
-| `wrap` | boolean | `true` | Specifies wrapping of options. Applies when 'direction' is 'horizontal'. Ignored when 'columns' is set. |
+| `direction` | string | `"horizontal"` | List options horizontally or vertical. Enum: `horizontal`, `vertical`. |
+| `wrap` | boolean | `true` | Specifies wrapping of options. Applies when 'direction' is 'horizontal'. |
 | `options` | array | `[]` | Options can either be an array of primitive values, on an array of label, value pairs - supports html. |
 | `options.$.label` | string | - | Value label shown to user - supports html. |
 | `options.$.value` | string \| number \| boolean | - | Option value. |
@@ -822,7 +746,7 @@ Checkbox group for selecting multiple options.
 | `theme.lineWidth` | number | `1` | Border width of the checkbox. |
 | `theme.lineType` | string | `"solid"` | Border style of the checkbox. |
 | `theme.fontSize` | number | `14` | Font size for checkbox labels. |
-| `theme.marginXS` | number | `8` | Column gap on the checkbox group element. Does not space the options apart; set 'gutter' for a grid. |
+| `theme.marginXS` | number | `8` | Horizontal gap between checkboxes in a group. |
 | `theme.paddingXS` | number | `8` | Inline padding between the checkbox and its label text. |
 
 | Event | Event Data | Description |

package/content/input-blocks/radioselector.md

@@ -752,75 +752,13 @@ Radio group for selecting a single option.
     valueKey: id
 ```
 
-```yaml
-- id: radio_columns_two
-  type: RadioSelector
-  properties:
-    title: Two columns
-    columns: 2
-    options:
-      - Weekday mornings
-      - Weekday afternoons
-      - Weekday evenings
-      - Weekend mornings
-      - Weekend afternoons
-      - Weekend evenings
-- id: radio_columns_responsive
-  type: RadioSelector
-  properties:
-    title: One column below md, three from md up
-    columns:
-      xs: 1
-      md: 3
-    options:
-      - Email
-      - SMS
-      - Push notification
-      - Webhook
-      - In-app message
-      - Weekly digest
-- id: radio_columns_gutter
-  type: RadioSelector
-  properties:
-    title: Wider gutter
-    columns: 2
-    gutter:
-      - 24
-      - 12
-    options:
-      - Read only
-      - Read and write
-      - Administer
-      - No access
-- id: radio_columns_per_option_color
-  type: RadioSelector
-  properties:
-    title: Coloured options in a grid
-    columns: 2
-    options:
-      - label: Low
-        value: low
-        color: "#16a34a"
-      - label: Medium
-        value: medium
-        color: "#d97706"
-      - label: High
-        value: high
-        color: "#dc2626"
-      - label: Critical
-        value: critical
-        color: "#7e22ce"
-```
-
 | Property | Type | Default | Description |
 | --- | --- | --- | --- |
-| `align` | string | `"start"` | Align options. Ignored when 'columns' is set. Enum: `start`, `end`, `center`, `baseline`. |
+| `align` | string | `"start"` | Align options. Enum: `start`, `end`, `center`, `baseline`. |
 | `color` | string | - | Selected radio color. |
-| `columns` | integer \| object | - | Number of columns to lay the options out in, or a responsive breakpoint object. Use a count that divides 24 evenly. |
 | `disabled` | boolean | `false` | Disable the block if true. |
-| `direction` | string | `"horizontal"` | List options horizontally or vertical. Ignored when 'columns' is set. Enum: `horizontal`, `vertical`. |
-| `gutter` | number \| array | - | Gap between options in the grid. Number or [horizontal, vertical] array. Applies when 'columns' is set. |
-| `wrap` | boolean | `true` | Specifies wrapping of options. Applies when 'direction' is 'horizontal'. Ignored when 'columns' is set. |
+| `direction` | string | `"horizontal"` | List options horizontally or vertical. Enum: `horizontal`, `vertical`. |
+| `wrap` | boolean | `true` | Specifies wrapping of options. Applies when 'direction' is 'horizontal'. |
 | `label` | object | - | Label properties. |
 | `label.align` | string | `"left"` | Align label left or right when inline. Enum: `left`, `right`. |
 | `label.colon` | boolean | `true` | Append label with colon. |

package/content/input-blocks/s3uploadbutton.md

@@ -1,6 +1,6 @@
 # S3UploadButton
 
-__Deprecated__ — use the provider-neutral <a href="/Upload">Upload</a> block with `uploadPolicyRequestId` instead. S3UploadButton remains as an alias so existing apps keep working. Upload files to AWS S3 with a button trigger. Supports file type filtering, upload limits, and custom button styling. Requires an `AwsS3PresignedPostPolicy` request to define the S3 upload policy.
+__Deprecated__ — use the provider-neutral &lt;a href=&quot;/Upload&quot;&gt;Upload&lt;/a&gt; block with `uploadPolicyRequestId` instead. S3UploadButton remains as an alias so existing apps keep working. Upload files to AWS S3 with a button trigger. Supports file type filtering, upload limits, and custom button styling. Requires an `AwsS3PresignedPostPolicy` request to define the S3 upload policy.
 
 > The S3UploadButton requires an AwsS3Bucket connection and AwsS3PresignedPostPolicy request to upload files. The examples on this page demonstrate UI configuration only — uploads will not function without a configured S3 connection.
 

package/content/input-blocks/s3uploaddragger.md

@@ -1,6 +1,6 @@
 # S3UploadDragger
 
-__Deprecated__ — use the provider-neutral <a href="/UploadDragger">UploadDragger</a> block with `uploadPolicyRequestId` instead. S3UploadDragger remains as an alias so existing apps keep working. Drag-and-drop file upload area for AWS S3. Supports file type filtering, upload limits, custom drag zone styling, and paste-to-upload. Requires an `AwsS3PresignedPostPolicy` request to define the S3 upload policy.
+__Deprecated__ — use the provider-neutral &lt;a href=&quot;/UploadDragger&quot;&gt;UploadDragger&lt;/a&gt; block with `uploadPolicyRequestId` instead. S3UploadDragger remains as an alias so existing apps keep working. Drag-and-drop file upload area for AWS S3. Supports file type filtering, upload limits, custom drag zone styling, and paste-to-upload. Requires an `AwsS3PresignedPostPolicy` request to define the S3 upload policy.
 
 > The S3UploadDragger requires an AwsS3Bucket connection and AwsS3PresignedPostPolicy request to upload files. The examples on this page demonstrate UI configuration only — uploads will not function without a configured S3 connection.
 

package/content/input-blocks/s3uploadphoto.md

@@ -1,6 +1,6 @@
 # S3UploadPhoto
 
-__Deprecated__ — use the provider-neutral <a href="/UploadPhoto">UploadPhoto</a> block with `uploadPolicyRequestId` instead. S3UploadPhoto remains as an alias so existing apps keep working. Picture-card style image upload for AWS S3. Displays a camera icon with upload text in a card format. Only accepts image files. Requires an `AwsS3PresignedPostPolicy` request to define the S3 upload policy.
+__Deprecated__ — use the provider-neutral &lt;a href=&quot;/UploadPhoto&quot;&gt;UploadPhoto&lt;/a&gt; block with `uploadPolicyRequestId` instead. S3UploadPhoto remains as an alias so existing apps keep working. Picture-card style image upload for AWS S3. Displays a camera icon with upload text in a card format. Only accepts image files. Requires an `AwsS3PresignedPostPolicy` request to define the S3 upload policy.
 
 > The S3UploadPhoto requires an AwsS3Bucket connection and AwsS3PresignedPostPolicy request to upload files. The examples on this page demonstrate UI configuration only — uploads will not function without a configured S3 connection.
 

package/content/input-blocks/tiptapmentioninput.md

@@ -1,6 +1,6 @@
 # TiptapMentionInput
 
-Rich-text editor with @-mention support. Same feature set as TiptapInput, plus a mention dropdown populated from a static options list or a request. Mention options can be marked as groups (roles, teams, queues) to render under their own menu section, as distinctly coloured chips, and with a hover popover listing the group's current members. See the guide below.
+Rich-text editor with @-mention support. Same feature set as TiptapInput, plus a mention dropdown populated from a static options list or a request. Mention options can be marked as groups (roles, teams, queues) to render under their own menu section, as distinctly coloured chips, and with a hover popover listing the group's current members. See the guide below.
 
 ## Group mentions
 

package/content/list-blocks/masonrylist.md

@@ -1,6 +1,6 @@
 # MasonryList
 
-Masonry-style grid layout for list data. Items flow into columns and stack vertically, filling gaps left by shorter items. Provide an array in state and use _state operators in the template to access each item's data.
+Masonry-style grid layout for list data. Items flow into columns and stack vertically, filling gaps left by shorter items. Provide an array in state and use _state operators in the template to access each item's data.
 
 ```yaml
 - id: ml_basic

package/content/operators/_type.md

@@ -29,7 +29,6 @@ The regex operator has shorthand argument definitions that can be used on web cl
     - `null`
     - `undefined`
     - `none` (`null` or `undefined`)
-    - `empty` (`null`, `undefined`, `''`, or `[]` - note that `0`, `false` and `{}` are not empty)
     - `primitive` (`undefined`, `null`, `string`, `number`, `boolean`, or `date`)
   - `on: any`: The value to test. One of `on` or `key` must be specified unless the operator is used in an input block.
   - `key: string`: The key of a value in `state` to test. One of `on` or `key` must be specified unless the operator is used in an input block.
@@ -61,23 +60,13 @@ Returns: `true` if a number.
 id: input
 type: TextInput
 validate:
-  - message: This field is required.
+  - message: This field id required.
     status: error
     pass:
       _not:
-        _type: empty
+        _type: none
 ```
-Returns: `true` if the input has a value. This is the test the `required` block field applies.
-
-###### Check if a value is empty:
-```yaml
-_type:
-  type: empty
-  on:
-    _state: selected_tags
-```
-Returns: `true` if `selected_tags` is `null`, `undefined`, `''` or `[]`, and `false` for any
-other value, including `0`, `false` and `{}`.
+Returns: `true` if the input is none.
 
 ###### Test if an id in the `urlQuery` is undefined or null:
 ```yaml

package/content/operators/_user.md

@@ -10,7 +10,7 @@
 }): any
 ```
 
-The `_user` operator gets a value from the [`user`](/user-object) object — the caller Lowdefy resolves for the signed-in user in their active organization. It has a [fixed shape](/user-object); see that page for the available fields.
+The `_user` operator gets a value from the [`user`](/user-object) object. The `user` object contains the data in the user idToken if OpenID Connect authentication is configured and a user is logged in.
 
 #### Arguments
 
@@ -50,7 +50,7 @@ Returns: The entire `user` object.
 ###### Dot notation:
 Assuming user:
 ```yaml
-id: abc123
+sub: abc123
 name: User Name
 my_object:
   subfield: 'Value'
@@ -76,7 +76,7 @@ Returns: The value of `might_not_exist`, or `"Default value"`.
 ###### Block list indices:
 Assuming `user`:
 ```yaml
-id: abc123
+sub: abc123
 name: User Name
 my_array:
   - value: 0

package/content/user-authentication/login-and-logout.md

@@ -8,19 +8,15 @@ The `Login` action is used to start the user login flow. If only one OAuth provi
 
 The authorization url usually hosts a page where the user can input their credentials. After the user has logged in successfully, the user is redirected to the `/api/auth/callback/<provider_id>` route in the Lowdefy app, where the rest of the authorization code flow is completed. This URL usually needs to be configured in the identity provider's settings.
 
-The `callbackUrl` parameter of the Login action specifies where the user lands after login is complete. Three sources are consulted, in order: the `callbackUrl` param, then the `?callbackUrl=` query parameter Lowdefy sets when it redirects an unauthenticated user to the sign-in page, then the app's home page. If none resolves the action throws, rather than staying silently on the sign-in page.
-
-In a protected app a signed-out visitor is sent to the sign-in page for every URL, present or absent, so a `404` means you are signed in — see [Page and API existence](/auth-upgrade#page-and-api-existence-is-no-longer-observable-before-you-sign-in).
-
-To sign in without navigating at all - a login form in a modal, or an embedded panel - set `callbackUrl: false`. This is not valid for magic-link or social/OAuth sign-in, which redirect through a hop Lowdefy does not control.
+The `callbackUrl` parameters of the Login action specify where the user is redirected after login is complete. If `callbackUrl` parameters not set, the user will return to the page from which the action was called.
 
 The parameters are:
 - `authUrl: object`:
   - `urlQuery: object`: Query parameters to set for the authorization URL.
-- `callbackUrl: object | false`: Set to `false` to sign in without navigating. As an object:
+- `callbackUrl: object`:
   - `home: boolean`: Redirect to the home page after the login flow is complete.
   - `pageId: string`: The pageId of the page to redirect to after the login flow is complete.
-  - `url: string`: The URL to redirect to after the login flow is complete. An absolute URL is not `basePath`-prefixed, so it can be an external landing page.
+  - `url: string`: The URL to redirect to after the login flow is complete.
   - `urlQuery: object`: The urlQuery to set for the page the user is redirected to after login.
 - `providerId: string`: The ID of the provider that should be used for login. If not set and only one provider is configured the configured provider will be used. Else the user will be redirected to a sign in page where they can choose a provider.
 
@@ -95,164 +91,18 @@ events:
             screen_hint: signup
 ```
 
-## Magic link sign-in
-
-`Login` with `magicLink: true` emails the user a sign-in link. By default that link points straight at Better Auth's verify endpoint, which consumes the single-use token on the first `GET` of the URL.
-
-That is a problem in corporate inboxes. Mail security products — Microsoft Defender Safe Links, Proofpoint URL Defense, Mimecast — fetch every link in a message as it is delivered, so the scanner spends the token minutes before the person clicks, and the person lands on the error page with `INVALID_TOKEN`.
-
-Set [`auth.authPages.magicLink`](/auth-configuration#auth-pages) to a page in your app to close that gap. The email then links to your page, carrying the token and the callback destinations on its URL query, and a [`MagicLinkVerify`](/MagicLinkVerify) action on a **button click** walks to the verify endpoint. Fetching the landing page does nothing, so a scanner cannot consume the token.
-
-```yaml
-lowdefy: {{ version }}
-auth:
-  magicLink:
-    enabled: true
-  authPages:
-    magicLink: /magic-link
-```
-
-```yaml
-id: magic-link
-type: PageHeaderMenu
-blocks:
-  - id: content
-    type: Box
-    blocks:
-      - id: title
-        type: Title
-        properties:
-          content: Sign in
-          level: 3
-      - id: description
-        type: Paragraph
-        properties:
-          content: Click the button below to finish signing in.
-      - id: verify_button
-        type: Button
-        properties:
-          title: Sign in
-        events:
-          onClick:
-            - id: verify
-              type: MagicLinkVerify
-```
-
-The landing page must be reachable while signed out, so add it to `auth.pages.public`.
-
-Do **not** run `MagicLinkVerify` in the page's `onMount`, and do not auto-redirect to the verify endpoint. Some scanning sandboxes render the page and execute its JavaScript, so an automatic verify hands the token back to the scanner and you are no better off than linking at the endpoint directly. The whole protection is that a human has to click.
-
-The action needs no parameters: the token and the `callbackURL`, `newUserCallbackURL` and `errorCallbackURL` values are read from the landing page's own URL query, which the email put there. Pass parameters only to override them.
-
-## Email code sign-in
-
-With `auth.emailOTP` enabled the app can sign a person in with a code emailed to them. Unlike a magic link, the code is typed into the tab they started from — so it survives corporate mail security that pre-fetches links (and consumes the single-use link token), and it works when the email is read on another device.
-
-Two actions drive it:
-
-- [`EmailOtpSend`](/EmailOtpSend) sends the code to an email address.
-- [`EmailOtpVerify`](/EmailOtpVerify) signs the person in with the code they typed.
-
-`EmailOtpVerify` lands the user through the same three sources as `Login`: the `callbackUrl` param, then the `?callbackUrl=` query, then the app's home page. `callbackUrl: false` verifies without navigating — it is a plain JSON sign-in with no redirect hop, so staying put is valid here.
-
-### With magic link, one email carries both
-
-When `auth.magicLink` is enabled alongside `auth.emailOTP`, the magic-link email also carries the code, so one email serves both paths. Keep using `Login` with `magicLink: true` to send it — no change is needed — and offer `EmailOtpVerify` on the same page for people whose link does not work. `EmailOtpSend` is then only needed for a code-only page, where no link is offered at all.
-
-###### A sign-in page offering a code:
-```yaml
-id: email-code-login
-type: Box
-blocks:
-  - id: email
-    type: TextInput
-    required: true
-    properties:
-      title: Email
-  - id: send_code
-    type: Button
-    properties:
-      title: Send code
-    events:
-      onClick:
-        - id: validate
-          type: Validate
-          params:
-            regex: ^email$
-        - id: send
-          type: EmailOtpSend
-          params:
-            email:
-              _state: email
-        - id: sent
-          type: DisplayMessage
-          params:
-            content: Check your email for the sign-in code.
-  - id: otp
-    type: TextInput
-    properties:
-      title: Sign-in code
-  - id: sign_in
-    type: Button
-    properties:
-      title: Sign in
-    events:
-      onClick:
-        - id: verify
-          type: EmailOtpVerify
-          params:
-            email:
-              _state: email
-            otp:
-              _state: otp
-```
-
-An expired, mistyped or already-used code is the auth server rejecting the attempt, not an app fault: the action throws a `UserError`, so `onClick` `catch` actions run and the message displays, but nothing is reported to the server.
-
-## SMS sign-in
-
-`PhoneNumberVerify` completes a sign-in with an SMS code, and lands the user through the same three sources as `Login`: the `callbackUrl` param, then the `?callbackUrl=` query, then the app's home page. `callbackUrl: false` verifies without navigating.
-
-Two modes are exempt, because neither ends with the user arriving somewhere new:
-
-- `disableSession: true` creates no session to arrive with.
-- `updatePhoneNumber: true` is a signed-in user confirming a new number. They already had a session, and the confirmation usually runs in a modal a navigation would yank them out of.
-
-### Carrying the destination to a separate SMS form
-
-The `?callbackUrl=` query is read from the page the action runs on, and the unauthenticated bounce puts it on `authPages.signIn`. If your SMS form lives on its own page, the link that gets the user there has to carry the parameter, or the destination falls back to the home page:
-
-```yaml
-- id: to_phone_login
-  type: Link
-  params:
-    pageId: phone-login
-    urlQuery:
-      _if:
-        test:
-          _eq:
-            - _url_query: callbackUrl
-            - null
-        then: null
-        else:
-          callbackUrl:
-            _url_query: callbackUrl
-```
-
-The `_if` is what keeps a user who reached the sign-in page directly from being sent to `/phone-login?callbackUrl=null` — `urlQuery` serialises a null value rather than dropping the key.
-
 ## Logout
 
 When the `Logout` action is called, the user data and authorization cookies are cleared by the app.
 
-The `callbackUrl` parameter of the Logout action specifies where the user lands after logout is complete. Unlike the `Login` action it has no default and does not read the `?callbackUrl=` query: with no `callbackUrl` the page is reloaded and the server re-applies the page's auth rules, which sends a signed-out user off a protected page to the sign-in page.
+The `callbackUrl` parameters of the Logout action specify where the user is redirected after logout is complete. If `callbackUrl` parameters are not set, the user will return to the page from which the action was called.
 
 The parameters are:
 - `callbackUrl: object`:
-  - `home: boolean`: Redirect to the home page after the logout flow is complete.
-  - `pageId: string`: The pageId of the page to redirect to after the logout flow is complete.
-  - `url: string`: The URL to redirect to after the logout flow is complete. An absolute URL is not `basePath`-prefixed, so it can be an external logout landing page.
-  - `urlQuery: object`: The urlQuery to set for the page the user is redirected to after logout.
+  - `home: boolean`: Redirect to the home page after the login flow is complete.
+  - `pageId: string`: The pageId of the page to redirect to after the login flow is complete.
+  - `url: string`: The URL to redirect to after the login flow is complete.
+  - `urlQuery: object`: The urlQuery to set for the page the user is redirected to after login.
 - `redirect: boolean`: If set to `false` the user session will be cleared, but the page will not be reloaded.
 
 

package/content/user-authentication/users-introduction.md

@@ -29,11 +29,3 @@ The Login and Logout actions are used to start the login and logout processes.
 ## \_user operator
 
 The `_user` operator can be used to access data in the user object received from the identity provider. The OpenID Connect standard claims (fields like `name` or `email`) are mapped to the user object by default and addition fields can be configured using the `userFields` configuration option.
-
-### `two_factor_enrolled`
-
-`_user: two_factor_enrolled` is `true` when the caller holds a factor that satisfies [`auth.twoFactor.required`](/two-factor) — a TOTP enrolment **or** a registered passkey.
-
-It is a fact about the **user**, not the session: it does not assert that a factor was presented on this sign-in, only that the user has one on file. (The name is imperfect — a passkey is not literally a second factor. The field means precisely "holds a factor that satisfies `auth.twoFactor.required`", which a passkey does on its own.)
-
-It is present only on session-resolved callers. The API strategy and the injected callers used in dev and e2e carry no session and so do not carry this field.