---
url: https://veles.beyondthecloud.dev/docs/setup/connect-production.md
description: >-
  Add a second production org to the Hub, manage its sandboxes, or let it run
  its own Veles as a sub-hub.
---

# Connect another production or a sub-hub

Most companies have one production org and one Hub. If you have several production orgs, you have two options.

## Another production, managed by this Hub

The Hub pushes configuration to the other production and manages that production's sandboxes. The other production needs Veles installed and its own [integration user and ECA](/docs/setup/integration-user) prepared (Step 1 of its Setup tab). It also needs its own Veles licence; see [Plans and pricing](/pricing).

On the Hub:

1. **Environment Management > New Environment > Add Production**.
2. Enter a **Label** and the production's **Instance URL** (its My Domain URL), then **Save**.
3. Open the row, set the **Integration Username** to that org's integration user, and click **Setup Environment**.

Veles pushes configuration to a production org but never runs workflows on one. To manage that production's sandboxes, add them with **New Environment > From Sandbox** and choose that production under **Import sandboxes from**.

## A sub-hub (Enterprise)

A production org that runs its own Veles, manages its own sandboxes and reports to your Hub. Use it when a region or subsidiary has its own admins. The sub-hub inherits configuration from your Hub through the groups you share with it and keeps everything else local.

On the sub-hub:

1. Complete Step 1 of its Setup tab.
2. In Step 2 choose **This org reports to a Master Hub**, enter your Hub's My Domain URL and your Hub's integration username, and click **Save Hub Configuration**.
3. Complete Setup.

On your Hub the sub-hub's row shows a **Sub-Hub** pill. Its sandboxes are managed by the sub-hub, so **Push** to them from your Hub is blocked with the note **Managed by its own Hub**. Pushes to the sub-hub itself travel on from there to its sandboxes one hop at a time.

Multi-hub needs the Enterprise plan on the Hub. Below it, the **Change Hub** window shows an upgrade prompt instead.

## Sandboxes of another production

Whichever option you chose, a sandbox always belongs to its real production: refresh requests go to that production, and refresh detection polls that production. Veles shows the link as an orange pill with the production's name on the sandbox row.