# Target Settings
**Target Settings** page allows you to make the changes on the selected target. **All fields are configurable**, the only exception is the connection type, which cannot be edited.
## Connection Configuration
Whenever you make changes to your application that require an connection update, you can do so in the **“Configure Connection”** tab. Once you decide to save your changes, the test connection process will begin. You’ll only be able to save your changes once the connection is successfully established.
## Target Configuration
If you need to do the updates on the target's configuration, such as modifying the base language for your chatbot, make the necessary changes and click the "Save" button.
For more information about the connection types and target configuration, revisit the [Connection Setup](https://docs.probe.splx.ai/ai-red-teaming/probe/target/add-target/integration-setup), and [Target Configuration](https://docs.probe.splx.ai/ai-red-teaming/probe/target/add-target/target-configuration) pages.
## Actions
Located in the top-right corner of the target settings, the **Actions** dropdown provides the following options:
### Notifications
* Enable email notifications by default for each test run on the selected target.
* After a test run completes, the user who initiated the run will receive an email with test run details and the generated report.
* Notifications can still be enabled or disabled for a specific test run.
### Duplicate Target
* Create a duplicate of the selected target in a specified workspace with a new name.
* Copies both the target and its probe settings.
* Files uploaded as part of probe or target settings are not copied to the new target instance.
* Test runs are **not** copied.
* Useful for cases with minor variations, such as:
* Deploying the same app in staging and production environments.
* Reusing the same probe settings across different targets.
### Worker Pool
#### Availability
The **Worker Pool** feature is currently available only to **enterprise customers** who choose our **VPC deployment option**.
It enables hybrid deployment approach, where the worker resides inside the client’s own infrastructure. This allows attacks to be executed in the customer’s **private environment**.
#### Creating a Worker Pool
Before you can assign a worker pool to a target, you must first create it at the **workspace level**.
1. Open **Settings**.
2. Navigate to the **Workspaces - Overview** page and select the workspace in which the target is located.
3. Go to the **Worker Pool** tab.
4. Click **Create Pool** to add a new worker pool.
Figure 2: Workspace Overview Page, Worker Pool Tab
For the existing pools, you have the following options:
* **Set as Default** - makes the pool the default for the workspace. Only targets created after this change will use it automatically. Existing targets keep their current worker pool and must be updated manually.
* **Delete** - removes a pool you no longer need.
{% hint style="warning" %}
[To change worker pools for existing targets](#assigning-a-worker-pool-to-a-target), you must update each target manually in **Target Settings**. Open the target, go to **Actions**, and select the desired worker pool from the dropdown.
{% endhint %}
{% hint style="info" %}
There is always one pool named **Default Worker Pool** that cannot be deleted. This is the built-in worker that sends attacks from your VPC to the Cloud.
{% endhint %}
#### Assigning a Worker Pool to a Target
Once a worker pool has been created, it can be assigned directly in the **Target Settings**. Choose the target, go to **Target** **Settings**, click on **Actions** and select the desired worker pool from the dropdown list.
{% hint style="info" %}
When a target is assigned to a **hybrid worker pool**, it is expected that the **Test connection** check will show as failed.
{% endhint %}
Figure 3: Target Settings Page
### Delete Target
* Permanently deletes the target, including all associated probe settings and test runs.
* **Warning: This action is irreversible. It deletes the target, its probe settings, and its test runs.**
.png?alt=media&token=db5e111c-7051-47e4-96f3-90e52a02034b)
