Smart Home Website
Tip

Who Controls the House?

Automation Smart Home Website Smart Home Website #routines#privacy

Most smart homes have one admin and everyone else lives in it. Here's how roles, cameras, locks and voice profiles should be split.

Who Controls the House?

Prices in this article are typical U.S. retail, checked October 2026.

Section 1: Who owns the smart home when more than one person lives there? (Introduction)

A multi-user smart home needs roles, not one admin account: owners, residents, guests and services each get the access they need, and remove people when they leave. Shared homes also need agreed rules for automations, guests and revoking access later.

Most smart homes are installed by one person and then lived in by several. The installer is the admin: the account owner, the person with the app, the one who knows which automation turns the hallway light on. Everyone else gets a login, or a code, or a voice assistant that does not recognize them.

The imbalance is structural. The person who installs the hub, creates the account, and pairs the devices becomes the permanent owner of the digital house, even if they are not the person who manages the household. The partner who does most of the everyday living gets a member login and no say in the automation that turns the lights off at 11 p.m.

That works until it does not. A roommate moves out with the front-door code. A teenager can unlock the door from a phone at school. A guest is added as a full admin because the invite screen did not explain the difference. The camera timeline is visible to everyone in the household, including the babysitter.

The fix is not a more complicated system. It is deciding, before the invitations go out, who needs which permission: control of devices, access to cameras, ability to add or remove people, and a voice that the assistant recognizes. The platforms already support most of it; the household has to use it.

This guide covers the role models in the major ecosystems, the four permission layers, onboarding, and the harder job of offboarding. For the wider routines library, start with the Automation hub.

Section 2: What roles does each platform offer?

The names differ, but the shape is consistent: an owner or admin, a member, and a guest.

Apple Home

Apple’s Home app uses a shared home with people you invite. The support documentation describes Residents as people with local and optional remote access to all accessories, and the owner can edit permissions for each person, including whether they can add and manage people and accessories or only control what is already there.

That distinction is the important one. “Can control the house” and “can change the house” are different permissions, and most households give both by default.

Google Home

Google’s Home app uses Admin and Member roles. An Admin can add and remove people, delete the home, add and remove devices, and share devices with partner services. A Member can control devices, with optional access to Activity (including camera history) and Settings.

The Member role is the right default for a partner, a roommate, or an older child. It gives control without giving the ability to remove the owner or rewire the house.

Alexa

Alexa’s model is less about roles and more about profiles. Alexa Profiles give each person in the home an individualized experience, and a Voice ID lets the device recognize who is speaking. Amazon Family links adult accounts to share eligible content and devices, while profiles remain associated with the account that created them.

The practical effect: a household can share the devices without sharing every preference, calendar, or shopping list. It is a personalization layer, not a security boundary.

The shared-home nuance

A single-platform household is the simple case. A household with two ecosystems — an Apple Home for the locks, a Google Home for the speakers — has two member lists and two places to revoke access. Matter was supposed to reduce that duplication by letting one device join several ecosystems, but multi-admin still means multiple fabrics to manage.

The practical rule: keep one ecosystem as the system of record for people, and treat the second as a control surface. When someone leaves, remove them from both, but start with the one that owns the locks and cameras.

Home Assistant

A local hub has the most explicit model: an owner account, additional users, and admin or non-admin privileges. The authentication documentation covers users, groups, and long-lived access tokens. The Person integration is separate: it represents a person for presence and tracking, not a login.

That separation is useful. A person can be “home” without having an account, and an account can exist without being a person. The household should decide which is which.

Section 3: What are the four permission layers?

Roles are the first layer. The other three are where most of the risk sits.

1. Devices and scenes

Who can turn things on, and who can change the rules?

  • Control: everyone in the household.
  • Create and edit automations: the adults, or whoever maintains the system.
  • Add or remove devices: the admin only.
  • Delete the home or the account: the owner only.

A member who can edit automations can create a rule that unlocks the door at midnight. That is not a device permission; it is a rule permission, and it is usually granted by accident.

2. Cameras

Camera access is the permission most likely to be overshared.

  • Live view: adults and caregivers, as needed.
  • Recorded history: the people who need it for the household’s safety, not every member by default.
  • Download and share: the owner, or a named person.
  • Adding or removing cameras: the admin.

If the platform supports per-camera sharing, use it. A camera in a home office should not be visible to a teenager’s account just because the account is a member of the home.

3. Locks and access codes

Locks have their own permission model, and it is usually separate from the home app.

  • Permanent codes: household members only.
  • Temporary codes: guests, cleaners, contractors, with an expiration date and a named owner.
  • Lock history: the people who need to know who came in, which may be fewer than the people who can unlock.
  • Remote unlock: a deliberate permission, not a default.

