---
title: OOTB - Financial Services - Privacy Settings Subflow
description: Learn about the OOTB - Financial Services - Privacy Settings Subflow flow, including its purpose, structure, inputs, outputs, and variables.
component: pingone-solutions
page_id: pingone-solutions:financial-services:flow-reference/financial-services-privacy-settings-subflow
canonical_url: https://docs.pingidentity.com/pingone-solutions/financial-services/flow-reference/financial-services-privacy-settings-subflow.html
revdate: July 1, 2025
section_ids:
  purpose: Purpose
  structure: Structure
  input-schema: Input schema
  output-schema: Output schema
  variables-and-parameters: Variables and parameters
---

# OOTB - Financial Services - Privacy Settings Subflow

The **OOTB - Financial Services - Privacy Settings Subflow** lets users update privacy settings.

## Purpose

The **OOTB - Financial Services - Privacy Settings Subflow** presents users with a form that lets them preview privacy changes and update their privacy settings. The user's updated settings are saved by PingOne.

## Structure

This flow is divided into sections using teleport nodes:

* **OOTB - Financial Services - Privacy Settings Subflow**

  A function node sets flow variables and a PingOne node verifies that the user exists. An HTML node then presents the user with privacy options. The flow then branches based on the user's selection:

  * If the user clicks **Submit**, function nodes validate the user's selections, then a PingOne node updates the user's privacy preferences. A success message is displayed, then the flow progresses to the **Return Success** section.

  * If the user clicks **Preview**, a function node stores the user's preferences, then an HTML node displays to preview the selected options. The flow then returns to the privacy options page.

  * If the user cancels, the flow progresses to the **Return Success** section.

* **Return Success**

  Sends a success JSON response, indicating that the flow has completed successfully.

* **Return Error**

  Uses a function node to enrich the error details, then sends an error JSON response indicating that the flow completed unsuccessfully.

## Input schema

This flow has the following inputs:

| Input name      | Required | Description                                            |
| --------------- | -------- | ------------------------------------------------------ |
| `pingOneUserId` | Yes      | The current user's PingOne user ID.                    |
| `companyLogo`   | No       | The company logo to display in user-facing HTML pages. |
| `flowMethod`    | No       | The flow method.                                       |

## Output schema

This flow has the following outputs:

| Output Name     | Description                                   |
| --------------- | --------------------------------------------- |
| `subflowResult` | The result status of the flow.                |
| `errorMessage`  | The error message to pass to the parent flow. |
| `errorDetails`  | The details of the error that occurred.       |

## Variables and parameters

This flow uses the following variable or parameter values:

| Parameter name      | Description                                                                                      |
| ------------------- | ------------------------------------------------------------------------------------------------ |
| `p1UserId`          | The current user's PingOne user ID.                                                              |
| `currency`          | The currency symbol for the user's locale.                                                       |
| `accountVisibility` | A property containing the user's preferences for sharing account information with third parties. |