Before You Begin

Orchestrator Studio access requires a separate sign-in with a valid EnterpriseOne user ID and password. Before users can sign in to Orchestrator Studio, an administrator must add each EnterpriseOne user to a list of allowed users in Server Manager. See Setting Up Allowed Users in this guide.

Also, orchestrations and orchestration components created in the Orchestrator Studio are saved and managed as user defined objects (UDOs) in EnterpriseOne. Therefore, an administrator must set up Orchestrator Studio users with the proper UDO security to access and use the Orchestrator Studio. See Setting Up UDO Security for Orchestrator Studio Users (Release 9.2.1) in this guide.

Note: Setting up users with access to the Orchestrator Studio automatically provides users with access to the Orchestrator Client, a standalone web application for testing orchestrations. You can access the Orchestrator Client from the Orchestrator Studio.