The guest-access guide covers the scheduling and revocation details, including the cloud dependency that can make a code fail offline.

Notifications

Notifications are a permission too. A household member who gets every camera alert, every door unlock, and every leak warning is a member with a second job. Split them:

  • Security events to the adults.
  • Device offline and battery to whoever maintains the system.
  • Delivery and doorbell to whoever is home.
  • Leak and freeze to everyone, because the cost of missing one is high.

Most platforms let each phone choose its own notifications, which is better than one household setting.

4. Voice and personalization

A shared speaker in the kitchen hears everyone. Voice ID and profiles let the assistant personalize responses, but they do not make the device private.

  • Voice purchasing: off by default, or protected by a PIN.
  • Calendar and messages: personal accounts, not the household account.
  • Music and lists: shared or personal, decided per service.
  • Announcements: useful, and also a way to broadcast to every room.

The rule: a shared device in a shared room has no privacy. A device in a bedroom should be muted or physically disabled when privacy matters.

The permission matrix

Action Owner Admin Member Guest
Control lights and scenes Yes Yes Yes Named devices
Create or edit automations Yes Yes No No
Add or remove people Yes Yes No No
View camera history Yes Yes Optional No
Unlock remotely Yes Yes Optional No
Add devices Yes Yes No No
Delete the home Yes No No No

The exact labels differ by platform; the pattern is the point. The rows people most often grant by accident are “create automations,” “view camera history,” and “unlock remotely.”

Section 4: How do you add a household member without giving away too much?

Adding someone is a five-minute job if the household has decided the permissions first.

  1. Decide the role. Admin, member, or guest. Write it down; the platform’s label is less important than the intent.
  2. Invite the right account. A personal account, not a shared one. Shared logins destroy the audit trail and make offboarding impossible.
  3. Set the device scope. Whole home or a subset, especially for cameras and locks.
  4. Add the lock code separately. A home-app invite does not create a door code; the lock app does.
  5. Train the voice. A voice profile makes the assistant usable; without it, the device treats everyone as the owner.
  6. Test the limits. Ask the new member to try something they should not be able to do — view a camera, add a user, unlock remotely — and confirm it fails.

That last step is the one people skip, and it is the only way to know the permission actually applied.

Section 5: How do you remove someone completely?

Removing someone is where smart homes fail quietly.

  • Remove the account from the home, not just the app from the phone. An uninstalled app does not revoke access.
  • Revoke the lock codes and check the lock’s user list, not just the home app’s member list.
  • Check the camera history. Some platforms keep shared clips after the member is removed; review the retention settings.
  • Change shared passwords if the person knew them, and turn on two-factor authentication for the owner account.
  • Transfer ownership carefully. A house sale or a breakup may require transferring the home to a new owner, which is a different operation from adding an admin. Follow the platform’s transfer process, and factory-reset devices that will stay with the house.
  • Remove the voice profile from shared speakers if the person had one.

Selling the house or ending a household

A move-out is not only a relationship event; it is an access event. The person leaving may have had the owner account, the lock codes, the camera app, and the voice profile. The new owner needs a transfer, not an invite, and the devices that stay with the house should be factory-reset and re-paired rather than handed over with the old account attached.

The same applies to an estate. A home full of accounts is a digital asset with no central registry unless someone made one; the documentation guide covers the inventory that makes the transfer possible.

The shared-account trap

A household that uses one account for everything — streaming, shopping, smart home — cannot remove one person without disrupting everyone. The fix is to separate the smart home account from the shared media account, and to give each adult their own login with the appropriate role.

Section 6: What should you set up, and when should you review it? (Conclusion)

  1. Name the roles before inviting anyone. Owner, admin, member, guest.
  2. Use personal accounts. No shared logins for the smart home.
  3. Separate control from configuration. Members control; admins configure.
  4. Scope cameras and locks explicitly. They are not the same permission as lights.
  5. Test the limits after onboarding. Try what should fail.
  6. Offboard in full. Account, codes, voice, history, passwords.

The review should be annual, and it should happen before a change, not after: a new roommate, a breakup, a child getting a phone, a caregiver starting. Each is a permission event, and each is easier to handle before the person has the access than after.

Some households do not need the complexity. A couple with no cameras, no locks, and one shared speaker can run everything as two admins and be fine. The roles matter when there are children, roommates, caregivers, or guests — which is most houses eventually.

A smart home is a shared resource, not a personal gadget. The permissions should reflect that.

Where to buy

Smart locks on Amazon

Opens an Amazon search. As an Amazon Associate, we earn from qualifying purchases. No product in this guide was supplied or tested by a manufacturer.

Sources