Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Password (2 Way Encrypted) design considerations

Store encrypted password data that can be decrypted.

Basic options

OptionDescription
LabelDisplays the label used to identify the data variable in the Workflow Studio interface. The label can consist of any text.
NameDisplays the name used to identify the data variable in script calls. The name can only consist of alphanumeric and underscore characters. The system automatically converts the label into a valid name by removing or replacing any special characters.
TypeIndicates the type of data stored by the data variable.
MandatoryIndicates whether the data variable must contain a value when configured in an action.

Advanced options

OptionDescription
HintProvides guidance to flow or action designers on how to configure the data.
Default valueSpecifies the value used when a flow or action designer does not provide a value.

General guidelines

Follow these general guidelines when designing flows containing Password (2 Way Encrypted) data.

  • Assign values using existing Password (2 Way Encrypted) data pills.

    You can only assign a value to a password2 variable by selecting an existing password2 data pill. Selecting values from other field types is not supported. Workflow Studio presents a warning message when invalid data pill types are selected.

Image omitted: password2-field-warning.ong.png
The warning message displayed when dragging a non-password2 data pill onto a password2 field.
**Note:** You cannot manually enter Password \(2 Way Encrypted\) values.
  • Use Password (2 Way Encrypted) variables only for valid field types

    Workflow Studio prevents selecting Password2 data pills as the value for invalid field types. The system presents a warning message when the field is an incompatible type.

Image omitted: password2-field-warning2.png
The warning shown when dragging a password2 field to a disallowed field.
Workflow Studio only allows Password2 data pills to be dragged into the following field types.

-   Email body fields
-   HTML fields
-   Password 2 Fields
-   PowerShell Input Variables
-   REST fields
    -   Variables
    -   REST payload body
    -   Query parameters
    -   Headers
    -   REST multi-part form values
    -   Form URL-encoded values
-   SOAP fields
    -   Headers
    -   Envelope
**Note:** you cannot use Password \(2 Way Encrypted\) variables as conditions

Flow Designer performs a validation check when a user saves, publishes, or tests actions and flows. This check shows that an alert for any data pills dropped in restricted field types and prevents the action or flow from executing. Update the action or flow to remove the invalid data pill and then retry the action.
  • Set up encryption modules for decryption

    Only users with a valid encryption module access can decrypt and view the contents of password2 variables. To specify the encryption algorithm and which roles can access encrypted data, see Password2 encryption with KMF .

Parent Topic:Workflow Studio input and output data variables