Academy
System Administration

Credential Management

The Credential Management screen centralizes the platform’s connection credentials — access to ERPs, databases, storage systems, and APIs that process steps use to import and export data. Once created, a credential can be reused in as many steps and processes as needed, with secrets protected and usage controlled by profiles. The screen is located under Settings > General Settings > Credentials.

Credential Types

Credentials are organized into four categories, which correspond to the platform’s integrations:

  • Database: connections used by the Database (import) and Database Export steps.

  • ERP: access for the native connectors used by the ERP step (SAP, Dynamics, Oracle, Sankhya).

  • Storage: storage connections (e.g., SFTP) used for automatic file exchange.

  • API: access to external APIs.

The list screen

  • Search by name and filters for Credential Type and Status refine the list.

  • Columns: Name, Type (with the connector icon), Processes (how many processes use the credential — hover to see the code and name of each one), Profiles (how many privacy profiles have access — hover to see which ones) and Status (Active or Inactive).

  • The action menu for each row includes Edit, Activate/Deactivate and Delete.

Attention: activating and deactivating do not require confirmation — the status changes immediately. Deactivating does not affect the processes that use the credential, but it can no longer be selected in steps and the runs that depend on it will start failing until it is reactivated.

Create a credential

  1. Click New credential.

  2. In the Select credential type dialog, browse the category tabs (All, Database, ERP, Storage, API) or use search, and choose the type. The type cannot be changed later — to switch it, create another credential.

  3. Fill out the form:

  • Credential name — required and unique.

  • Type-specific fields — vary by connector (address, user, password, keys); required fields are marked with an asterisk.

  • Privacy profiles — at least one is required. These define which user profiles can view and use the credential; users outside the selected profiles will not find it in steps.

  1. Click Save.

  2. Once the credential is saved, use Test connection (available for types that support testing) to validate access — the result appears on the screen itself, in green on success or in red with the error message. Pending changes are saved automatically before the test.

Types that have their own configuration guide display the Documentation button in the editor header, which opens the support material in a new tab.

Sensitive data security

  • Passwords, secrets, and keys are encrypted in storage and are never shown back — when editing, sensitive fields appear masked.

  • When editing, leave the sensitive field blank to keep the saved value; fill it in only if you want to replace the secret.

  • Inactive credentials cannot be edited — reactivate them before making changes.

  • Revoking access is immediate: Deactivate on the screen itself (or deactivate the integration user in the source system).

The Processes column shows where each credential is being used. A credential linked to processes cannot be deleted — the delete dialog shows the list of processes and instructs: "This credential is linked to processes and cannot be deleted. Remove the links before deleting." Unlinking is done in the processes themselves, by replacing the credential in the steps that use it; to stop using it immediately without deleting it, deactivate it.

Use in process steps

In steps that consume credentials (ERP, Database, Database Export), the selector shows only the credentials from the corresponding category that your profiles allow you to use. From the selector itself, it is possible to create a new credential (shortcut "+ New credential") or edit an existing one, without leaving the step. Inactive credentials appear disabled in the list — the ERP step, for example, warns: "The selected credential is inactive. Activate it to continue."

Access permissions

Access to the screen has two levels:

  • Read: views the list, search, filters, and links — with the actions disabled.

  • Write: creates, edits, activates/deactivates, and deletes credentials; it also enables the shortcuts to create and edit credentials within process steps.

Users without permission do not see the item in the Settings menu.

Usage example

The data team registers an SQL Server credential with the read-only user provided by IT, validates it with Test connection, and restricts the privacy profiles to the finance team. The same credential can then be selected in the Database step of three different processes — and when the password is rotated, updating it in one place applies to all of them.

  • Introduction to integrations

  • ERP Step

  • Database Step

  • Database Export Step

  • Connect external storage systems (SFTP, SharePoint, OneDrive)

Was this helpful?
Was this helpful?