Your account
HOL-D096Story implementation: In progress

Claim an existing organization page

organizations · Proposed launch phase 2

Start from Home

Review as Registered user

User story

As a registered member, I want to prove my authority to manage an existing organization page so I can gain the correct organization access.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Require verified email before claiming; locate the existing canonical organization and submit an organization-specific request with contact/authority evidence and a reason.
  • Use one claim/status record: draft, submitted, information requested, approved or declined, with understandable reason and next action. Submission grants no management access.
  • Existing available owners should use ordinary owner-managed invitations/transfers. For unclaimed pages or a former owner who is unavailable, HOL Commercial manager handles normal evidence-backed claims.
  • Disputed ownership, contradictory evidence, suspected compromise or exceptional overrides escalate to Platform administrator. Keep evidence/private contact details out of public pages.
  • An approved recovery changes only the organization assignment and explicitly records old access removal/retention. Never take over the former representative’s personal account, membership or other organizations.

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 on the free Member Home. For a local example use Sign in → Try a demo account → Alex Morgan → Open account, then choose Member in the account/workspace menu if a remembered workspace opens. This is a genuine local account; no paid access is supplied.

Navigation from sign-in

  1. 01Open the fictional Registered user 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 verified Member Home use footer Explore → Organizations, open Ridge Stewardship Collective or another organization you do not manage, then select Represent this organization?. The feature starts at Fictional evidence reference and Why you represent this organization.

Feature checks start here

Claim an existing organization page

Connected in dev; full acceptance remains In progress. An applicant submitted fictional evidence, reloaded its private status and withdrew the claim without gaining organization access. Reviewer MFA, information-response and disputed/stale browser cases remain open.

  1. 03Use only fictional evidence: fill Fictional evidence reference and Why you represent this organization, then Submit ownership claim.
  2. 04Inspect the returned private claim status and reload the same claim page. If appropriate use its Withdraw claim control; a submitted claim never grants early access.
  3. 05Information requests and approval/decline/escalation outcomes require a separate assigned HOL reviewer with MFA. Do not expect applicant-side buttons to approve or escalate their own claim.

Backend work for this feature

Backend development authorized · Dev only

What needs to be supported

  • Persist a claim on the canonical org with applicant, reason, private synthetic evidence/contact references, version, state, information requests and decision linkage. Claim creation/submission must not mutate org access.
  • 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.

How to verify in dev

  1. Submit for an unclaimed page and an unavailable-former-owner example, request more info, decline/approve through assigned staff and compare applicant access before versus after the recorded decision.
  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 on the free Member Home. For a local example use Sign in → Try a demo account → Alex Morgan → Open account, then choose Member in the account/workspace menu if a remembered workspace opens. This is a genuine local account; no paid access is supplied.
  • Use a fictional registered member 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