Back to Blog

Remove a Departing Roommate From Google Home and Third-Party Controls

Remove the departing roommate from Google Home, audit vendor accounts, clean automations, and test access from a remaining admin.

Remove a Departing Roommate From Google Home and Third-Party Controls

An administrator should remove the departing roommate from the correct Google Home, then audit linked third-party services, manufacturer apps, automations, presence settings, and physical access. Removing a person from Google Home closes that person’s membership in the selected home, but it should not be treated as a universal unlink button for every smart device account.

Schedule this while an administrator and the departing roommate can identify personally owned integrations. Do not share Google passwords or take over the other person’s accounts.

Remove the home membership in the right home

Open Google Home and confirm the home name at the top. Many people have test homes, an old apartment, or a relative’s home in the same app. Open Home settings, find the household or people section, select the departing roommate, and use the removal control available to an administrator.

Google’s official people and permissions guide explains that administrators can add, manage, and remove people, while members have more limited powers. It also describes the device, settings, and activity access associated with each role.

Refresh the people list after removal. Check that the email address is gone and that no duplicate invitation remains pending. If the person is an administrator, remember that broad access may have included devices, services, home settings, activity, and the ability to manage other people. Prompt removal matters when occupancy ends.

Do not delete the entire home just to remove one roommate. A home deletion affects remaining residents and configured devices. Use the member-level action unless the household is actually dismantling the whole setup.

Trace controls that live outside Google Home

Build an inventory by room: lights, plugs, thermostat, cameras, locks, robot vacuum, garage controller, and sensors. For each brand, note who owns the manufacturer account and whether Google Home reaches it through a linked cloud service, Matter, or another setup path.

If the departing roommate linked a manufacturer service from their own account, ask them to unlink their service or transfer ownership through the manufacturer’s supported process. The remaining administrator can reconnect using an account controlled by the continuing household. Google Home membership removal does not promise to change permissions in a separate vendor app.

For security-sensitive products such as locks, cameras, and garage controls, inspect the manufacturer app’s members, guest codes, shared links, and recovery contacts. Change physical keypad codes when appropriate. Avoid a blanket device reset until you understand whether it would erase schedules, footage settings, or access needed by remaining residents.

Ownership should be explicit. A smart bulb the roommate takes should be removed from the home and reset for its new location. A thermostat that stays should use an account and recovery address controlled by the continuing household or property owner.

Clean automations and presence behavior

Review household routines and automations for the roommate’s voice, schedule, devices, or presence. Remove obsolete personal actions and test safety-relevant routines manually. A “when everyone leaves” automation deserves special attention because the household roster and phones contributing to presence may have changed.

Check personal results, Voice Match, Face Match where applicable, media services, and subscriptions. Some personal settings belong to the departing account and some home-wide settings belong to the home. Work through the app labels instead of assuming one category covers all.

Finally, test essential controls from a remaining administrator’s phone. Confirm that lights, locks, cameras, and heating controls respond under the account that will stay. Testing reveals integrations that depended entirely on the departed account.

How HomeCo helps

At a weekly house meeting, assign one inventory owner and one test owner. HomeCo can list devices by generic room and brand, mark whether each stays or goes, and set a due date for membership removal.

Keep camera links, access codes, Wi-Fi passwords, recovery codes, and account credentials out of shared tasks. “Test front lock from remaining admin account” is sufficient. HomeCo helps expose unfinished handoffs without becoming a secrets vault.

Frequently asked questions

Is removing a Google Home member enough for a smart lock?

Not necessarily. Review the lock maker’s app, guest codes, physical codes, and ownership settings as separate access paths.

What if the roommate linked the device from their account?

Coordinate unlinking or ownership transfer in the manufacturer service, then reconnect through a continuing account if needed. Do not request their password.

Should we factory-reset every smart device?

Reset devices that leave, cannot be cleanly transferred, or require it under manufacturer instructions. For devices staying, inventory and supported ownership transfer may preserve useful settings while still closing access.

A reliable offboarding removes the person, traces outside accounts, cleans presence logic, and tests control from an account that remains in the home.