REFLO logoREFLO
…
BlogGuide
Guide

REFLO share with client guide — get a comp reviewed with one link

REFLO Team2026. 7. 22. 오후 1:1813 min read

From creating a share link through the screen the client sees, and how approve or request-changes comes back into the app — how to get a comp reviewed without attaching a file.

Review day usually looks like this. Export the PSD to JPG, attach it to email, send a still on chat too, and a few days later get “which one was final?” You need a review, but the process becomes send-file and ask-again on a loop.

REFLO Share with client shortens that flow to one link. Pick the version you want to show on the timeline, make a web link, and the client opens it in a browser and replies with Approve or Changes requested. That reply comes back into the REFLO app as a badge next to that same version. As the app says — “Share a version with a web link and get approval.”

This guide covers creating a share link, the screen the client sees, and how you check the reply.

What is Share with client?

  • What you send — a web link that holds a preview of a specific version recorded on the timeline. It is not a file attachment.
  • What the recipient does — opens the link in a browser, reviews the comp, and approves or leaves changes requested. No REFLO install, and no account.
  • What comes back to you — the client’s reply shows next to that version in the app as a Client approved / Changes requested badge.

You don’t have to explain “which round of the comp” in words. The link itself points at exactly that moment’s version.

Before you start — account and cloud

For the client to see the comp in a browser, that version has to be reachable on the web, so share links need a REFLO account and a cloud connection.

If you open share before connecting, you’ll see this hint.

> “Account connection is required for web share — we upload the selected version and create a secure link so the client can view the comp in a browser. Connect cloud in Settings, then continue sharing.”

The hint’s Connect in Settings button goes to the Settings screen. For how to connect an account, see the Account tab in the Settings guide.

  1. On the History screen (⌘2), select the file and version you want to share.
  2. In the right inspector, click Share with client. You can also right-click a version on the timeline — the contextual menu gathers restore, share, notes, and similar actions.
  3. In the share window, enter three things.
  • Title (required) — becomes the title on the client screen. Example: “Round 3 review.”
  • Message (optional) — “A note to send the client.” Something like “Please focus on the banner copy this time” is useful.
  • Expires — how long the link stays valid. Choose 7 days / 14 days / 30 days (default 14 days).
  1. Click Create share link.
  2. The done screen shows the link — “Send the link below to your client.” Click Copy link, then paste it into the messenger or email you already use.

What if the version isn’t in the cloud yet?

You don’t need to worry. If you share a version that only lived on this Mac, REFLO handles it.

> “On share, only this version is uploaded, then the client link is created.”

Not the whole history — only the version you’re sharing is uploaded, so cloud capacity impact is kept small.

The screen the client sees

From the recipient’s side, it looks like this.

  • Opening the link shows a Review request screen in the browser. No sign-in, and no install.
  • The title and message you set, plus the link expiry date, are shown together.
  • The comp is shown as a preview image, and they can click to view it larger.

One reassuring point — what the link shares is a preview, not the original working file. The client cannot download the PSD original from the link. Even if a review link leaks, the original stays in your history.

Approve and changes requested

Under the preview, the client picks one of two.

  • Approve — fine to proceed as-is.
  • Changes requested — something needs to change.

They can leave a name (optional) and a comment (optional), then click Send response, and it finishes with “Your response has been sent.” Each link takes a response once — opening a link that already has a response shows “A response has already been recorded.” When you need another review after edits, create a new link from the new version.

Checking the response

When the client responds, you don’t have to be watching the app.

  • Select that version on the History screen, and the inspector’s Client response area shows a Client approved or Changes requested badge. The response is reflected automatically within about one minute.
  • View response shows the message the client left, who responded, and when. A response with no comment shows “No attached message.”

Approval is attached to exactly that version on the timeline, so you won’t have to hunt later for “which version was approved?”

Expiry and safety

  • After the expiry period, the link no longer opens — the client only sees “This link has expired or the sender withdrew it.”
  • For sensitive work such as a pre-release comp, we recommend a short expiry of 7 days.
  • As above, the original file is not shared, and the link is made as a unique address that can’t be guessed.

FAQ

Does the client need a REFLO account too?

No. The recipient only opens the link in a browser. No sign-in, install, or sign-up.

Can the client get the original file too?

No. The share link only shows a preview image. To send the original file, keep using whatever file-delivery method you already use.

Until the expiry you chose when you created it (7 / 14 / 30 days). After that it won’t open, so create a new link and send it again if you still need it.

Can I collect several responses?

Each link takes one response. After you edit, creating a new link from the new version is also cleaner as a flow — which version got which response stays on the record as-is.

I see “This version can’t be shared yet”

“Select a version that has a restorable snapshot.” A version without a snapshot (for example an old version that was already pruned) cannot be shared. Pick another restorable version on the timeline.

I see “Cloud capacity was too low to finish the share upload”

Cloud usage is near the limit. In Settings → Storage tab → Usage, check cloud usage, clean up or raise the limit, then try again.

Right now the flow is one version per share. If you want them compared, make a link per version and send them together.

This guide follows the wording in the app. Button placement may shift slightly between versions — follow the tooltips and on-screen hints. If the share flow needs more, send beta feedback.

Related posts