Your account
HOL-D030Story implementation: Planned

Send in photos or video for review

media · Proposed launch phase 2

Start from Home

Review as Visitor · Full workflow planned

User story

As a visitor, I want to submit photo/video for review so I can contribute with clear attribution and publication expectations.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Offer the shared photo/video submission path to all account roles; a Visitor may discover the route and must register/sign in and verify email before submitting. No paid-reader or professional-label prerequisite.
  • Keep one person-owned attributed submission with bounded draft content/media, credits and consent. Staff and organization management grant no automatic publication authority.
  • Save a draft, submit, view requested changes or decline, revise/resubmit or withdraw under the editorial workflow. Keep drafts private and publish only the separately approved canonical revision.
  • Paid Guide content pass-through is a future idea with its bypass rules undefined. Do not implement automatic publication or a payment-based approval bypass.
  • Paid member-group participation, expert answers and other restricted features retain their separate rules; shared editorial submission does not unlock them.

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 Visitor Home while signed out. If an account is active, use the account/workspace menu → Sign out. Public browsing does not require an account.

Navigation from public entry

  1. 01Begin on Visitor Home, without signing in.
  2. 02From this role’s Home use footer The magazine → Submissions. The current page is submission guidance with Contact editorial; it is not the planned shared draft/submission workspace.

Feature checks start here

Send in photos or video for review · Full workflow planned

Planned shared submission workflow; current compose samples are partial. Backend implementation is on hold; content implementation is outside the first account/workspace build.

  1. 03Review Before you pitch and Contact editorial as the current UI endpoint. A contact inquiry is not a saved original-work submission.
  2. 04Stop here. Planned acceptance after the shared workflow is built: prepare an attributed photo/video/written draft, save, submit, receive requested changes and inspect the same contributor outcome without requiring paid membership.

Backend work for this feature

Requirements only · Backend implementation on hold

What needs to be supported

  • 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.

How to verify when implementation is approved

  1. Test owner, manager, unrelated account, unverified account and permitted HOL staff where relevant; deny self-grants and cross-organization access.
  2. 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 Visitor Home while signed out. If an account is active, use the account/workspace menu → Sign out. Public browsing does not require an account.
  • Use a fictional visitor account and begin at its Home with its actual permitted context.
  • Keep simulated outcomes separate from real account/backend evidence.

Connected stories