← Back to catalogue
Published

Online Account

vr.wm-vrt-005 · wm-vrt-005-online-account

Describe one account within a service or virtual environment, including its governed identity, access relationships and lifecycle.

World Models Information and virtual systems INF.VRT.ACC

Bundle → Layer → Finding → Questions Filled

3 bundles · 4 layers · 5 findings · 10 questions

Account and holder What the account is and who controls it.

Account record

Identifier, service and status of the account.

Account identity

The service-scoped identifier and handle of the account.

  1. Which service holds the account, and under which identifier and handle?
  2. Is the account active, suspended, locked or closed?

Holder relationship

The person, organisation or agent that controls the account.

  1. Is the account held by a person, an organisation or a non-human agent?
  2. Is the holder's identity verified, and to what assurance level?
Authentication and access How the holder signs in and what the account can do.

Credentials and federation

Authenticators and linked identity providers.

Sign-in methods

The authenticators and federated logins bound to the account.

  1. Which authentication methods are enabled, and is multi-factor authentication on?
  2. Is sign-in federated through an external identity provider?

Roles and delegation

Permissions held and delegated access.

Permissions

Roles, scopes and delegated grants of the account.

  1. Which roles or scopes does the account hold in the service?
  2. Which third-party applications have been granted access, and with which scopes?
Lifecycle How the account is created, changed and ended.

Status and closure

Creation, suspension, recovery and deletion.

Closure and data

What happens to the account and its data at the end.

  1. Has the holder requested closure or deletion, and when?
  2. Which data remains after closure, and for how long?

Classifiers Filled

Family
World Models
Category
Information and virtual systems
Entry kind
entity
Navigation path
NAV.INF.VRT.ACC
Domain
INF.VRT.ACC
Industry
Cross-industry
Tags
onlineaccountinf.vrt.acc

What it is Filled

An online account is a record within one service or virtual environment that lets a holder sign in, keep settings and data, and act under the service's terms. It belongs to that service and is distinct from the person behind it and from a federated digital identity that may be used to sign in to many services.

In scope

  • Service and tenant-qualified account identity, aliases, class and observed direct properties.
  • Holder and administrator mandates, optional federation links and credential metadata references.
  • Account status, provisioning evidence, authorization and session references, recovery and closure dispositions.
  • Policy-qualified provenance, access views, export and retention records.

Out of scope

  • Person or organization master records, global federated identity, credential secrets and token values.
  • Protocol execution, remote account operations, incident investigation workflows and authentication certification.
  • Financial ledgers, content collections, subscription billing and virtual assets mastered elsewhere.

Why it exists Filled

Describe one account within a service or virtual environment, including its governed identity, access relationships and lifecycle.

Distinguishing features Filled

  • It exists within one service and is governed by that service's terms.
  • One person can hold many accounts, and an account can be held by an organisation or an agent.
  • Distinct from a federated digital identity, which can be used across services to sign in.
  • Distinct from a financial account, which holds monetary balances rather than service access.

What robots and AI may and may not do Filled

Must not

  • Obtain, store or reveal account passwords, recovery codes or session tokens.
  • Create accounts or sign in on someone's behalf without that person's authorisation.
  • Bypass verification, rate limits or bot detection of a service.
  • Link accounts across services to the same person without a lawful basis.
  • Close or delete an account without the holder's instruction.

Only with a human decision

  • Recovering access to an account after lost credentials.
  • Suspending or closing an account for terms violations.
  • Granting a third-party application access to the account.

May

  • Report the status, roles and connected applications of an account to its holder.
  • Flag weak authentication settings or unusual sign-in activity.
  • Help the holder export their account data through the service's own tools.

Moral aspects Filled

  • Accounts give access to private communications, purchases and personal data.
  • Losing access to an account can cut people off from services they depend on.
  • Linking accounts across services enables tracking and profiling of people.

Who is affected

  • Account holders
  • Service providers
  • Contacts and others whose data the account holds

Owners Filled

Steward

The service provider that operates the account system answers for its records and access controls.

Roles

Account steward
Maintain scoped identifiers, current profile pins and evidence quality.
Holder or mandated delegate
Supply evidence and request changes within the documented mandate.
Security reviewer
Review binding, recovery and access anomalies through restricted evidence views.
Privacy and retention reviewer
Approve data scope, audience rules, disposition schedules and exceptions.
Local automation operator
Run authorized local metadata functions with no remote account side effects.

