Your account
HOL-D029Story implementation: In progress

Verify experts and manage their access

operations · Proposed launch phase 2

Start from Home

Review as Platform administrator

User story

As a platform administrator, I want to review optional professional credential claims so separately verified expertise is represented accurately.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Internal HOL staff invitation/assignment lifecycle is D103, not part of this optional professional-evidence decision.
  • Professional evidence review grants only its explicitly verified claim. Ordinary Guide/Creator/Athlete registration and basic profile publication have no HOL approval gate.
  • Normal organization ownership claims belong to Commercial through D097; disputed/exceptional escalations belong to Platform administrator. Organization owner/manager permissions remain separate from internal HOL assignments.
  • An authorized Platform administrator reviews professional evidence and approves or declines with a reason.
  • Keep professional attributes, assigned operational roles and paid subscription entitlement as separate records.
  • Record who decided what and when in a generated audit trail; sample decisions do not change real account access.
  • Professional applicants cannot self-verify. A guide/athlete evidence submission and result workflow still needs its own acceptance.
  • Receive an application/revision from D071, request missing information or decide the exact submitted evidence version, and return the result to the same applicant.
  • Revoke/expire professional standing only under the agreed policy, retaining history and approved/public field boundaries; membership remains a separate entitlement.
  • Professional verification applies to a person’s reviewed attribute. A public organization listing, approved affiliation or commercial partner record does not automatically verify a person or business, grant paid access or create an organization login role.

What to check in the demo

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

Review as

Platform administrator

Start here: Home

Choose the Robin Park dummy account and open its assigned Platform administrator Home without a password or authenticator prompt. This dev-only Home review does not verify MFA or unlock protected staff actions. Use your own provisioned staff account and authenticator when reviewing those actions.

Navigation from sign-in

  1. 01Open the fictional Platform administrator account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02On Platform administrator Home, select Professional verification to review sample evidence.

Feature checks start here

Professional verification

A partial role preview is available. Platform administrator → Professional verification shows sample evidence with approval and reasoned decline; access and decision-history examples are separate. Layered assignment, entitlement changes and a generated audit trail remain incomplete. Review the current sample controls, then treat remaining checks as planned acceptance. Public people and organization pages are available; this operator handoff remains incomplete. Backend implementation is on hold.

  1. 03Review the sample evidence for Maya Hart and select Approve sample; check the recorded sample status.
  2. 04Enter a reason for the Liam McGee sample and select Decline with reason; check the resulting sample status.
  3. 05Return to Platform administrator Home and inspect Roles + membership access and Decision history as separate examples.
  4. 06Remaining acceptance: connect role assignment, professional attributes, subscription entitlement and a generated decision audit trail. No real account access is changed.
  5. 07Once connected, request changes, approve/decline and inspect the same D071 applicant outcome; verify a stale or self-approved request cannot change standing.
  6. 08Compare a published organization, an approved person affiliation and an approved professional credential; confirm the first two cannot substitute for the verification reviewer’s credential decision.

Backend work for this feature

Requirements only · Backend implementation on hold

What needs to be supported

  • Use D071 application/evidence records and an explicit reviewer assignment; restrict private evidence to its applicant and permitted reviewer.
  • Validate the submitted revision and reviewer authority server-side; decide/request changes with actor/time/reason and expose the appropriate applicant-visible result.
  • Apply approved professional attribute/expiry/revocation updates as trusted transitions with audit and public-index refresh; do not couple them to paid access or unrelated staff authority.
  • Use expected-version/idempotency checks for duplicate or competing decisions; retain private evidence under the approved storage/retention policy without secrets in public logs.
  • Keep person professional-verification decisions separate from organization-publication and affiliation decisions; do not derive role or entitlement grants from public organization relations.

How to verify when implementation is approved

  1. Verify applicant/assigned-reviewer/unassigned-reviewer access, denied self-approval and separate membership state.
  2. Request changes, resubmit and approve/decline an exact revision; race competing decisions and verify one consistent applicant/public result.
  3. Test authorized revocation/expiry and index refresh with synthetic records; preserve audit and unrelated entitlement.
  4. Attempt to use an organization publication or affiliation as proof of professional verification; verify no automatic role, badge or membership grant.

Before this can work

  • Choose the Robin Park dummy account and open its assigned Platform administrator Home without a password or authenticator prompt. This dev-only Home review does not verify MFA or unlock protected staff actions. Use your own provisioned staff account and authenticator when reviewing those actions.

No prerequisite story has been confirmed. The setup above describes the content or decisions needed.

Connected stories