> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/admin/configuring-a-self-hosted-instance/configuring-worker-zones.md).

# Configuring worker zones

{% hint style="info" %}
**Required global permission:** Manage environment settings
{% endhint %}

On a self-hosted instance, you can configure a list of zones to assign Structural workers to. Each zone can contain one or more workers.

When zones are available, each workspace can be assigned a zone. When a workspace is assigned to a zone, then the workspace jobs are always routed to a worker in that zone. Workspaces that are not assigned to a zone are routed to a worker that is not in a zone.

Worker zones allow you to manage the job traffic on your instance.

## Displaying the list of zones

The list of zones is on the **Zones** tab of **Structural Settings**.

<figure><img src="https://3378426797-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSQCLFQ4bslJ-HYc8c3%2Fuploads%2FWMlT6lb5NhBTyXEbPKpw%2FZonesList.png?alt=media&amp;token=e85ce242-5a75-48d3-a332-4c3bc94fc991" alt=""><figcaption><p>Zones tab on Structural Settings with the list of worker zones</p></figcaption></figure>

For each zone, the list includes:

* The zone identifier. You use the identifier to [assign workers to the zone](#assigning-workers-to-zones).
* The zone name.
* The zone description.
* The number of workspaces that use the zone.
* When the zone was added.

## Adding a zone

To add a worker zone:

1. Click **Create Zone**.

<figure><img src="https://3378426797-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSQCLFQ4bslJ-HYc8c3%2Fuploads%2Ftu7QVi5VTZHRXmzywUVN%2FZoneCreate.png?alt=media&amp;token=09d1ae58-329f-4276-a566-53bf473110f6" alt=""><figcaption><p>Create Zone panel to create a new worker zone</p></figcaption></figure>

2. On the zone details panel:
   1. In the **Zone Name** field, provide a name for the zone.
   2. In the **Description** field, provide a longer description of the zone.
3. Click **Save**.

Structural generates an identifier for the zone and adds the zone to the list.

### Editing a zone

For an existing zone, you can edit the name and description. The identifier does not change.

To edit a zone:

1. In the zone list, click the edit icon for the zone.
2. On the zone details panel, make the edits to zone configuration.
3. Click **Save**.

## Assigning workers to zones

On each worker, to assign the worker to a zone, set the [environment setting](/app/admin/environment-variables-setting.md) `TONIC_WORKER_ZONE_ID` to the identifier of the zone.

The zone identifier is displayed on the **Zones** list.

## Deleting a zone

To delete a zone:

1. In the zone list, click the delete icon for the zone.
2. On the confirmation panel, click **Yes, delete zone**.

When you delete a zone, any workspaces that used that zone are updated to not use a zone.<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tonic.ai/app/admin/configuring-a-self-hosted-instance/configuring-worker-zones.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
