Your account
HOL-D095Story implementation: In progress

Transfer organization ownership

organizations · Proposed launch phase 2

Start from Home

Review as Organization owner

User story

As a organization owner, I want to transfer ownership to another authorized person so the organization can continue when responsibilities change.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Only the current owner initiates the ordinary transfer. The verified recipient must explicitly accept through their own account before ownership changes.
  • Keep one current owner and change ownership atomically, with clear confirmation, cancellation, expiry and retry outcomes. A manager cannot self-promote.
  • Before completion, show the outgoing owner’s resulting access and require an explicit choice to retain manager access or leave the organization. Never silently retain ownership privileges.
  • Record the former/new owner, actor, acceptance, time and affected organization; preserve the public organization, history and both personal accounts.
  • Owner unavailable cases use the separate reviewed claim/recovery process D096/D097; disputes and exceptional overrides escalate to Platform administrator.
  • Keep ownership transfer in the named organization context with existing owner/recipient/revision checks. Personal profile/settings edits never transfer ownership or rewrite accepted org grants.

What to check in the demo

Follow these steps from the role’s landing page through navigation and feature checks.

Review asStart here: Home

Begin in a named organization workspace as its current owner. The local Organization owner choice uses Maya Hart → Teton Meadow Guides; current assignments may change during reviews. Choose the organization in the account/workspace menu. Personal account security remains separate.

Navigation from sign-in

  1. 01Open the fictional Organization owner account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02From the owner’s named organization Home select Team & ownership. The feature starts at Transfer ownership, Intended owner’s registered email and Your access after acceptance.

Feature checks start here

Transfer organization ownership

Connected in dev; full acceptance remains In progress. The intended recipient accepted ownership with the former owner removed. The former owner lost the workspace/direct private page but retained paid access, professional profile and saved story. Other transfer dispositions and stale/concurrent cases remain open; restart preserves authority.

  1. 03Under Transfer ownership enter Intended owner’s registered email, explicitly choose Remove my organization access or Keep me as a manager, then Propose ownership transfer.
  2. 04The intended verified recipient uses their own account/workspace menu → Invitations & requests to accept. Confirm exactly one current owner and the selected former-owner disposition.
  3. 05Use a dedicated disposable organization for transfer, cancellation, expiry and stale/concurrent checks. Personal profile, saved work and membership remain separate. The walkthrough must not transfer an existing stakeholder organization as setup.

Backend work for this feature

Backend development authorized · Dev only

What needs to be supported

  • Persist an owner-initiated transfer proposal with org, expected current owner/revision, verified intended recipient, pending acceptance/expiry and explicit outgoing-access choice. Apply accepted ownership change atomically under a one-owner invariant.
  • Use one trusted account ID; keep email verification, professional labels, reader entitlement, organization-scoped access and internal HOL staff assignments independent.
  • Validate actor, organization/person IDs, current access and expected revision at the trusted boundary. Remembered workspace, URL, fixture choice and client flags never grant permissions.
  • Persist only the records needed for this outcome, including owner-scoped drafts and decision/assignment/consent audit where applicable. Keep private evidence and contacts out of public projections.
  • Enforce the selected requirements above in database/API policies, with idempotent transitions, concurrent-update handling and denied cross-account writes.
  • Use isolated local synthetic data only; no hosted migration, public service connection, real credentials/recipients, live payment or deployment.
  • Use organization-scoped owner/manager records rather than the internal staff-assignment table. Require verified email for organization creation, claims, management and invite acceptance.
  • Enforce one current owner and atomic accepted transfer; replayed or competing transfers cannot leave zero owners or multiple owners.

How to verify in dev

  1. Race two transfers and acceptance against cancellation or changed ownership; verify exactly one current owner, no stale recipient grant and explicit former-owner manager/removed state.
  2. Test owner, manager, unrelated account, unverified account and permitted HOL staff where relevant; deny self-grants and cross-organization access.
  3. Exercise success, interrupted/repeated requests, expiry/revocation and stale/concurrent updates; verify stable identity, correct public visibility and preserved unrelated account data.

Before this can work

  • Begin in a named organization workspace as its current owner. The local Organization owner choice uses Maya Hart → Teton Meadow Guides; current assignments may change during reviews. Choose the organization in the account/workspace menu. Personal account security remains separate.
  • Use a fictional organization owner account and begin at its Home with its actual permitted context.
  • Use actual local provider sessions and persisted state; record connected UI and direct permission checks separately.

Connected stories