> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/developer-guide/development-cycle/overview/runtime/dynamic-accounts.md).

# Dynamic Accounts

## **Why use Dynamic Accounts**

Static account configuration does not allow credentials to change at runtime. This limits scenarios such as receiving a certificate from an endpoint to authenticate in a REST API, or receiving an ephemeral token to authenticate over an SFTP connection.

The [Store Account](/documentation/connectors-and-triggers/connectors/tools/store-account.md) connector lets you configure credentials on the Runtime screen for multipurpose pipelines. This centralizes credential management and provides agility and security across the stages of a workflow.

## **Availability**

Dynamic Accounts adapt account settings to the specific needs of each connector. This functionality is available as a parameter configuration for the following connectors:

* [SAP](/documentation/connectors-and-triggers/connectors/enterprise-applications/sap.md)
* [SFTP](/documentation/connectors-and-triggers/connectors/file-storage/sftp.md)
* [FTP](/documentation/connectors-and-triggers/connectors/file-storage/ftp.md)
* [REST v2](/documentation/connectors-and-triggers/connectors/web-protocols/rest-v2.md)
* [SOAP v3](/documentation/connectors-and-triggers/connectors/web-protocols/soap-v3.md)
* [DB v2](/documentation/connectors-and-triggers/connectors/structured-data/db-v2.md)
* [Kafka](/documentation/connectors-and-triggers/connectors/queues-and-messaging/kafka.md)
* [Email v2](/documentation/connectors-and-triggers/connectors/web-protocols/email-v2.md)
* [AWS Simple Email Service (SES)](/documentation/connectors-and-triggers/connectors/aws/ses.md)
* [Dynamics 365](/documentation/connectors-and-triggers/connectors/enterprise-applications/dynamics-365.md)
* [PGP](/documentation/connectors-and-triggers/connectors/security/pgp.md)
* [PBE cryptography](/documentation/connectors-and-triggers/connectors/security/pbe-cryptography.md)
* [RSA cryptography](/documentation/connectors-and-triggers/connectors/security/rsa-cryptography.md)
* [S3 Storage (AWS)](/documentation/connectors-and-triggers/connectors/aws/s3-storage.md)

Configuration parameters for Dynamic Accounts are described in the documentation of each respective connector.

{% hint style="warning" %}
For security reasons, never store credentials openly anywhere, nor save them in the [Object Store](/documentation/connectors-and-triggers/connectors/structured-data/object-store.md).
{% endhint %}

## **How to add dynamic credentials to a pipeline**

To add dynamic credentials to a pipeline:

1. Add the [**Store Account**](/documentation/connectors-and-triggers/connectors/tools/store-account.md) connector to the pipeline.
2. Select the type of account to register.
3. Enter the required credentials.
4. Click **Save**.

The credentials become available on every pipeline run, ready to be referenced by other connectors.

## **How to use Dynamic Accounts on a connector**

To use Dynamic Accounts in a connector:

1. Enable the **Use Dynamic Accounts** option on the desired connector (see the list of connectors in [Availability](#availability)).
2. Enter the name of the account created with the [**Store Account**](/documentation/connectors-and-triggers/connectors/tools/store-account.md) connector in the **Account Name** field.
3. Confirm that the connector authenticates using this credential.

## **How to reference accounts with Double Braces**

To reference the account scope in the body of requests in connectors such as [**REST v2**](/documentation/connectors-and-triggers/connectors/web-protocols/rest-v2.md) and [**SOAP v3**](/documentation/connectors-and-triggers/connectors/web-protocols/soap-v3.md), register the credential using the **Store Account** connector with the syntax `{{ account.custom-1.password }}`. This makes the information available for use in your operations.

For example, for a Basic type account named **account-test**, the reference is: `{{account.account-test-password}}`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digibee.com/documentation/developer-guide/development-cycle/overview/runtime/dynamic-accounts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.