Your account
HOL-D075Story implementation: Planned

Review submitted work and expert answers

content · Proposed launch phase 2

Start from Home

Review as Editor · Full workflow planned

User story

As an editor, I want to review assigned contributions and expert answers with clear decisions so only approved material reaches readers.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Shared submissions can originate from any verified account role; professional status and paid reader membership are not general submission prerequisites.
  • Paid Guide pass-through and its approval bypass remain undefined/follow-up. Preserve the separate editorial approval/publication process until selected otherwise.
  • Provide an assigned queue for professional/member submissions and Guide answers, identifying type, author, revision and intended audience.
  • Review content, attribution/consent, disclosure, relevant associations and scope; inspect only the information needed for the decision.
  • Request changes or decline with a reason; approve a specific revision and notify the contributor through a visible in-app outcome.
  • Approval of a contribution hands it to D074 for canonical publication; approval of a Guide answer exposes the approved revision in D033 through D073. Do not treat every approval as immediate publication.
  • Keep assigned-group moderation D026 distinct from editorial review. Changed, withdrawn, stale or already-reviewed submissions need clear handling.
  • Do not automatically publish local conversation comments or professional evidence; those retain their separate moderation/verification policies.

What to check in the demo

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

Review as

Editor

Start here: Home

Choose the Nora Vale dummy account and open its assigned Editor 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 Editor 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 Editor Home, select Contributions + answers.

Feature checks start here

Review submitted work and expert answers · Full workflow planned

Planned full workflow. Existing workspace samples, where present, demonstrate only isolated controls. Backend implementation is on hold; no completed end-to-end outcome or stakeholder approval is claimed.

  1. 03Inspect the sample queue and available Approve/Request changes controls; a local sample decision is not a connected contributor outcome.
  2. 04Once built, open a pending contribution and an assigned expert answer, checking their exact author/revision and intended audience.
  3. 05Request a change, inspect the author’s revision, then approve or decline with a reason.
  4. 06Confirm a submission reaches the correct publication handoff and an answer reaches the matching member session only after its required approval.
  5. 07Attempt to act on a withdrawn or changed revision and inspect the conflict; verify another unrelated Editor cannot act outside assigned scope.

Backend work for this feature

Requirements only · Backend implementation on hold

What needs to be supported

  • Model review assignments, item type/reference, submitted revision, decision, reviewer, time/reason and contributor-visible outcome; keep private review notes separate from public content.
  • Enforce assigned reviewer access and a valid submitted state server-side; define conflict-of-interest/self-review policy before a connected review grant.
  • Require an exact revision/version match and make repeated decisions idempotent. A new author revision or withdrawal invalidates a stale approval request.
  • Commit the decision and intended publication/answer handoff without duplicate outcomes; publish only through the approved destination workflow and retain audit history.
  • Expose an understandable author outcome through authenticated reads; real notification delivery, broad comment auto-publication and unreviewed private data access remain excluded.

How to verify when implementation is approved

  1. Test assigned Editor, unassigned Editor and contributor access to queue, private notes and decisions.
  2. Request changes and resubmit; race author revision/withdrawal with approval and verify stale decisions are denied.
  3. Approve a contribution and an answer separately; verify the correct D074 or D073/D033 handoff exactly once and persistent contributor-visible state.

Before this can work

  • Choose the Nora Vale dummy account and open its assigned Editor 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.
  • Confirm the named editorial reviewer, assignment boundaries, self-review rules and which material requires a second publication step. No live notification or publication service is enabled.
  • Use fictional role-preview records. Frontend prototypes may simulate the workflow; no backend implementation or real service operation is authorized.

Connected stories