Sites
Since v3.38.0 every customer can have several sites (e.g. office, warehouse, data center, laptop cart). Hosts of all modules can be assigned to a site. Jobs can be limited to one site, and scripts get the site via placeholders.
Creating sites
- Administration > Customers, click the customer, tab Sites. Create, rename or delete sites with name and address. Each site shows how many hosts of which module it holds.
- Directly on the host: detail panel, tab Overview, field Site. A new name is created there and assigned right away.
A site always belongs to exactly one customer. If a host changes customer, it loses its site.
Assigning hosts
| Way | When |
|---|---|
| Detail panel > Overview > Site | single host |
| Select hosts > Set site | many hosts of one customer at once |
All host lists have a Site column (show it via the column picker). It can be filtered and searched like any column.
Jobs for one site
In the job form under target Customer, a second field appears after choosing the customer: All sites (default) or one site. The job then runs only on hosts of that site. The job list shows the target as Customer · Site.
If a site is deleted, Control deactivates jobs that target only that site. A site job never silently becomes a job for the whole customer.
Placeholders in scripts
| Placeholder | Value |
|---|---|
{{standort.name}} (Tactical: {{site.name}}) | site name |
{{standort.adresse}} | address |
{{standort.NAME}} | site variable NAME (Automation > Script variables, tab Site) |
If a host has no site, a script using {{standort.x}} does not start on it and names the missing variable.
OPNsense: former site field
Up to v3.37 OPNsense had a free-text field Site. The update to v3.38.0 turns these texts into real sites per customer and assigns the firewalls. The free-text field is gone from the UI.
Installer links (since v3.49.0)
In the customer panel on the tab Installer links you create an install command per device type (Windows, Linux, macOS, Proxmox, OPNsense). Agents installed with it land directly with this customer – optionally with site and groups – so provisioning profiles and onboarding jobs apply right away.
| Setting | Effect |
|---|---|
| Site, groups | assigned to the new host during installation |
| Device type | link only valid for this type (empty = all) |
| Valid | 1 to 365 days, afterwards the link is worthless |
| Max. installs | empty = unlimited |
The link is visible only when created; Control stores only a hash. Customer, site and groups come only from the link, never from the install command. You can revoke it at any time; installed agents stay. Every installation is in the audit log.