Skip to main content

Multi-branch setup with groups

A business with several branches puts its devices in groups and sets the configuration once per group instead of once per computer.

Groups​

Dashboard → Devices → Groups. Groups can be nested, for example:

Organization
├── Haiti
│   ├── Port-au-Prince (group)
│   └── Cap-Haïtien (group)
└── Miami (group)

An activation code can put new devices straight into a group. You can also move a device to another group later.

Config profiles​

The agent configuration is merged in this order, later wins:

  1. system defaults,
  2. the organization profile,
  3. each parent group, from the top down, then the device's own group,
  4. the device profile.

So a setting for all branches goes in the organization profile, a setting for one branch in its group, and an exception for one computer in the device profile. Profiles are partial: set only what differs.

Example: every receipt printer uses alias receipt, but the Cap-Haïtien branch prints on 58 mm paper.

Organization profile:

{ "security": { "allowedOrigins": ["https://pos.example.com"] }, "ui": { "locale": "fr" } }

Group "Cap-Haïtien":

{ "printers": { "defaults": { "prn_7f3a": { "paper": "58mm", "codepage": "CP858" } } } }

Device profile of the till with a second printer:

{ "printers": { "aliases": { "receipt": "prn_7f3a", "kitchen": "prn_91cc" } } }

Dashboard → Devices → device → Config shows the merged result and which layer each value comes from. Before you save a profile, the dashboard shows how many online devices the change reaches.

How changes reach the agents​

The cloud sends the merged configuration with a hash. When the hash changes, the agent reloads it without restarting, within seconds for online devices, and at reconnection for the others.

Every setting is described in the config reference.