Account sharing¶
Permit multiple people to authenticate as one nominal account by reusing its credentials or authenticators, collapsing individual identity, accountability, and revocation boundaries.
Core Idea¶
Account sharing is the practice in which more than one person uses the same nominal digital account by transferring or jointly using its password, one-time code, approval event, token, or other authenticator. The service consequently observes one subscriber identity even though several human actors exercise access. Sharing may be permitted, tolerated, prohibited, coerced, or informal; those policy judgments vary, while the structural identity collapse remains.
An enrolled account binds one or more authenticators to a subscriber. The subscriber discloses a secret, transfers a device, relays an approval, or maintains a common credential store so another person can pass the same verifier challenge. Authorization attached to the account then flows to every sharer.
Scope of Application¶
The abstraction is literal wherever practitioners can identify the same constitutive roles, apply the same boundary tests, and obtain the same kind of output. The following habitats are uses of Account sharing itself, not metaphors based only on resemblance.
- Consumer subscriptions. Analyzing shared credentials separately from permitted household profiles.
- Enterprise systems. Identifying shared administrative or operational logins.
- Caregiving and assistance. Comparing informal credential transfer with supported delegation.
- Incident response. Explaining ambiguous actor attribution in account logs.
- Identity design. Providing multiple users scoped credentials instead of one shared secret.
- Policy analysis. Separating security, contract, accessibility, and household considerations.
Clarity¶
A clear account of Account sharing must preserve the recognition invariant stated in the Core Idea rather than rely on the title alone. State which authenticator is shared and whether separate profiles retain individual identity. Distinguish consent of the holder from authorization by the service or organization. Identify logging, revocation, recovery, and multifactor consequences. Avoid treating all household or assistive access as the same policy case.
Manages Complexity¶
Account sharing manages complexity by replacing a diffuse field of observations or possible operations with a bounded role structure: nominal account supplies one service-side identity holds entitlements and state.; bound authenticator supplies a password, token, device, or approval proves access.; primary holder supplies an enrolled or controlling person transfers use.; additional user supplies another person authenticates under the same nominal identity.; shared authorization supplies account entitlements become available to all successful users..
Abstract Reasoning¶
- Identify the account owner, intended subject identity, and entitlement set. 2. Trace how each human user satisfies authentication. 3. Determine whether the service records distinct actors or one nominal account. 4. Compare supported delegation, profiles, and role-based alternatives. 5. Assess consent, policy, accessibility, and legal context separately. 6. Map revocation and recovery effects when one sharer leaves or a credential leaks. 7. Document attribution uncertainty in any audit or incident conclusion.
Knowledge Transfer¶
The strict upward abstraction is Access Control. Account Sharing instantiates Access Control because multiple people obtain authorization by satisfying the verifier as one nominal account. Within shared account authentication, the full mechanism transfers literally when the same roles and boundary tests recur. Beyond that domain, only the parent-level skeleton should travel. Reusing the label Account sharing after removing its constitutive vocabulary would hide a change of mechanism behind an analogy. The honest transfer rule is therefore two-stage: recognize the domain-specific pattern first, then lift only the parent relation that remains invariant under a substrate change.
Relationships to Other Abstractions¶
Current abstraction Account sharing Domain-specific
Parents (1) — more general patterns this builds on
-
Account sharing is a kind of Access Control Prime
Account Sharing instantiates Access Control because multiple people obtain authorization by satisfying the verifier as one nominal account.
Hierarchy paths (3) — routes to 3 parentless roots
- Account sharing → Access Control → Authority
- Account sharing → Access Control → Boundary
- Account sharing → Access Control → Constraint
Neighborhood in Abstraction Space¶
Account sharing sits in a sparse region of the domain-specific corpus (97th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Unclustered & Miscellaneous (1565 abstractions)
Nearest neighbors
- Passwordless authentication — 0.77
- Authentication Failure — 0.76
- Light-weight Identity — 0.76
- Multi-factor authentication — 0.75
- Data Access Service — 0.75
Computed from structural-signature embeddings · 2026-09-08