Your account
HOL-D071Story implementation: Planned

Apply for professional verification and see the result

people · Proposed launch phase 2

Start from Home

Review as Creator · Full workflow planned

User story

As a creator, I want to submit my professional evidence and track the decision so my approved identity and expertise are represented accurately.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • This story concerns separately verified professional evidence or credential claims only. It is not a prerequisite for ordinary Guide/Creator/Athlete setup, profile publication or entry to the free Professional workspace.
  • Affiliation agreement belongs to D098, not professional verification. Keep optional evidence decisions separate from reader access and organization ownership.
  • Create an optional evidence application for a separately verified professional claim on the same account; ordinary role labels remain self-service.
  • Provide identity and credited-work evidence for Creator review; the accepted evidence standard still needs HOL confirmation.
  • Save a private draft, submit for review and show pending, changes requested, approved, declined and withdrawn states with an understandable reason and next step.
  • Allow an applicant to correct and resubmit requested information without overwriting the earlier decision; show only approved fields publicly.
  • Only the assigned verification reviewer can decide through D029. Applicants cannot self-verify; approval neither activates paid membership nor grants editorial or staff authority.
  • Organization affiliation is independent of this credential application: use D098 two-sided consent against the canonical D083/D084 organization ID, with no automatic sponsor relationship.

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 Professional Home using Liam McGee (Creator) or your own verified account with that professional label. Use the account/workspace menu → Professional. Professional labels do not include paid reader access.

Navigation from sign-in

  1. 01Open the fictional Creator account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02Begin on Professional Home. Its current tools are Edit professional profile, View public profile and Affiliations.
  3. 03The earlier role-specific collection/composer/verification tile named in this story is not available from this connected Home. Stop here for that operator workflow; public examples can be explored through View public profile and Events/Community/Explore.

Feature checks start here

Apply for professional verification and see the result · Full workflow planned

The connected Professional workspace currently provides profile editing, public profile and affiliations only. The story’s specialist collection, sharing, verification or answer workflow is not reachable from this Home. Earlier isolated previews are not a complete current walkthrough. Backend implementation is on hold for this specialist workflow.

  1. 04Inspect the current Professional Home and public identity without assuming that a professional label grants paid reader access.
  2. 05Current review stops before the missing role-specific tool. Planned acceptance: Inspect the sample verification record; distinguish this preview from a submitted application. Once built, create a fictional application using the evidence fields appropriate to this role, save a draft, then submit it. Review the pending state and a requested change; revise and resubmit the same application. Review approved and declined examples with their next steps; confirm that only approved public identity fields change and no paid entitlement is granted. Once built, request a Guide/tour-company or Athlete/brand affiliation change; verify pending evidence stays private and only the separately approved relationship becomes a reciprocal public link.

Backend work for this feature

Requirements only · Backend implementation on hold

What needs to be supported

  • Store the applicant, requested professional attribute, structured evidence references, version, status and submission time; evidence stays private to its owner and assigned reviewer.
  • Accept evidence types and sizes from an approved allowlist. Keep uploads private, validate files and support an agreed retention/removal policy; do not collect real credentials or evidence in the present demo.
  • Enforce owner draft/submission rights and reviewer-only decisions on the server/database; reject cross-account reads, forged role claims and self-approval.
  • Apply D029 decisions to professional attributes through a trusted transition, retaining decision actor/time/reason and prior versions; paid entitlement remains managed separately by D069.
  • Handle duplicate submission, interrupted upload, requested changes, concurrent reviewer decisions and denied/revoked professional standing without duplicate grants.
  • Keep private verified-claim evidence separate from D098 mutual affiliations; neither a verified claim nor its revocation changes organization ownership or reader entitlement.

How to verify when implementation is approved

  1. Test Creator, Guide and Athlete application fields using separate synthetic accounts and an assigned reviewer.
  2. Verify an applicant cannot see another applicant’s evidence or approve their own request; a reviewer outside the assigned scope is denied.
  3. Submit twice, request changes, resubmit, approve or decline, then reload; verify one versioned result, an audit trail and unchanged paid access.
  4. Decline or revoke a proposed organization affiliation; verify public person/organization links update without changing an unrelated approved credential or paid entitlement.

Before this can work

  • Begin on Professional Home using Liam McGee (Creator) or your own verified account with that professional label. Use the account/workspace menu → Professional. Professional labels do not include paid reader access.
  • HOL must select acceptable professional evidence, the assigned reviewer, retention and any expiration/reverification policy. These are build prerequisites, not newly granted permissions.
  • Use fictional role-preview records. Frontend prototypes may simulate the workflow; no backend implementation or real service operation is authorized.

Connected stories