Transcend Docs

How DSR Forms Are Built

Learn how data subjects, data actions, and identifiers combine into the request form that your Privacy Center shows.

After you read this page, you can tell which setting controls each part of the request form in your Privacy Center. For the dashboard steps, see Setting up DSR Automation Forms.

The building blocks

Building blockPart of the form it controls
Data subjectThe requester types that a person picks from, and the request types offered to each
Data actionOne request type: its button, and the text on the confirmation screen
IdentifierOne input field on the confirmation screen

What the requester sees

The form opens when a person clicks Make a Privacy Request.

  1. Requester type. The form lists your active data subjects in display order. If you have one active data subject, the form skips this step.
  2. Request type. The form shows one button for each data action enabled for that data subject. Each button shows the title and description of the data action.
  3. Login. A person who is not logged in logs in before the next step.
  4. Confirmation. The screen shows the title and confirmation description of the data action, then the input fields. The person clicks Confirm Request to submit.

Two settings change this flow:

  • A data subject with disabled instructions shows that message in place of the request types.
  • When the Sale of Info page is enabled, the form hides the sale opt-out and sensitive information opt-out request types. That page handles them.

How the form picks input fields

For the selected data action, the form adds fields in this order:

  1. Identifiers. The form adds each identifier enabled for that data action. It skips an identifier that is limited to other data subjects.
  2. Details. Rectification and restriction requests add a required details field.
  3. Confirmations and file uploads. The form adds the confirmation messages and file uploads set on the data action.
  4. Region. The form adds a region field when the Region Detection Method of the data action is Request in form.

The form puts the core identifier first. It sorts the other identifiers by Display Order, lowest first.

Each identifier field takes its parts from the identifier settings:

Part of the fieldIdentifier setting
LabelPrivacy Center Title. An empty title falls back to a default label.
Helper textPrivacy Center Description
PlaceholderPrivacy Center Placeholder
RequiredRequired in Privacy Center Form
Dropdown choicesPrivacy Center Form Options, on custom identifiers

A custom identifier with options renders as a dropdown. Without options it renders as a text box.

Forms with Workflows V2

Your Privacy Center lists workflows in place of data actions when all of these are true:

  • Your organization has Workflows V2.
  • Show the Workflows V2 experience on the Privacy Center? is on in Privacy Center > General Settings.
  • At least one workflow is published to the Privacy Center.

Each button then shows the title and subtitle of a workflow. The confirmation screen shows the title and description of the workflow, with the input fields set on that workflow. To set these, see Workflows: Quickstart Guide.

On this page