Skip to content

[Sites] Share private Sites previews for release approval #2102

Open

Description

@sidneyswift

Parent epic: #2093

Priority

P2 — Later expansion or nonblocking follow-up.

User story

As a manager, I want an artist or teammate to review the exact draft before it goes live.

User journey

Generate → create a private review link → artist opens it on their phone → leaves feedback or approves → manager revises → obtains approval for the new revision → publishes.

Acceptance criteria

  • Create revocable, expiring review links that cannot enumerate drafts or access fan data, account data, or publishing controls.
  • Bind feedback and approval to a specific revision and identify the reviewer; distinguish identified approval from anonymous feedback.
  • Show unresolved feedback and approval status in the editor; a revision change invalidates the previous approval for the new draft.
  • Review visits are excluded from campaign results. Public URLs still expose only the published snapshot.
  • Keep publishing permission with authorized workspace members and expose review management through API/MCP.

Owning code

API review-token/feedback operations; database review records; chat preview and editor UI; docs.

Use the epic's API-first/MCP, workspace authorization, database migration, docs, and explicit-publishing requirements.

Blocking dependencies

These are completion prerequisites, mirrored in GitHub’s blocked-by links. Design and contract work may start earlier. Other coordination references are not blockers.

Validation

Check expired/revoked links, token leakage prevention, wrong revision, anonymous review, unauthorized publish, and mobile review behavior.

Platform foundation alignment

This remains part of Sites epic #2093. Recoup Sites and external apps must share primitives, authorization, and billing. Coordinate with:

The Blocking dependencies section is authoritative. Campaign release follows the external integration proof gate; independent design/test work can proceed earlier.

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority:P2Later expansion or nonblocking follow-up

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions