# Proxy Settings

> Settings > Configuration > Proxy Settings: enable proxies separately for Shift-Left Engine and Shift-Left Agent based on execution mode.

Source: https://totalshiftleft.ai/help-center/product-documentation/proxy-settings

## Proxy Settings

*Configure proxy servers for API testing. The appropriate proxy will be automatically used based on your selected execution mode.*

Use this screen when outbound API traffic must go through a corporate proxy. For the **engine URL** and **Reconfigure** flow, see [Server Connection](/help-center/product-documentation/server-connection).

Where to find everything: [Administration Settings](/help-center/product-documentation/administration-settings).

## Actions

- **Reset to defaults** — restores proxy settings to defaults (top right of the section).  

## Engine vs Agent

Two side-by-side areas:

| Area | Purpose |
|------|---------|
| **Shift-Left Engine** | Proxy for tests that run **on the engine** (scheduled and manual server-side execution). |
| **Shift-Left Agent** | Proxy for tests run **locally** through the desktop application. |

In each area:

- **Enable proxy** — turn proxy routing on or off for that execution path.  
- **Save settings** — apply changes for that card.  

**Proxy configuration** (information footer): explains that settings differ by execution mode and that **proxy authentication uses HTTP Basic Auth** (when your proxy requires credentials, configure them per your deployment’s fields).

## Practices

- Set engine vs agent proxies to match how your teams actually run tests.  
- Validate proxy credentials before large scheduled runs.  
- Disable proxy when not required to reduce latency and failure points.  

## Related documentation

- [Server Connection](/help-center/product-documentation/server-connection)
- [Execution mode](/help-center/product-documentation/execution-mode)
- [Public API](/help-center/product-documentation/public-api)