OneCloud is proud to announce that we've re-vamped the user interface to enhance productivity without interruptions to your existing workflow. We believe these changes make actions more clearly visible, while maximizing the use of space on the screen. Highlighted below are some of the major changes.

New navigation bar

The navigation bar is now fixed to the left side of the screen. Most notably, "Flow Management" has been re-named to "Build" and "Self Service" has been re-named to "Run". In addition, a link to the admin page has been added to the navigation bar (only visible to admin users).

Environment cards and colors

Environments are now displayed as cards within a workspace, and users may now select a color for each environment. This color-coding acts as a visual cue for the user to remind them which environment's chains they are editing or running.

Editing workspaces and environments

Workspaces and environments are now edited separately. When editing a workspace, you're only required to submit basic information and choose variables. These variables can have a default value, and their values can be set on a per-environment basis by editing an environment individually. Lastly, users can choose an environment's color. Visit the Workspace Setup documentation for a more in-depth look on the changes to editing workspaces and environments.


Computing resources are now called Connections to more accurately represent how they connect your chains and commands to external services. All of your existing computing resources were automatically migrated to connections, so no action is required to keep your chains running. Connections still encapsulate the same functionality as computing resources, though, so creating a connection is very similar to creating a computing resource.

Additional security features and the ability to use connections across different workspaces make connections a marked improvement over the previous workflow for creating computing resources.

OAuth support for connections

Certain external services and APIs require the use of OAuth 2.0 instead of basic auth (i.e. username and password) to connect. We have added the ability to connect via OAuth 2.0 to an external service automatically, without leaving the platform. In the connections form, if you select an OAuth 2.0 enabled service, you will be automatically prompted to authenticate.

Security features added to connections

Granular security is an important feature of the OneCloud platform, and we're pleased to be able to extend it to connections. Admin users can now specify the environments and workspaces in which connections can be used. This change helps users prevent mis-use of production credentials in non-production environments. We recommend that admin users view the Connections documentation for more details on how to build and authorize new connections.

We have strived for make this change feel like an iterative one, and we are confident that it enables users to be even more productive when building and running chains. Our documentation has been updated to reflect all of the new workflows, but please do not hesitate to reach out to support if anything is unclear. Thanks for reading, and we look forward to hearing your feedback!

Did this answer your question?