The access question

For every person and linked service, who owns or administers the home, who can control or view devices and data, who can invite others, and who can revoke access?

The useful result is a named access matrix, not a shared password. Record the platform owner or administrator, each member and role, affected devices, data, and features, third-party services, the recovery account, the revocation path, region, and app or operating-system version.

Stop condition: if a role, invite, recovery, unlink, or removal path is not documented for the current platform and region, record UNKNOWN or VERIFY. Do not share credentials or infer that a similarly named role has the same powers on another platform.

Branch by the platform actually used

Keep platform roles and linked services separate
BranchIdentifyVerifyDo not infer
Google HomeHome structure, administrator/member role, current app and regionDevice/settings/activity access; invite and member-removal pathGoogle's role labels do not define Apple or Amazon access.
Apple HomeHome owner, resident or guest, current OS and regionAccessory/control scope; add/remove path; remote-access dependenciesResident and guest behavior does not transfer to another platform.
Amazon AlexaAmazon account, household/device context, skill or serviceIdentity association, skill account-link and unlink path, recoveryAccount linking does not establish a universal household role.
Third-party serviceService account owner, scopes, connected platform and regionLink, unlink, token/revocation path, and residual accessRemoving a household member may not revoke a separate service link.

Build and test the matrix

  1. Inventory individual identities. Give each person and service a separate row; never put a shared credential in the record.
  2. Attach the exact role. Copy the current platform label, region, and version, then list control, viewing, settings, activity, invite, and removal powers.
  3. Separate account links. Record who can link and unlink each third-party service and what identity or data it joins.
  4. Test least privilege and exit. Use only the access needed. Verify recovery and revocation without exposing secrets.
  5. Classify the row. Documented and tested access is PASS. Excess or inseparable access is BLOCKED. An untested or missing path is VERIFY or UNKNOWN. A capability outside that row is NOT_APPLICABLE.

Complete the household-access, account-link, and revocation record

Complete one copy per person or linked service. Do not enter passwords, recovery codes, tokens, or other secrets. Values are not submitted or saved.

Evidence boundaries

Google's current home-sharing and permission guidance defines access through Google Home roles and permissions. Those labels and capabilities are specific to Google's documented platform state.

Google's third-party account connection guidance treats linked-service access and removal as a separate control path; removing household access must not be assumed to remove every third-party connection.

Apple's Home invitation guidance distinguishes residents and guests and documents owner-managed access. Apply it only to the stated Apple software and home configuration.

Amazon's account-linking documentation describes linking an Alexa customer identity with a service identity; the authorization and unlink behavior remains service-specific.

Cross-platform boundary: do not transfer owner, administrator, member, resident, guest, household, skill, or linked-account powers between Google, Apple, Amazon, or a third-party service. Verify the current region, version, role, and revocation path independently.

Use the completed record

This owner maps identities, roles, linked services, recovery, and revocation. It does not recommend a device, authorize shared credentials, or promise that different platforms expose equivalent controls.