Claim Code Pairing
Edge appliances join your organization through claim code pairing. A Monozu technician (or your contracted installer) runs registration on the appliance; Monozu completes pairing to your tenant. As a customer administrator, you verify the device in Monozu Cloud — you do not create registration keys or run internal pairing tools.
| Who | Responsibility |
|---|---|
| Monozu technician (typical) | Power, network, SSH, run monozu edge register, share claim code with Monozu operations if needed |
| Monozu operations | Completes pairing of the claim code to your tenant |
| Your tenant administrator | Confirms the device appears Online under Edge Devices; edits label or location if needed |
What you do in Monozu Cloud
Section titled “What you do in Monozu Cloud”-
Coordinate with Monozu so your site network allows outbound access per Network & Connectivity.
-
After the technician finishes on-site registration, sign in to
https://cloud.monozu.io. -
Open Edge Devices in the main navigation.
-
Find the new appliance (by name, location, or registration time). Status should be Online.
-
Open the device and update label or location if your team uses those fields for operations.
-
Confirm licensed modules (VPN, backup, security) match your License — enable features in the cloud UI as documented for each module.
Claim code basics (customer view)
Section titled “Claim code basics (customer view)”- The technician sees a short claim code on the appliance console after running
monozu edge register. - The code is time-limited. If pairing is delayed, the technician may need to restart registration — contact Monozu support rather than attempting internal pairing steps.
- You never type the claim code in the customer UI; pairing is completed on the Monozu side.
Permissions
Section titled “Permissions”| Task | Typical permission |
|---|---|
| View Edge Devices | edge_devices.read (or Admin) |
| Edit label / location | edge_devices.update (or Admin) |
If the device stays Offline
Section titled “If the device stays Offline”| Check | Action |
|---|---|
| Pairing not finished | Contact Monozu — claim may still be pending |
| Firewall / proxy | Verify outbound HTTPS to cloud.monozu.io and api.cloud.monozu.io |
| Site network | Confirm WAN path and DNS; see Troubleshooting |