2 - Create Environments for Testing
- How to create a private environment
- How to create a shared environment
Daniel WroblewskiMarch 8, 2026
Prerequisites
- You have completed the previous tutorial in the Joule Studio CodeJam Mission, Open and Explore the SAP Build Lobby.
Joule studio has different types of environments to guide the development of your projects:
-
Private Environment: Each developer can set up a private environment, which is designed to provide a “sandbox” or safe, isolated space for experimenting with your Joule Studio projects. It is used to run the current project without being influenced by other deployed projects. The key advantages are:
-
Safely experiment with new agent logic, skills, and actions.
-
Test conversations during design time (before deployment).
-
Test projects without needing to create new releases or deployments.
-
-
Shared Environment: Allows different lines of business to deploy their projects to separate areas, each with specific permissions and different destinations and other settings.
-
Production Environment: Agents and skills in the production environment are run in the central Joule instance along with all other built-in or custom skills and agents.
So the flow of development would be something like this:
-
You create a private environment.
-
You create 2 shared environments for any line of business: one for testing, and one for production.
-
You set the environment designated for production to expose to production any Joule Studio artifacts deployed to that environment (there is a toggle in each environment to do this).
-
You develop a Joule Studio project and test it inside your private environment.
-
You deploy it to your test shared environment for a particular line of business and test it there.
-
When ready, you deploy it to the production environment, which will automatically expose it to the production Joule.
- Step 1
First, you will create an environment for yourself.
A private environment is for your user to test your Joule project in an isolated sandbox, unaffected by any other projects of yours or anybody else.
-
In the SAP Build Lobby, click on the Control Tower tile.
-
In the Control Tower, click on the Environments tile.
-
Click the Activate Private Environment button.
You will see a new environment labeled Private in the list of environments.
-
- Step 2
Though you will not create a shared environment for this CodeJam, we wanted you to understand what it is and how to create one.
A shared environment is a place to deploy your projects for your LOB that has its own settings and permissions.
-
A shared test environment is a place for you to test your projects away from other projects of other LOBs, though with other projects from your LOB.
-
A production shared environment is a place for you to deploy your LOB projects that should be placed into production. Though all projects in all production shared environments will go into the production Joule, only people given permission to your production shared environment will be able to make use of your projects, skills and agents.
For this CodeJam, you have not been given admin permission to create an environment, but here is how it would work.
-
In the same environments screen, you would click Create (for you this is disabled).
-
In the Create Environment form, you would fill in something like the following:
Field Value Environment Name Joule Studio 003 DBWColor Whatever color you’d like 😸 Description Shared environment for Sales team
-
You would click Create.
You would now see a new environment labeled Sales in the list of environments, this time not gray but with the color you assigned to it.
-