---
title: Page node
description: The Page node lets you combine multiple nodes that request input onto a single page for display to the user. For example, you can use it to create a single login page that requests a username and password.
component: auth-node-ref
version: 7.4
page_id: auth-node-ref::page
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/page.html
llms_txt: https://docs.pingidentity.com/auth-node-ref/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
keywords: ["Nodes & Trees", "Journeys", "Authentication"]
page_aliases: ["auth-node-page.adoc"]
superseded_by: https://docs.pingidentity.com/auth-node-ref/latest/page.html
section_ids:
  compatibility: Compatibility
  outcomes: Outcomes
  properties: Properties
  example: Example
---

# Page node

The Page node lets you combine multiple nodes that request input onto a single page for display to the user. For example, you can use it to create a single login page that requests a username and password.

|   |                                                                           |
| - | ------------------------------------------------------------------------- |
|   | The Page node can only include nodes that use callbacks to request input. |

To use it, drag and drop compatible nodes onto the Page node in the journey editor.

When designing a journey that includes a Page node, consider the following points:

* A Page node must contain at least one node.

* Page nodes can't be nested inside each other. Similarly, you can't include an [Inner Tree Evaluator node](inner-tree-evaluator.html) in a Page node.

* Page nodes are designed to group nodes together that require user input. Non-interactive nodes, such as the [Data Store Decision node](data-store-decision.html) or [Push Sender node](push-sender.html), should be placed outside of Page nodes.

* Scripted Decision nodes can be included in Page nodes but only if they handle callbacks.

  Scripts that use the `Action` class to set outcomes (using the `goTo` method), or set messages (using fields such as `lockoutMessage` or `errorMessage`), aren't supported within a Page node.

* Only the final node can have multiple outcomes. All preceding nodes must have a single outcome path.

## Compatibility

| Product                                    | Compatible?           |
| ------------------------------------------ | --------------------- |
| PingOne Advanced Identity Cloud            | [icon: check, set=fa] |
| ForgeRock Access Management (self-managed) | [icon: check, set=fa] |
| Ping Identity Platform (self-managed)      | [icon: check, set=fa] |

## Outcomes

The outcomes are determined by the last node in the Page node. Only the last node in the page can have more than one outcome path.

## Properties

| Property           | Usage                                                                                                                                                                                                                                    |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Page Header        | Optional localized title for the page node and the nodes contained within it. Use this when components of an authentication flow need a title, such as breaking a registration into labeled sections.                                    |
| Page Description   | Optional localized description for the page node and the nodes contained within it. Use this when additional descriptive text is needed in an authentication flow.                                                                       |
| Stage              | An optional stage name to pass to the client to aid in rendering.                                                                                                                                                                        |
| Submit Button Text | Optional. Use the Key and Value fields to set the text of the Submit button.This property is available only in the Ping Identity Platform admin UI.                                                                                      |
| Page Footer        | Optional. A localized footer for the page node and the nodes contained within it. Use this when additional descriptive text is needed in an authentication flow\.This property is available only in the Ping Identity Platform admin UI. |
| Theme              | Optional. If using hosted pages, specify a theme to override this journey's UI theme.This property is available only in the Ping Identity Platform admin UI.                                                                             |

|   |                                                                                                                                                                |
| - | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | This node's optional properties are passed in the response, but a self-hosted or custom UI must support these properties to make them visible to the end user. |

## Example

The following example uses a page node containing a username collector, a password collector, and a choice collector:

![Example journey showing Page node use](_images/trees-node-page-example-platform.png)

The flow prompts the user for all input on a single page:

![User's view of an example journey containing a Page node](_images/trees-node-page-example-output-platform.png)