Deployment Tab

Enables you to configure and secure feeds for packages and libraries. You can manage the feeds for all tenants from a centralized location using Automation Ops. For more information, see feeds management in the Automation Ops guide.

Settings here only affect tenant feeds; folder feeds and personal workspace feeds are always internal and available in the context of the respective folder or personal workspace alone.

Packages

Enables you to set an internal or an external feed in which automation packages can be maintained. By default, an internal feed is used. The feeds can be secured either by defining basic authentication credentials or by using an API key.

Field	Description
Internal	Use an internal feed. The feed can be secured either with the Secure Deployment option or by using an API key: Secure Deployment - Ensures that your automation packages are downloaded through a secure NuGet feed. API Key - The key used to secure your feed against write operations such as delete or upload. This is only required if you want to upload a package directly to the NuGet feed using an external client.
External	Use an external feed. The feed can be secured either by using an API key or basic authentication credentials: API Key - The key used to secure your feed against write operations such as delete or upload. Authentication - Enables you to specify the credentials for your basic authenticated feed. Please keep in mind that both the username and the password used with the API Key option should be used in this case as well. When External is selected, the Deployment URL field is displayed where you need to fill in the address where the NuGet feed is located.

Libraries

Enables you to configure the feed to be used for library and activity packages.

Field	Description
Only host feed	Libraries are stored in the host feed and are available to all tenants which use it. The Libraries page is the same for one Orchestrator instance, meaning libraries are not isolated at the tenant level: each tenant has access to the other tenants' activity. You cannot upload libraries from Orchestrator if this option is selected. This option gives robot access only to the host feed.
Only tenant feed	Libraries are isolated at the tenant level, meaning data is separated across tenants. You may set an internal or an external feed in which libraries are maintained. By default, an internal feed is used. This option gives robot access only to the tenant feed.
Both host and tenant feeds	Libraries are isolated at the tenant level, meaning data is separated across tenants. You may set an internal or an external feed in which libraries are maintained. By default, an internal feed is used. This option gives robot access to both the host and tenant feeds.
Internal	Must be selected in order to use an internal feed as the tenant feed. The feed can be secured either with the Secure Deployment option or by using an API key: Secure Deployment - Ensures that your automation packages are downloaded through a secure NuGet feed. API Key - The key used to secure your feed against write operations such as delete or upload. The user can use it to publish packages. This key is generated by the external provider and has the following format [username]:[password]. For example, admin:2652ACsQhy.
External	Must be selected in order to use an external feed as the tenant feed. The feed can be secured using an API key: API Key - The key used to secure your feed against write operations such as delete or upload. The user can use it to publish packages. This key is generated by the external provider and has the following format [username]:[password]. For example, admin:2652ACsQhy. When External is selected, the Deployment URL field is displayed where you need to fill in the address where the NuGet feed is located.