Permissions must be easy to grant temporarily and revoke

What it is

Household permissions are mostly temporary in shape: tonight's babysitter, the weekly cleaner, a relative staying a week, a neighbour watering the plants. These grants should exist while the person is there and lapse when they are not — but if the formal delegation flow is heavy (install an app, register, pair, teach), users route around it and simply hand over the master account password. The everyday usability of granting and revoking — the domestic face of access delegation — is therefore not polish but the precondition for any permission layering to exist: once the official channel is costlier than sharing a password, the layering exists in name only.

Why it happens

This is security economics at household scale. Users pick the cheaper of two paths — formal delegation (multi-step operation plus the other party's learning cost) versus sharing the master credential (one sentence). The expensive one loses, and the system degrades to "everyone is an admin".

Revocation matters more than granting, because grants rot: the tutor stops coming, the cleaner changes, the relative goes home — the grant loses relevance, but nobody goes cleaning up unless revoking is a single action. Stale grants accumulate month over month and the permission perimeter quietly widens. One more layer: the right to grant must itself be delegable — the parent arranging the babysitter is often not the account admin; if every grant must pass through the admin, the admin becomes the household bottleneck and people take the password-sharing shortcut instead.

Studying it

• Smart-home access-control surveys (described generically): the largest reported friction concentrates on "letting a new person in" — the complexity of onboarding visitors is among the most-cited abandonment reasons; master-account sharing is consistently documented in surveys and interviews.
• Usable-security metrics: borrowing from usable security research, use time and error rate as the usability measures of a security mechanism — time from "this person needs access" to "they can actually use it", time from "no longer needed" to "the access is actually gone", and error and abandonment rates along the way.
• Variables: grant latency, revocation latency, count of expired-but-live grants (unused since long ago), proportion of households reverting to password sharing.

Where it stops holding

• Convenience must not be bought with ambiguity: one-tap granting that hides scope hands over full permissions while the grantor believes they gave "turning on lights". Usability presupposes that the scope is visible at the moment of granting.
• Some roles need durable access (live-in carers, long-term housemates); framing every grant as "temporary" misfits them. The usability design has to hold temporary and standing grants simultaneously.
• However easy revocation is, it is useless if the grantor has forgotten the grant exists: invisible grants are never revoked. The usability checklist must include "active grants visible at a glance".

Applying it

• Put the granting entry on the everyday surface (the home panel or main screen), completable in 30 seconds; never require the other party to install an app — voice, panel PIN, a temporary passphrase all work.
• Show scope in plain language at grant time ("can turn on lights and heating; cannot view cameras or change settings"), with templated scopes instead of free-form permission forms.
• Keep a standing active-grants list on the main surface: who holds what, last used when; revocation is one action; non-admin members can grant within their own scope.
• How to check: count zombie grants (unused for weeks) and the latency from "the role ended" to "the permission disappeared"; spot-check the active-grants list for accuracy. Zero zombies is unrealistic, but steady growth means the layering is being bypassed.

Related

• Same group: Z6.02.1 Residents, guests, and children need different permissions · Z6.02.3 Concentrated admin control creates dependence
• Nearby: Z4.08 Guests and temporary authorisation · Z2.04 Presence and identity recognition
• Search terms: access delegation · usable security · permission revocation · smart home onboarding