Each Application can designate one Environment as its default environment

In the data model this is the primary Environment for the Application; in the UI it powers shortcuts and which Environment is emphasized when several exist.

Conceptual context: Environments under Core Concepts in the sidebar and Applications under Core Concepts in the sidebar.

Why it matters

• Navigation: From the Application list, the overflow menu on an active Application can offer Open default environment, jumping into that Environment’s Services view when setup is complete.
• Overview: The Application Overview tab highlights a primary Environment card for at-a-glance health and quick links, aligned with the resolved default when one is set.
• First Environment: During Create New Application, the first Environment you create is typically marked as the default when you have no others yet.

How to change the default

1. Open the Application, then open the Environment you want.
2. Go to the Environment Settings tab (heading Settings).
3. Under General, enable Use as default environment for this application.
4. Click Save Changes.

The card copy states that the section covers Name and default environment for this application.

Multiple Environments

You can add more Environments later (Create an environment when published). Only one should be the default at a time; switching the checkbox on another Environment moves the default.

Related

• Application settings (Application name and description, not the default Environment)
• Create an application
• Draft vs active environments (when published)
• Troubleshooting overview if shortcuts or default routing misbehave