Credential Management
Credential Management is the screen that centralizes the platform’s connection credentials—the access details for ERPs, databases, storage systems, and APIs that process steps use to import and export data. Once created, a credential can be reused across as many steps and processes as needed, with secrets protected and usage controlled by profiles. The screen is located at Settings > General Settings > Credentials.
Credential types
Credentials are organized into four categories, corresponding to the platform’s integrations:
Database: connections used by the Database (import) and Database Export steps.
ERP: access details for the native connectors used by the ERP step (SAP, Dynamics, Oracle, Sankhya).
Storage: storage connections (e.g., SFTP) used for automatic file transfers.
API: access details for external APIs.
The list screen
Search by name and the Credential type and Status filters refine the list.
Columns: Name, Type (with the connector icon), Processes (how many processes use the credential—hover to see each process’s code and name), Profiles (how many privacy profiles have access—hover to see which ones), and Status (Active or Inactive).
Each row’s action menu includes Edit, Activate/Deactivate, and Delete.
Note: activating and deactivating do not require confirmation—the status changes immediately. Deactivating does not affect the processes that use the credential, but the credential can no longer be selected in steps, and any runs that depend on it will fail until it is reactivated.
Create a credential
Click New credential.
In the Select credential type dialog, browse the category tabs (All, Database, ERP, Storage, API) or use search, then select a type. The type cannot be changed later—to use a different type, create another credential.
Fill out the form:
Credential name — required and must be unique.
Type-specific fields — vary by connector (address, username, password, keys); required fields are marked with an asterisk.
Privacy profiles — at least one is required. These determine which user profiles can view and use the credential; users outside the selected profiles will not find it in the steps.
Click Save.
After saving the credential, use Test connection (available for types that support testing) to validate access—the result appears on the screen, in green if successful or in red with an error message. Pending changes are saved automatically before the test.
Types with their own configuration guide display the Documentation button in the editor header, which opens the reference material in a new tab.
Sensitive data security
Passwords, secrets, and keys are encrypted when stored and are never displayed again—sensitive fields appear masked when editing.
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.
Access revocation is immediate: click Deactivate on the screen (or deactivate the integration user in the source system).
Process associations
The Processes column shows where each credential is being used. A credential associated with processes cannot be deleted—the deletion dialog displays the list of processes and explains: "This credential is associated with processes and cannot be deleted. Remove the associations before deleting it." Associations are removed within the processes themselves by changing the credential in the steps that use it; to stop its use immediately without deleting it, deactivate it.
Using credentials in process steps
In steps that use credentials (ERP, Database, Database Export), the selector shows only credentials in the corresponding category that your profiles allow you to use. From the selector, you can create a new credential (the "+ New credential" shortcut) or edit an existing one without leaving the step. Inactive credentials appear disabled in the list—for example, the ERP step displays: "The selected credential is inactive. Activate it to continue."
Access permissions
There are two levels of access to the screen:
Read: can view the list, search, filters, and associations, with actions disabled.
Write: can create, edit, activate/deactivate, and delete credentials; also enables the shortcuts for creating and editing credentials within process steps.
Users without permission do not see the item in the Settings menu.
Usage example
The data team creates a SQL Server credential using the read-only user provided by IT, validates it with Test connection, and restricts its privacy profiles to the finance team. The same credential is then 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.
Related articles
Introduction to integrations
ERP step
Database step
Database Export step
File repositories: which ones Dattos connects to and how to set them up