Accounts
Learn more about accounts and how they are used to safely manage credentials on the Digibee Integration Platform.
Overview
Accounts provide a secure way to store sensitive information, such as passwords, private keys, and authentication tokens, without exposing these credentials directly in your integrations. By encrypting and centrally managing credentials, accounts help ensure the security of authentication processes.
Furthermore, accounts can be restricted to specific projects, ensuring that sensitive information is only accessible where it is needed. They can then be used in connectors within pipelines and capsules to authenticate and authorize access to external endpoints.
Managing accounts
Creating an account
On the Platform home page, click Settings in the upper-right corner, then select Accounts on the next page.
Click Create and fill in the fields:
Name: Identifier for the account.
Account type: Choose from the available options.
Description: Additional information about the account.
Project Availability: Define if the account can be used in all projects or only in selected ones. On the Accounts listing page, you will only see accounts that are available to all projects or the ones you have permission to access.
Pipelines only work with accounts available in their project. If a pipeline is moved to another project, the account is disconnected until a new one is configured or the project is allowed.
Environment configuration: Credentials required for the selected account type. See below how to configure each account type.
Expiration date: Enter in DD/MM/YYYY format (for example, 30/05/2030). Accounts close to expiration show Expires in DD/MM; expired accounts show Expired. When the date matches the external service, the account stops working until you update the credentials and redeploy the pipelines. You can also filter accounts by Close to expiring or Expired. This field is optional and only applies to OAuth Bearer, Private Key, Public Key, OAuth 2, Certificate Chain, Google Key, AWS V4.
Click Save to create the account.
Configuring each account type
Editing an account
To edit an account, go to the Accounts page and click the pencil icon in the Actions menu.
You can:
Update the description.
Mark the account as deprecated. Learn more about deprecating an account.
Define new rules for Project Availability.
Update credentials for all environments. Sensitive credentials won’t be visible, but you can add new ones.
View all pipelines that use the account. Note that if the account is edited, any deployed pipelines must be redeployed to apply the changes.
After editing the account, a confirmation window appears. Type “I want to edit the account” in the Confirmation message field and click Edit.
All changes are applied immediately to pipelines that use the account and have not yet been deployed.
Deprecating an account
Deprecating an account makes it unavailable for new pipelines or new pipeline versions. Existing deployments will keep working unless redeployed.
To deprecate an account:
Open the Accounts page and click the pencil icon next to the account.
Enable the Deprecated toggle.
Click Save.
This action is irreversible.
Deleting an account
Deleting an account permanently removes it from the Platform. You cannot delete accounts that are currently used in pipelines, whether deployed or not. To proceed, remove or replace the account in all pipelines before deleting it.
To delete an account:
Open the Accounts page.
Click the trash icon next to the account.
Click Delete in the confirmation window.
Using accounts
Accounts are used within pipelines and capsules to provide secure access to external services through connectors that support the Account field. When a connector requires an account, the Account field appears in its configuration form, allowing you to select the appropriate account for that integration.
Last updated
Was this helpful?