The previous tenants hand back their keys. The new tenant can already register in an app and operate the agreed lighting. Still, one answer is missing in the handover record: who confirms which previous apartment-related accesses were terminated and which personal contents will not be passed on? Organise this question as a coherent change order.
Specify the actual scope of the tenancy
First note which digital functions belong to the apartment being handed over. Separate them from the private devices of the departing person and from communal installations. For each affected function you need an appropriate system designation and an actually responsible party. An unknown device is clarified first before anyone makes changes to it.
Ask the responsible support which roles and access paths exist in the specific system and how a user change is envisaged. This can also include issued access media. The overview describes only your procedure; it contains no passwords, secret codes or data of other residents.
Coordinate a change order instead of sharing passwords
The Police Crime Prevention recommends distinct profiles with the respective necessary rights for shared device use. It also recommends changing default passwords and deleting your own data before passing on smart devices. [POL] These general tips do not replace instructions for your specific system.
Agree with the responsible party what should be prepared before the change, what should be changed at the agreed time and how the result will be confirmed. Ask explicitly about previous apartment-related authorisations, new permissions and personal data. The previous tenant should be able to clarify the prescribed route for their private accounts themselves with the responsible support. Do not request a personal master password as a shortcut.
A case with an incomplete success report
In the fictional case a new tenant receives an invitation for an already existing lighting control. The normal operation attempt succeeds. The landlady could now mark the point as completed. Instead she checks her working record: the confirmation regarding the former user access is still missing; it is also unclear whether an additional access medium belongs to the same process.
She queries these two points with the named system support. The tenant receives an agreed contact for follow-up questions while the change item remains open. Only the concrete answer regarding the affected system supplements the successful operation attempt. The example does not claim any specific technical connection between the app and the access medium.
Record operability and confirmed rights change separately
A normal operation test initially shows which agreed function could be used at that time. It alone does not answer all previously raised questions about old authorisations and data. Therefore record observation, confirmation by the responsible party and any unresolved remainder side by side.
Do not perform a general factory reset or a change to important residential functions following a third-party quick guide. Have the prescribed system route and any necessary interim solution explained. This article contains no technical reset or deletion instructions.
Complete the process in a traceable way
The completion information states the handed-over functions, the confirmed change status and the regular fault contact. If a question remains unresolved, assign it a responsible person and an agreed next step. This makes it clear which parts of the handover are actually confirmed. Such organisation is neither a security certification nor a statement about the landlord's legal access rights.