Client Approval and the Post-Approval Flow

When a delivery link is opened by the client, they land on the delivery page (/delivery/[token]), which is a standalone public-facing view that does not require a Vremly account to browse media. The page has a hero header with the property cover image, address, and a Download button. Below the header, the main content area begins with the Approval section — the first thing the client sees — followed by the media gallery, marketing assets, and optionally an invoice and capture (floor plan / virtual tour) section.

The Approval section has two states. If the client is not signed in, it shows a 'Sign in to approve this delivery or request changes' prompt with a Sign In button that redirects to /login?redirect=/delivery/[token]. Once signed in as the customer on record, the approval card shows two action buttons: 'Approve Delivery' (a filled primary button) and 'Request Changes' (an outline button). Approving calls POST /delivery/[token]/approve and shows an immediate success toast. Requesting changes opens a dialog with a textarea — the client must write feedback before submitting, which calls POST /delivery/[token]/request-changes.

After the client clicks Approve Delivery, the system launches a sequential post-approval flow: first a star-rating dialog (ProjectRatingDialog) where the client can rate the team with 1–5 stars; then, if the rating meets or exceeds the organization's configured threshold (default 4 stars), a review prompt dialog (DeliveryReviewPrompt) showing links to the organization's configured review platforms (Google, Facebook, etc.); and finally, if an active survey is configured for the organization, a survey dialog. Each step can be skipped. Completing or skipping all steps marks the post-approval flow as done and the approval card updates to a green 'Delivery Approved' state with the approval date.

From the provider side, the approved state is reflected back in the job detail. On the iOS iOS app, the Deliverables tab of OrderDetailView shows a CUSTOMER REVIEW card when the job has been approved: it displays a checkmark seal icon labeled 'Approved', the name of the person who approved, the date, any star rating, and any written feedback. This gives the team visibility into client satisfaction without leaving the mobile app.

If the client clicks Request Changes instead, they submit written feedback and the delivery page updates to a 'Changes have been requested' state. On the provider side, the job's clientApprovalStatus reflects CHANGES_REQUESTED — you can see this in the delivery page preview. The client can return to the delivery link at any time after changes are made and approve at that point; the flow resumes where they left off. There is no limit on the number of change request rounds.