Admin: Factory Allocation

Factory Allocation is where newly-provisioned units — devices that came off the production line but haven't been assigned to a customer yet — get allocated to an organization and, optionally, given their relay configuration in the same step.

Authorization

Factory Allocation only appears in the navigation menu for Super-Users. The underlying allocate action itself only requires Admin+ server-side, but in practice you need Super-User to reach this screen at all.

Unallocated stock

Opening Factory Allocation shows the Unallocated Devices step: every provisioned unit that hasn't yet been assigned to an organization, with:

• Device ID (MAC)
• Type (e.g. coppelbox)
• Relay count
• Provisioned date

If there's nothing to allocate, the screen shows "No unallocated devices — All provisioned units have been allocated to an organisation." Use the refresh icon in the header to re-check the list at any time.

Allocating a device to an organization

Click Allocate on a device row to move to the allocation form. You'll need:

• Organisation (required) — pick the destination organization from the dropdown.
• Device Name / Site (required, minimum 3 characters) — defaults to the device's ID but should be replaced with something meaningful (e.g. "Titchfield Main Panel").
• Location (optional) — free text, e.g. "Building A, Floor 2".
• SIM CCID (optional) — if the unit has cellular connectivity.

Once you click Allocate Device, the unit moves from unallocated to allocated, and you land on a done screen summarizing the device ID, name, organization, location, and status. From there you can Allocate Another or close the dialog.

Applying a config at allocation

After you pick an Organisation, the "Apply Config Preset (optional)" dropdown loads that organization's presets. Selecting one means:

• The relay configuration from that preset is written to the device immediately after allocation, and the config version (rlyCfgV) is bumped.
• The organization used for allocation is the one you explicitly selected on this form — a preset's own "allocate to" target org (if it has one) is not used to override your choice here, so you won't get a conflicting double-allocation.

If no organization is selected yet, the preset dropdown shows "Select an organisation first to load presets." If the chosen organization has no presets, it shows "No presets defined for this organisation yet."

If applying the preset fails after the device itself was successfully allocated, the allocation still stands — the done screen shows a warning ("Preset apply failed: ...") rather than rolling back the allocation. You can apply the preset again afterwards from Config Presets.