Account sharing

Permit multiple people to authenticate as one nominal account by reusing its credentials or authenticators, collapsing individual identity, accountability, and revocation boundaries.

Version

v2 · 2026-09-19 · History

Domain-specific #

1226

Domain group

Applied Sciences & Engineering

Origin domain

Computer Science & Software Engineering

Subdomains

Digital Identity, Shared Account Authentication → Computer Science & Software Engineering

Aliases

Credential sharing, Password sharing, Shared login

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.

How would you explain it like I'm…

One Card, Many Users

Imagine a library card with one person's name on it, and the whole family uses it with the same secret number. The library thinks just one person is borrowing everything. And if one person should stop using it, you'd have to change the secret number for everybody.

Sharing One Login

Account sharing is when more than one person uses the same online account by sharing its password, a login code or something similar. The website or app only sees one account, even though several people are really using it. That means it can't tell who did what, since everything is recorded under the one account. And to stop just one person from using it, you usually have to change the password for everyone. Some services allow sharing and some don't, and family plans that give each person their own login are different, because each person keeps their own identity.

Many People, One Identity

Account sharing is the practice of several people using one nominal digital account by passing around or jointly using its authenticator - a password, one-time code, login approval, token or similar. The service sees a single subscriber identity even though multiple people are acting through it. Whatever permissions the account has flow to every sharer, activity logs point to the account rather than a particular person, and removing one person usually means changing the shared credential for everyone. Whether sharing is allowed, tolerated, banned, pressured or informal varies, but the collapse of several people into one identity is the same in every case. It's different from a family plan with separate profiles and logins, from an account that gives each user their own credentials, and from 'secret sharing' in cryptography.

 

Account sharing is the use of one nominal digital account by more than one person through the transfer or joint use of its authenticator - password, one-time code, approval event, token or other credential. An enrolled account binds authenticators to a subscriber; sharing happens when the subscriber discloses a secret, hands over a device, relays an approval, or keeps a common credential store so another person can pass the same verifier challenge. The structural consequence is identity collapse: authorization attached to the account flows to every sharer, logs attribute actions to the account rather than reliably to an individual, and revoking one person usually means rotating the common authenticator for all. The policy status - permitted, tolerated, prohibited, coerced or informal - varies without changing that structure, and even consensual sharing weakens accountability and recovery. Formal household profiles and delegated roles avoid some of the collapse by keeping distinct identities, and a shared subscription is not necessarily shared credentials, as family plans may issue separate profiles and authenticators under one billing relationship. The term should also be distinguished from cryptographic secret sharing, federation across services, authorized multi-user accounts with individually attributable credentials, and ordinary sharing of content after access.

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

1. 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) — outgoing typed relations

• 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 → is a kind of Access Control → is a kind of Authority

Show alternative paths (2)

Neighborhood in Abstraction Space

Account sharing sits in a sparse region of the domain-specific corpus (98^th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (2769 abstractions)

Nearest neighbors

• Passwordless authentication — 0.77
• Claims-Based Identity — 0.76
• Authentication Failure — 0.76
• Multi-factor authentication — 0.75
• Secret Sprawl — 0.74

Computed from structural-signature embeddings · 2026-10-25