From f40d96a9b92c190517ce6956592ee76ec1ff87bd Mon Sep 17 00:00:00 2001 From: Carlos Fung Date: Wed, 13 May 2026 15:13:29 +0200 Subject: [PATCH 1/8] Update customize-signup-and-login-prompts.mdx --- .../customize-signup-and-login-prompts.mdx | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx b/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx index 996c19b271..c423f74207 100644 --- a/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx +++ b/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx @@ -45,7 +45,6 @@ The following prompts can be customized: * `signup` * `signup-id` * `signup-password` -* `customized-consent` * `passkey-enrollment` * `passkey-enrollment-local` @@ -336,6 +335,10 @@ When using a database connection: * Data from the Signup Prompts is accessible on the [`pre-user-registration`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/pre-user-registration-trigger) trigger. A validation error from the trigger prevents the user from registering. * Data from Login Prompts is accessible on the [`post-login`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger) trigger. Validation errors are forwarded to the customer’s application error page. +When using a custom datatabe connection: + +* Data from from both the Signup and Login Prompts is accessible only for `create user`, `get user`, and `password`. + When using a Passwordless connection: * Data from both the Signup and Login Prompts is accessible on the [`post-login`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger) trigger. Validation errors are forwarded to the customer’s application error page. @@ -346,6 +349,10 @@ When using `passkey` prompts: * The `passkey-enrollment` and `passkey-enrollment-local` prompts never capture data on the Post Login trigger. * Data from the `passkey-enrollment-local` prompt is not accessible since it is always displayed after the [`post-login`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger) trigger is run. +When using social or enterprise connections: + +* Data is not captured when a user logs in with either a [social](/docs/authenticate/identity-providers/social-identity-providers) or an [enterprise](/docs/authenticate/enterprise-connections) connection. + Sanitize any data that you collect on the form before saving or rendering it. From d6cf76b6b68d299777509ea96eba85d2602212c7 Mon Sep 17 00:00:00 2001 From: Carlos Fung Date: Wed, 13 May 2026 15:17:46 +0200 Subject: [PATCH 2/8] Update customize-signup-and-login-prompts.mdx --- .../universal-login/customize-signup-and-login-prompts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx b/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx index c423f74207..0644269e29 100644 --- a/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx +++ b/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx @@ -337,7 +337,7 @@ When using a database connection: When using a custom datatabe connection: -* Data from from both the Signup and Login Prompts is accessible only for `create user`, `get user`, and `password`. +* Data from from both the Signup and Login Prompts is accessible only for `create user`, `get user`, and `password reset` scripts. When using a Passwordless connection: From 167d664a681b99486dfbfb3c00c434381e82720e Mon Sep 17 00:00:00 2001 From: Carlos Date: Wed, 13 May 2026 15:32:06 +0200 Subject: [PATCH 3/8] fix: correct two typos in customize-signup-and-login-prompts MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - datatabe → database - from from → from Co-Authored-By: Claude Opus 4.6 --- .../universal-login/customize-signup-and-login-prompts.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx b/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx index 0644269e29..e23d8b232a 100644 --- a/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx +++ b/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx @@ -335,9 +335,9 @@ When using a database connection: * Data from the Signup Prompts is accessible on the [`pre-user-registration`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/pre-user-registration-trigger) trigger. A validation error from the trigger prevents the user from registering. * Data from Login Prompts is accessible on the [`post-login`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger) trigger. Validation errors are forwarded to the customer’s application error page. -When using a custom datatabe connection: +When using a custom database connection: -* Data from from both the Signup and Login Prompts is accessible only for `create user`, `get user`, and `password reset` scripts. +* Data from both the Signup and Login Prompts is accessible only for `create user`, `get user`, and `password reset` scripts. When using a Passwordless connection: From e30ec17f97f2a3266eb142a490c9a6e3ba3301d0 Mon Sep 17 00:00:00 2001 From: Carlos Date: Wed, 13 May 2026 16:20:36 +0200 Subject: [PATCH 4/8] fix(DOCS-5493): review and fix customize-signup-and-login-prompts.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Promote all #### and ##### headings to ## and ### for Mintlify ToC visibility - Fix typo: prompt.screen.texts → prompt.screen.text - Complete incomplete sentence in Validate and Save section - Fix image alt text for partials editor screenshot - Replace all four blocks with per component standards - Fix mixed JSON/bash code block: split into bash request + prose + json response - Strip trailing whitespace and reduce excessive blank lines Co-Authored-By: Claude Opus 4.6 --- .../customize-signup-and-login-prompts.mdx | 106 +++++++----------- 1 file changed, 40 insertions(+), 66 deletions(-) diff --git a/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx b/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx index e23d8b232a..cb8f749c2b 100644 --- a/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx +++ b/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx @@ -13,7 +13,7 @@ title: Customize Signup and Login Prompts **Customize Signup and Login Prompts** is a feature that allows customers with Custom Domain and Custom Page Template enabled to add custom fields and content to their app’s signup and login prompts. -#### Use Cases +## Use Cases Customize Signup and Login Prompts supports two use cases: **custom content** and **data capture.** @@ -21,12 +21,11 @@ Customize Signup and Login Prompts supports two use cases: **custom content** an **Data capture** uses form elements dynamically added to the signup and login prompts, which is useful for collecting and validating user consent or user-produced data like surname. - - + Only use Signup and Login Prompt Customizations to convey or collect sensitive or regulated data as permitted under your agreement with Okta. - + -#### Terminology +## Terminology A **prompt** is a specific step in a given authentication flow. Each prompt has at least one **screen** and, depending on tenant configuration, each supported screen has either four or six **entry points,** which are locations in the screen where custom code (**partials**) can be inserted. @@ -64,42 +63,42 @@ The following entry points are available when at least one social or enterprise ![Screenshots of each Custom Prompt option and their partials](/docs/images/cdy7uua7fh8z/7sQVWVbaTp4VMW4nJjsn2G/74d0b30da7b034bd695274dbd146964b/Custom_Prompts.png) -#### Use the Auth0 Dashboard to manage Partials +## Use the Auth0 Dashboard to manage Partials Use the Dashboard to insert custom fields and content into Login and Signup screens using partials. 1. Navigate to [Auth0 Dashboard > Branding > Universal Login](https://manage.auth0.com/#/universal-login/customize-partials), and select **Enhance screens with partials**. -2. Select the **Screen** to customize with the partials editor. +2. Select the **Screen** to customize with the partials editor. **Screens** can have the following **Rendering modes**: -* **STANDARD**: The `screen` is rendered using the default [Universal Login](/docs/customize/login-pages/universal-login) UI; you can use partials to insert code snippets and [template variables](/docs/customize/login-pages/universal-login/customize-templates#page-template-variables). +* **STANDARD**: The `screen` is rendered using the default [Universal Login](/docs/customize/login-pages/universal-login) UI; you can use partials to insert code snippets and [template variables](/docs/customize/login-pages/universal-login/customize-templates#page-template-variables). * **ADVANCED**: The `screen` is rendered using [ACUL](/docs/customize/login-pages/advanced-customizations) and partials do not apply. * **ADVANCED (FILTERED)**: The `screen` is rendered with ACUL applied to specific applications and organizations; partials only apply to `screens` excluded from ACUL filters. -3. Select **** **ENTRY POINTS** to insert code snippets and template variables. +3. Select **** **ENTRY POINTS** to insert code snippets and template variables. -4. Select **** to add **CODE SNIPPETS** to the selected entry point. +4. Select **** to add **CODE SNIPPETS** to the selected entry point. -5. Select **\{ }** to add **TEMPLATE VARIABLES** to the selected entry point. +5. Select **\{ }** to add **TEMPLATE VARIABLES** to the selected entry point. -6. Select **** **ACTIONS** to add [Actions](/docs/customize/actions/actions-overview) and apply custom logic using your partials fields and content. +6. Select **** **ACTIONS** to add [Actions](/docs/customize/actions/actions-overview) and apply custom logic using your partials fields and content. 7. Select **Save and Publish** to update your **Screen**. - ![[partials]](/docs/images/universal-login/partials-editor.png) - -#### Use the Management API to manage Partials +## Use the Management API to manage Partials Partials can be a maximum of 10,000 characters. You can manage Partials using the [Auth0 Management API](https://auth0.com/docs/api/management/v2/prompts/put-partials) at `/v2/prompts/{prompts_name}/partials`. Every prompt must specify the `screen` when adding, updating, or deleting a partial. Below is an example call to view all existing partials for a prompt, noting that `ulp-container` prefix is not required when referencing entry points in API calls. -```json lines +```bash GET /api/v2/prompts/signup-id/partials -# response -# success code: 200 -# not found code: 404 -body: { +``` + +Returns `200` on success, `404` if the prompt is not found. + +```json +{ "signup-id": { "form-content-start": "
HTML or Liquid
...", "form-content-end": "
HTML or Liquid
..." @@ -107,16 +106,11 @@ body: { } ``` - - - - - Partials can also be managed using Auth0 CLI’s Universal Login Customize Interface by running `auth0 ul customize` in your terminal. ![An image showing the command-line interface for Partials. ](/docs/images/cdy7uua7fh8z/KxWfVAMkumyI2jrUqkEp8/b9315709899864a2f8758ad7f5a4f5b2/Partials_CLI_Image.jpg) -#### Style and Validate Form Inputs +## Style and Validate Form Inputs Customize Signup and Login Prompts offers pre-built styles and support for client-side validations for certain HTML form elements. The following elements are supported: @@ -132,7 +126,7 @@ Customize Signup and Login Prompts offers pre-built styles and support for clien To use pre-built input styles, wrap your form element of choice in a `
` with the `ulp-field` class. Similarly, add the `ulp-error` class to the same `
` to use pre-built error styles. If the `ulp-error-info` element is present, a styled error message will also be displayed. -#### Client-Side Validation +### Client-Side Validation The feature's client-side validation framework allows customers to validate user input using HTML attributes to execute one or more custom validation functions. Validation functions can be included directly in the Partial or included in the `` of the page template. @@ -142,7 +136,6 @@ To add client-side validation to a form element: * Declare which DOM events the validation function should be run on using the `data-ulp-validation-event-listeners` attribute on the `
` element, noting that validations run automatically on submission. * For WCAG compliance, inputs must be programmatically linked to their error messages - for example, by using `aria-describedby="error-id"` and `aria-invalid="true"` - to ensure screen readers announce validation errors. - @@ -264,23 +257,19 @@ To add client-side validation to a form element: - - - - + Be cautious when using third-party JavaScript on your signup page. Sensitive security-related information often flows through the signup page, leaving it vulnerable to cross-site scripting. Whenever possible, Auth0 recommends validating user-provided data before submitting. + - - -#### Localize Content +## Localize Content -Partial content can be localized by defining new custom text variables using the [Custom Text API](https://auth0.com/docs/api/management/v2/prompts/put-custom-text-by-language). Up to thirty custom text variables can be defined per screen/language combination. +Partial content can be localized by defining new custom text variables using the [Custom Text API](/docs/api/management/v2/prompts/put-custom-text-by-language). Up to thirty custom text variables can be defined per screen/language combination. -##### Create or Update a Custom Text Variable +### Create or Update a Custom Text Variable -The Custom Text API is available [here](https://auth0.com/docs/api/management/v2/prompts/get-custom-text-by-language) and each variable follows a `var-` naming convention. Calls to the API must specify the screen when adding, updating, or deleting a custom text variable. Markdown links are supported and are converted to HTML `` elements before being displayed to users. +Calls to the Custom Text API must specify the screen when adding, updating, or deleting a custom text variable. Custom text variables follow the `var-` naming convention. Markdown links are supported and are converted to HTML `` elements before being displayed to users. Below is an example call to add a variable for the text of a terms of service checkbox label in English and Spanish. See the Management API to learn more. @@ -300,12 +289,7 @@ Below is an example call to add a variable for the text of a terms of service ch } ``` - - - - - -##### Use a Custom Text Variable in a Partial +### Use a Custom Text Variable in a Partial Custom text variables are referenced in partials using the `prompts.screen.text` object; the reference for the `var-tos` example in the previous section is `prompt.screen.text.varTos`. See below for an example of how to use a previously created variable in a partial on the Signup ID Prompt, noting that the Management API's `var-tos` variable is referenced as `varTos` in the partial. @@ -313,31 +297,28 @@ Custom text variables are referenced in partials using the `prompts.screen.text` # PUT api/v2/prompts/signup/partials
- +
``` +## Validate and Save Captured Data -#### Validate and Save Captured Data - -Data captured by custom form elements is available in Actions, and Auth0 recommends validating the data collected - - +Data captured by custom form elements is available in Actions, and Auth0 recommends validating the data collected before saving or submitting it. + When using custom form elements, you must include the `ulp-` prefix with any input names to ensure the data is available to [Actions](/docs/customize/actions/actions-overview). - - + Each Action receives the captured data as an object on the `event.request.body`. Customers can return a validation error by using the `api.validation.error` function. When using a database connection: -* Data from the Signup Prompts is accessible on the [`pre-user-registration`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/pre-user-registration-trigger) trigger. A validation error from the trigger prevents the user from registering. +* Data from the Signup Prompts is accessible on the [`pre-user-registration`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/pre-user-registration-trigger) trigger. A validation error from the trigger prevents the user from registering. * Data from Login Prompts is accessible on the [`post-login`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger) trigger. Validation errors are forwarded to the customer’s application error page. When using a custom database connection: -* Data from both the Signup and Login Prompts is accessible only for `create user`, `get user`, and `password reset` scripts. +* Data from both the Signup and Login Prompts is accessible only for `create user`, `get user`, and `password reset` scripts. When using a Passwordless connection: @@ -345,16 +326,15 @@ When using a Passwordless connection: When using `passkey` prompts: -* Data from the `passkey-enrollment` prompt is accessible on the [`pre-user-registration`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/pre-user-registration-trigger) trigger. A validation error from the trigger prevents the user from registering. +* Data from the `passkey-enrollment` prompt is accessible on the [`pre-user-registration`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/pre-user-registration-trigger) trigger. A validation error from the trigger prevents the user from registering. * The `passkey-enrollment` and `passkey-enrollment-local` prompts never capture data on the Post Login trigger. * Data from the `passkey-enrollment-local` prompt is not accessible since it is always displayed after the [`post-login`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger) trigger is run. When using social or enterprise connections: -* Data is not captured when a user logs in with either a [social](/docs/authenticate/identity-providers/social-identity-providers) or an [enterprise](/docs/authenticate/enterprise-connections) connection. - - +* Data is not captured when a user logs in with either a [social](/docs/authenticate/identity-providers/social-identity-providers) or an [enterprise](/docs/authenticate/enterprise-connections) connection. + Sanitize any data that you collect on the form before saving or rendering it. * Ensure any data being saved has passed through [Liquid’s `{{escape}}` helper function](https://shopify.github.io/liquid/filters/escape/) @@ -364,10 +344,9 @@ Sanitize any data that you collect on the form before saving or rendering it. * If you pass data into query string, encode with eg: `{{encodeURI}}` or `{{encodeURIParam}}` For more information regarding risk mitigation and best practices for securely storing data see [this cheatsheet](https://cheatsheetseries.owasp.org/cheatsheets/Input_Validation_Cheat_Sheet.html). + - - -##### Save to User Metadata +### Save to User Metadata From the Action, captured data can be sent to an external API for validation and storage or saved in `user_metadata` on the user via `api.user.setUserMetadata`. @@ -389,11 +368,6 @@ exports.onExecutePreUserRegistration = async (event, api) => { }; ``` - - - - - ## Learn more * [Use Dynamic Variables to Internationalize Custom Form Elements](/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts/use-dynamic-variables-to-internationalize-custom-form-elements) From 945fa118a8dc2824cee07280d714b9a97e66768b Mon Sep 17 00:00:00 2001 From: Carlos Fung Date: Mon, 18 May 2026 08:45:28 +0200 Subject: [PATCH 5/8] Update customize-signup-and-login-prompts.mdx --- .../customize-signup-and-login-prompts.mdx | 160 ++---------------- 1 file changed, 16 insertions(+), 144 deletions(-) diff --git a/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx b/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx index cb8f749c2b..e5e3a570ce 100644 --- a/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx +++ b/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx @@ -19,7 +19,7 @@ Customize Signup and Login Prompts supports two use cases: **custom content** an **Custom content** is static content like text, links, or images placed directly on the signup and login prompts. -**Data capture** uses form elements dynamically added to the signup and login prompts, which is useful for collecting and validating user consent or user-produced data like surname. +**Data capture** uses form elements dynamically added to the Signup and Login prompts, which is useful for collecting and validating user consent or user-produced data like surname. Only use Signup and Login Prompt Customizations to convey or collect sensitive or regulated data as permitted under your agreement with Okta. @@ -89,22 +89,7 @@ Use the Dashboard to insert custom fields and content into Login and Signup scre ## Use the Management API to manage Partials -Partials can be a maximum of 10,000 characters. You can manage Partials using the [Auth0 Management API](https://auth0.com/docs/api/management/v2/prompts/put-partials) at `/v2/prompts/{prompts_name}/partials`. Every prompt must specify the `screen` when adding, updating, or deleting a partial. Below is an example call to view all existing partials for a prompt, noting that `ulp-container` prefix is not required when referencing entry points in API calls. - -```bash -GET /api/v2/prompts/signup-id/partials -``` - -Returns `200` on success, `404` if the prompt is not found. - -```json -{ - "signup-id": { - "form-content-start": "
HTML or Liquid
...", - "form-content-end": "
HTML or Liquid
..." - } -} -``` +You can manage Partials using the [Auth0 Management API](https://auth0.com/docs/api/management/v2/prompts/put-partials) (`GET /prompts/{prompts_name}/partials`). Every prompt must specify the `screen` when adding, updating, or deleting a partial. Partials can be a maximum of 10,000 characters. Partials can also be managed using Auth0 CLI’s Universal Login Customize Interface by running `auth0 ul customize` in your terminal. @@ -126,6 +111,8 @@ Customize Signup and Login Prompts offers pre-built styles and support for clien To use pre-built input styles, wrap your form element of choice in a `
` with the `ulp-field` class. Similarly, add the `ulp-error` class to the same `
` to use pre-built error styles. If the `ulp-error-info` element is present, a styled error message will also be displayed. +You can find pre-built code snippets when using the [partials](#use-the-auth0-dashboard-to-manage-partials) editor. + ### Client-Side Validation The feature's client-side validation framework allows customers to validate user input using HTML attributes to execute one or more custom validation functions. Validation functions can be included directly in the Partial or included in the `` of the page template. @@ -136,127 +123,6 @@ To add client-side validation to a form element: * Declare which DOM events the validation function should be run on using the `data-ulp-validation-event-listeners` attribute on the `
` element, noting that validations run automatically on submission. * For WCAG compliance, inputs must be programmatically linked to their error messages - for example, by using `aria-describedby="error-id"` and `aria-invalid="true"` - to ensure screen readers announce validation errors. - - - -```html lines -
- - -
- First Name is Required -
-
-``` - - - - -```html lines -
- - -
- Please Select a Language. -
-
-``` - - - - -```html lines -
- - -
- Please provide an answer. -
-
-``` - - - - -```html lines -
- - Terms of Service - -
- Please agree to the Terms of Service. -
-
-``` - - - - -```javascript lines -// Validation Function - - -// Custom Input Field including the validation error HTML -
- - -
- Invalid phone number -
-
-``` - - - - ```html lines - - -
- - - -
- ``` - - - - Be cautious when using third-party JavaScript on your signup page. Sensitive security-related information often flows through the signup page, leaving it vulnerable to cross-site scripting. @@ -311,20 +177,26 @@ When using custom form elements, you must include the `ulp-` prefix with any inp Each Action receives the captured data as an object on the `event.request.body`. Customers can return a validation error by using the `api.validation.error` function. -When using a database connection: +When using a [database connection](/docs/authenticate/database-connections#use-auth0-user-store): * Data from the Signup Prompts is accessible on the [`pre-user-registration`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/pre-user-registration-trigger) trigger. A validation error from the trigger prevents the user from registering. * Data from Login Prompts is accessible on the [`post-login`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger) trigger. Validation errors are forwarded to the customer’s application error page. -When using a custom database connection: +When using a [custom database connection](/docs/authenticate/database-connections/custom-db): + +* Data from the Signup Prompts is accessible on the [`pre-user-registration`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/pre-user-registration-trigger) trigger with the following custom database action scripts: [Create User](/docs/authenticate/database-connections/custom-db/templates/create) and [Login](/docs/authenticate/database-connections/custom-db/templates/login). -* Data from both the Signup and Login Prompts is accessible only for `create user`, `get user`, and `password reset` scripts. +* Data from Login Prompts is accessible on the [`post-login`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger) trigger with the following custom database action scripts: [Login](/docs/authenticate/database-connections/custom-db/templates/login) and [Change Password](/docs/authenticate/database-connections/custom-db/templates/change-password). + + +To use custom database action scripts, enable **Context objects in database scripts** in your custom database connection. To learn more, read [Enable context object](https://auth0.com/docs/authenticate/database-connections/custom-db/create-db-connection#enable-context-object). + -When using a Passwordless connection: +When using a [Passwordless connection](/docs/authenticate/passwordless/passwordless-with-universal-login): * Data from both the Signup and Login Prompts is accessible on the [`post-login`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger) trigger. Validation errors are forwarded to the customer’s application error page. -When using `passkey` prompts: +When using [`passkey`](/docs/authenticate/database-connections/passkeys) prompts: * Data from the `passkey-enrollment` prompt is accessible on the [`pre-user-registration`](/docs/customize/actions/explore-triggers/signup-and-login-triggers/pre-user-registration-trigger) trigger. A validation error from the trigger prevents the user from registering. * The `passkey-enrollment` and `passkey-enrollment-local` prompts never capture data on the Post Login trigger. @@ -332,7 +204,7 @@ When using `passkey` prompts: When using social or enterprise connections: -* Data is not captured when a user logs in with either a [social](/docs/authenticate/identity-providers/social-identity-providers) or an [enterprise](/docs/authenticate/enterprise-connections) connection. +* Data is *not* captured when a user logs in with either a [social](/docs/authenticate/identity-providers/social-identity-providers) or an [enterprise](/docs/authenticate/enterprise-connections) connection. Sanitize any data that you collect on the form before saving or rendering it. From 5cb9b98d630b816098d9a61813344e23d4e39f84 Mon Sep 17 00:00:00 2001 From: Carlos Fung Date: Mon, 18 May 2026 08:54:36 +0200 Subject: [PATCH 6/8] Update customize-signup-and-login-prompts.mdx --- .../universal-login/customize-signup-and-login-prompts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx b/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx index e5e3a570ce..d4d120c323 100644 --- a/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx +++ b/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx @@ -135,7 +135,7 @@ Partial content can be localized by defining new custom text variables using the ### Create or Update a Custom Text Variable -Calls to the Custom Text API must specify the screen when adding, updating, or deleting a custom text variable. Custom text variables follow the `var-` naming convention. Markdown links are supported and are converted to HTML `` elements before being displayed to users. +Calls to the [Custom Text API](/docs/api/management/v2/prompts/get-custom-text-by-language) must specify the `screen` when adding, updating, or deleting a custom text variable. Custom text variables follow the `var-` naming convention. Markdown links are supported and are converted to HTML `` elements before being displayed to users. Below is an example call to add a variable for the text of a terms of service checkbox label in English and Spanish. See the Management API to learn more. From 6bd430a06f219030cd30ee3be67d6f8b6fa9b276 Mon Sep 17 00:00:00 2001 From: Carlos Fung Date: Mon, 18 May 2026 16:03:19 +0200 Subject: [PATCH 7/8] Update customize-signup-and-login-prompts.mdx --- .../customize-signup-and-login-prompts.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx b/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx index d4d120c323..951e173bf0 100644 --- a/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx +++ b/main/docs/customize/login-pages/universal-login/customize-signup-and-login-prompts.mdx @@ -13,7 +13,7 @@ title: Customize Signup and Login Prompts **Customize Signup and Login Prompts** is a feature that allows customers with Custom Domain and Custom Page Template enabled to add custom fields and content to their app’s signup and login prompts. -## Use Cases +## Use cases Customize Signup and Login Prompts supports two use cases: **custom content** and **data capture.** @@ -95,7 +95,7 @@ Partials can also be managed using Auth0 CLI’s ![An image showing the command-line interface for Partials. ](/docs/images/cdy7uua7fh8z/KxWfVAMkumyI2jrUqkEp8/b9315709899864a2f8758ad7f5a4f5b2/Partials_CLI_Image.jpg) -## Style and validate form inputs +## Style and validate Form Inputs Customize Signup and Login Prompts offers pre-built styles and support for client-side validations for certain HTML form elements. The following elements are supported: @@ -113,7 +113,7 @@ To use pre-built input styles, wrap your form element of choice in a `
` wit You can find pre-built code snippets when using the [partials](#use-the-auth0-dashboard-to-manage-partials) editor. -### Client-side Validation +### Client-side validation The feature's client-side validation framework allows customers to validate user input using HTML attributes to execute one or more custom validation functions. Validation functions can be included directly in the Partial or included in the `` of the page template. @@ -135,7 +135,7 @@ Partial content can be localized by defining new custom text variables using the ### Create or update a custom text variable -Calls to the [Custom Text API](/docs/api/management/v2/prompts/get-custom-text-by-language) must specify the `screen` when adding, updating, or deleting a custom text variable. Custom text variables follow the `var-` naming convention. Markdown links are supported and are converted to HTML `` elements before being displayed to users. +Manage custom text variables with the [Custom Text API](/docs/api/management/v2/prompts/get-custom-text-by-language). Calls must specify the `screen` when adding, updating, or deleting a custom text variable. Custom text variables follow the `var-` naming convention. Markdown links are supported and are converted to HTML `` elements before being displayed to users. Below is an example call to add a variable for the text of a terms of service checkbox label in English and Spanish. See the Management API to learn more. @@ -155,7 +155,7 @@ Below is an example call to add a variable for the text of a terms of service ch } ``` -### Use a custom text variable in a partial +### Use a custom text variable in a Partial Custom text variables are referenced in partials using the `prompts.screen.text` object; the reference for the `var-tos` example in the previous section is `prompt.screen.text.varTos`. See below for an example of how to use a previously created variable in a partial on the Signup ID Prompt, noting that the Management API's `var-tos` variable is referenced as `varTos` in the partial. @@ -218,7 +218,7 @@ Sanitize any data that you collect on the form before saving or rendering it. For more information regarding risk mitigation and best practices for securely storing data see [this cheatsheet](https://cheatsheetseries.owasp.org/cheatsheets/Input_Validation_Cheat_Sheet.html). -### Save to user Metadata +### Save to user metadata From the Action, captured data can be sent to an external API for validation and storage or saved in `user_metadata` on the user via `api.user.setUserMetadata`.