Before you start
- Identify the physical device by model, serial, MAC, and current branch.
- Review active vouchers and packages attached to the device or branch.
- Do not release a device only to fix connectivity.
Procedure
Follow these steps in order
Move to another branch
Use Move device when ownership stays with the same customer. Select the destination branch, review package compatibility, and confirm the move.
Archive temporarily
Archive when the customer still owns the device but it is not in active service. Monitoring stops and the record remains available in Archived devices.
Restore an archived device
Open Archived devices, select Restore, choose the correct branch, and recheck packages and connectivity.
Release ownership
Release only when the device is sold, transferred outside the workspace, or permanently removed from K7abeer. Enter the reason and complete the protected backup/cleanup workflow where supported.
Hand over to another customer
Complete release and sanitization first, then the receiving customer adds the device to their own branch. Ownership cannot be silently reassigned between unrelated accounts.
Review vouchers
Before release, export required records and decide whether unused vouchers remain historical, are disabled, or must be regenerated under the destination gateway. Never assume a vendor controller moved them automatically.
Verify success
- The device appears in only one active branch.
- Archive records are available under Archived devices.
- Release removes active ownership only after confirmation.
- Audit history records who performed the action and why.
Troubleshooting
Move is refused
Check destination branch ownership, device state, active operations, and package assignments. Resolve duplicate or incompatible mappings before retrying.
Release cleanup times out
Restore device connectivity and retry cleanup. Use support escalation only when a physical reset or independent sanitization has been verified; do not force release casually.
Was this guide helpful?
Your response helps the system owner prioritize documentation updates.