Possession and control are different parts of the asset
Owning the hardware does not automatically place it in the correct management organization or confer every administrative permission. Modern platforms can separate device adoption, site administration, account ownership and subscription management. Each relationship affects a different future action.
Ubiquiti's documentation makes one distinction concrete. Supported UniFi OS consoles have an ownership-transfer process performed by the Owner account, while self-hosted UniFi Network servers use administrators rather than that same owner model. A handoff instruction copied from one deployment type can therefore be wrong for another.
The useful installation record identifies the actual management arrangement. It should be possible to tell where the device is managed, which organization controls the relevant account and who is authorized to change access. A generic note saying credentials provided is too imprecise to establish those facts.
A login test does not establish the necessary authority
A customer may be able to view devices and still be unable to add administrators, transfer ownership or manage another relevant part of the deployment. The existence of a working login can hide that gap if acceptance checks only the dashboard's opening screen.
The right test follows the responsibilities being handed over. The organization needs the authority required for its operating model, while a support provider should have the access needed for the agreed work. Those do not have to be the same role, and broad shared access is not the only way to make support convenient.
This distinction also improves accountability. Named access lets the organization relate administrative activity to the responsible party. A shared password can make an urgent handoff feel simpler while making later changes harder to attribute or revoke selectively.
Recovery needs to survive the person who performed setup
A recovery address controlled by one employee creates a dependency on that employee's continued availability. A locally managed credential can have different recovery options from a cloud account. The organization should understand which mechanism actually applies to its deployment.
Ubiquiti distinguishes UI Account recovery from local-only and standalone credentials, with important limitations when the latter cannot be recovered. The narrow lesson is that a password reset is not a universal fallback. Losing the relevant access can require a disruptive rebuilding process on some deployments.
The practical response is to establish an authorized, securely maintained recovery path as part of delivery. That does not mean circulating sensitive credentials in work orders. It means ensuring the organization can obtain the right access through its own approved process when the installer is no longer present.
Provider changes should not require rediscovering the estate
When support changes hands, the customer needs more than a list of serial numbers. The incoming team must understand the management location, supported configuration, backup arrangement and remaining provider dependencies. Otherwise, changing a service relationship becomes an unplanned technical migration.
This is one reason to keep the customer's administrative control explicit even when a provider performs daily management. Delegated access can support the service while preserving the organization's ability to change providers or internal responsibilities. The exact arrangement should match the platform and the agreement.
Removal of old access also needs a sequence. Revoking the outgoing administrator before the receiving team has tested its authority can create a gap. Leaving obsolete access indefinitely creates a different problem. A complete handoff establishes the successor's control and then closes the prior relationship deliberately.
Installation acceptance should include the operating handoff
The device's connectivity result and its administrative handoff are separate deliverables. Both matter to the installed service. The organization should be able to identify its authorized operators, exercise the necessary management role and locate the approved recovery and configuration records.
Cartennas's conclusion is that administrative ownership belongs in the definition of installed. A device that works today but cannot be managed tomorrow leaves an unfinished dependency behind. Making control and recovery explicit at delivery prevents a routine staffing or provider change from becoming a network emergency.