# June 2026 > The all-jobs cross-folder grid now includes a **Go to folder** inline action on each row. Selecting it opens the **Jobs** page for that row's folder. When the job has an associated release, the page is pre-filtered by the job's process. ## June 8, 2026 ### Navigate to a folder from the cross-folder Jobs grid The all-jobs cross-folder grid now includes a **Go to folder** inline action on each row. Selecting it opens the **Jobs** page for that row's folder. When the job has an associated release, the page is pre-filtered by the job's process. For more information, check [Jobs](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/jobs-monitoring). ![Go to folder button](https://dev-assets.cms.uipath.com/assets/images/orchestrator/Go_to_Folder-ba33d0fa.webp) ### Run as Myself renamed and extended to Windows automations When you configure an execution target through bindings, the **Run as Myself** option is now labeled **Inherit parent job identity**, making it clearer that the invoked job runs under the identity of the parent job. This option is now also available for Windows (foreground) automations, not only background processes. When you use it for a Windows automation, the parent job identity must have an unattended robot with credentials configured — otherwise the invoked job fails to start. For more information, check [About jobs](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-jobs). ### Out-of-the-box execution identity for new folders You can now configure a tenant-level default execution identity—a default account and machine—that is automatically applied to new folders as they are created. This removes much of the manual setup previously required before you could run automations in a newly created folder. New tenants are provisioned with an out-of-the-box default configuration, and administrators can review and update the tenant's default execution identity at any time. For more information, see [Default Execution Identity](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-default-execution-identity) and [Configure the Default Execution Identity](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/configure-default-execution-identity). ### Automatic cleanup of Default Execution Identity references When a user or machine is deleted from a tenant, the references to that user or machine are now automatically removed from the tenant-level **Default Execution Identity** configuration. Previously, deleted users or machines remained as dangling entries in the configuration. The references were skipped at apply time, but they produced repeated warning logs and made the configuration harder to inspect. With this change, the configuration stays in sync with the actual users and machines in the tenant. ### Unified outbound IP ranges — transition begins Orchestrator outbound IP ranges are being unified. The new unified outbound IP ranges apply per regions (for example, United States, Europe, etc.) and are the same for all UiPath services within a region. For the full list of affected services, refer to the [June 8, 2026 Automation Cloud release notes](https://docs.uipath.com/automation-cloud/automation-cloud/latest/release-notes/june-2026#june-8%2C-2026). The current Orchestrator outbound IP ranges will remain active until September 16, 2026. Starting September 16, they will be progressively phased out as the unified IP ranges take effect. **What you need to do**: 1. **Add the new unified IP ranges to your firewall configuration now.** Find the full list of unified outbound IP ranges by region on the [Configuring the firewall for Automation Cloud](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/configuring-the-firewall-for-cloud) page. 2. **Until September 16, 2026**: Keep both the current Orchestrator outbound IP ranges (on the [Legacy - Configuring the firewall for Automation Cloud](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/configuring-the-firewall-for-cloud-legacy#orchestrator) page) and the new unified IP ranges allowlisted simultaneously. 3. **After September 16, 2026**: Continue allowlisting both sets of IP ranges until a subsequent release note confirms the legacy IP ranges can be safely removed. ## June 2, 2026 ### South Korea region support for Orchestrator As part of our ongoing cloud expansion, we're bringing complete data sovereignty to the South Korea region for Orchestrator, ACR - VM, and ACR - Serverless. This ensures your data is securely stored and replicated across multiple availability zones within South Korea, offering full control and compliance confidence. For more information, refer to the [Global cloud regions](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/global-cloud-regions) page.