Credential Stores
For Automation Cloud, Test Cloud, and Automation Cloud Dedicated, the Credentials page is split in two views: Stores and Proxies.
- The Stores page allows you to create new stores, view existing stores and their properties, and delete any current credential store. Note that the native Orchestrator Database store is automatically created, will always appear first in this list and be the Default store for all new tenants.
- The page allows you to create new proxies for your own custom credential stores, view a list of existing proxies, edit, and remove them.
For Automation Cloud Public Sector and Test Cloud Public Sector, the Stores page allows you to create new stores, view existing stores and their properties, and delete any current credential store. Note that the native Orchestrator Database store is automatically created, will always appear first in this list and be the Default store for all new tenants.
The credential stores feature must be enabled for your tenant by the Orchestrator administrator. See here for details.
Managing credential stores in Orchestrator requires specific privileges because credential stores contain sensitive authentication data used by automations. To create, modify, or delete credential stores, a user must have Settings permissions (View, Edit, Create, and Delete). These permissions are included in the Orchestrator Administrator role. If the Settings permissions are removed from a role, the user will no longer be able to manage credential stores.