Preflight and Identity Enrichment Overview

Before processing begins for a DSR, Transcend validates the request through a series of preflight checks (also called identity enrichers) to ensure it is legitimate and ready for processing. Preflight checks primarily resolve and verify identifiers on the request. Each check can be read about in more detail by clicking on the desired check name below:

  1. Email verification (magic link)
  2. Phone number verification via SMS (magic link)
  3. Custom Functions
  4. Post to a Server (Webhook)
  5. Notify a Person
  6. Region Matcher
  7. RegExp Match
  8. Auto Approve
  9. Database
  10. Looker
  11. Legal Hold Check
  12. Wait Period
  13. Government ID verification via Stripe Identity (magic link)

Each preflight check is configured with an input identifier. Some preflight checks, such as Transcend Email Verification, do not allow the input identifier to be configured as Transcend automatically maps the input. A check runs when the defined input identifier exists on the request. If a preflight check returns output identifiers, Transcend adds them to the request and queues any other preflights whose input identifiers are now available. Each preflight check targets a single input identifier type and runs once for every value of that type on the request.

Preflight checks are not ordered by how they appear in the Admin Dashboard. Transcend determines execution order based on input and output identifiers:

  • A preflight check runs when its required input identifier is present on the request.
  • If it produces output identifiers, preflight checks that depend on those outputs are queued automatically.
  • When multiple preflight checks are ready at the same time, they may run in parallel.

In most cases, you will not need to configure explicit ordering. Preflight Dependencies are available for situations where a preflight check must wait for other specific checks to finish, regardless of identifier flow.

Note: Preflight Dependencies enforce completion order, not immediate sequencing. A dependent check remains in a Waiting on Dependencies state until the upstream check fully resolves.

The following settings apply to many, but not all, preflight checks. For example, the Transcend Email Verification preflight does not support custom input or output identifiers.

SettingWhat it controls
Input IdentifierWhich request identifier triggers this check
Output IdentifiersIdentifiers this check can add to the request
Live for DSRs?Whether new and restarted DSRs queue this check
Paused for DSRs?Whether active processing for this check is halted
Enabled ActionsWhich DSR actions (Access, Erasure, etc.) use this check
Data SubjectsWhich data subject types this check runs for (empty = all)
Preflight DependenciesOther checks that must resolve before this one runs
DSR Processing Time WindowOptional daily start and end times during which this check may process requests

For settings unique to a specific integration, see the relevant per-type article above.