Master systems

  • Identity and access management systems
  • Customer identity stores of online services

Links to other meta-models Filled

references

  • WM-PER-002 - Optional candidate link to a separately mastered federated identity; pin a reviewed neighbor version before operational binding. Registry relation remains candidate.
  • WM-PER-001 - Optional person holder reference when a reviewed deployment profile requires it; not every account is a person account and no identity proof is inferred.
  • wm-per-001-person - A person may hold many accounts.

neighbor

  • WM-PER-002 federated digital identity - An optional reference to a federated subject does not replace service-local account identity. Multiple bindings require separate authority and evidence; email equality cannot establish sameness.
  • Holder, administrator and public profile - The account record is distinct from the party that holds rights, the actor that operates it and a public-facing profile. Shared or non-human classes require explicit local policies, not inferred personhood.
  • Authenticator, session and authorization grant - These retain separate identities and lifecycles. Successful authentication does not imply permission, and ending a session does not establish revocation of all grants.
  • Financial account and service content - References to purchases, balances or content may be associated with this root, but their ledgers and resource masters remain outside this model.
  • world-r4-identity-register - Federated digital identity is held there; an account is local to one service.

related

  • wm-per-010-contact-point-party-profile - Accounts often carry contact points of their holder.

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • An account is identified by a service-scoped identifier, often with a user name, handle or email address.
  • Federated sign-in links it to an identity provider's subject identifier.

Direct properties not applicable Not applicable

Not applicable

An online account is a record in a service with no physical properties to measure.

Recognition optional Filled

  • An online account has a service-scoped identifier, a holder, authenticators and a status.
  • Often confused with the person, a federated digital identity or a public profile page.

Capabilities and actions required Filled

  • Accounts can be created, verified, suspended, recovered, merged and closed.
  • Accounts can grant scoped access to third-party applications.

Hazards and failure modes required Filled

  • Account takeover through phishing, credential stuffing or weak recovery.
  • Impersonation and fake accounts.
  • Lock-out and data loss when recovery fails.

Standards and interfaces required Filled

  • OpenID Connect and OAuth 2.0 for federated sign-in and delegated access.
  • SCIM (IETF RFC 7643 and RFC 7644) for account provisioning.
  • W3C WebAuthn for phishing-resistant authentication.

Context of use required Filled

  • Used in every online service, platform, game and enterprise application.
  • Subject to data protection law and to the service's own terms of use.

Sources Filled

  1. System for Cross-domain Identity Management: Core Schema - IETF
  2. System for Cross-domain Identity Management: Protocol - IETF
  3. OpenID Connect Core 1.0 incorporating errata set 2 - OpenID Foundation
  4. Digital Identity Guidelines: Authentication and Authenticator Management - NIST
  5. Best Current Practice for OAuth 2.0 Security - IETF
  6. Web Authentication: An API for accessing Public Key Credentials - Level 2 - W3C
  7. OAuth 2.0 Token Revocation - IETF
  8. PROV-O: The PROV Ontology - W3C
  9. NIST SP 800-63 Digital Identity Guidelines (NIST)
  10. OpenID Connect Core 1.0 (OpenID Foundation)
  11. RFC 7643 System for Cross-domain Identity Management: Core Schema (IETF)

Open questions

  • Restore independent external review before canonical or publishable-draft promotion.
  • Verify all source responses, exact versions, errata and update effects, then approve a bounded adoption profile including account class and legal-policy applicability.
  • Implement nested data contracts and adapters with fixtures for tenant collisions, alias reuse, issuer mismatch, stale updates, scoped revocation, disputed recovery and incomplete downstream erasure.
  • Independent second-provider review remains absent.
  • Direct HTTP checks are not attempted under the owner-reported sandbox restriction; statuses and response hashes are unmeasured.
  • Current errata, SCIM updates listed by the publisher, later WebAuthn editions and complete version/applicability review remain unresolved.
  • Nested instance schemas, adapters, deterministic permission evaluation and adversarial fixtures are not implemented.
  • Non-human, shared, guardian-managed and organizational account profiles, legal duties, portability, succession and service-specific terms require specialist review.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-vrt-005-online-account/spec.yaml, ver-cy/world-models/card-supplements/wm-vrt-005-online-account.json