...
For a SnapLogic-managed Snaplex (Cloudplex), when you create an Account, the information in it is encrypted by the browser before transmission using your Org’s public key. At rest, the encrypted Account data is stored in an encrypted Amazon S3 bucket. When a Pipeline executes, the Snaplex decrypts the information using a private key.
For a self-managed Snaplex (Groundplex) the default behavior is the same as for a SnapLogic-managed Snaplex. Organizations can add one of the following for additional security:
Enhanced Encryption, where the organization creates and manages the private keys used by nodes to decrypt credentials.
Secrets Management, for organizations using a third-party secret manager, such as HashiCorp Vault.
...
A single Account can be used by multiple Pipelines, Snaps, and Flows. Accounts are accessible to the User who created them and to Pipelines in the Project folder in which they were created. Accounts in a shared folder can be used by anyone with access permission to that folder. Org admins with access to multiple Orgs can migrate Accounts from one Org to another. Learn more about Migrating Accounts.
| Anchor | ||||
|---|---|---|---|---|
|
...
To change a field to be dynamic, click 
and enter the expression value. If you change a field with an encrypted value, such as a password or a token, to use an expression, the IIP clears the original value to protect sensitive information.
If any fields in the Account settings use an expression value, the suggestions for other fields in the Snap settings are not populated. This is a known limitation of the SnapLogic Platform.
The following screenshot shows the dynamic fields available in an Azure SQL Active Directory Dynamic Account:
...