Features

FelagarDeliverable approvals

Share a branded review link, verify the guest with email OTP, and lock approvals to the right version — whatever the file type.

In practice

Deliverable approvals

Share one branded link. The client proves email with a one-time code, reviews the version, and approves or requests changes — no portal account required. Works for PDFs, videos, images, documents, and press materials, not just visual designs. Import frames from Figma into the same review loop, with decisions and history stuck to the deliverable.

Approvals stick to the version, not a screenshot buried in email. Guests prove who they are with a one-time code, decide on that round, and you keep a history you can defend when someone asks which file was signed off — whether it's a mockup, a video cut, or a press release.

Highlights

What stands out when this becomes part of how you run client work.

How it works

Deliverable review stays on the file, whatever it is. Guests do not need a portal account; your studio keeps versions, Figma imports, and decisions in one place.

  1. 01

    Upload a deliverable version — PDF, video, image, document — or import frames from Figma into the review flow for the project.

  2. 02

    Send a guest review link. The client proves email with a one-time code, then opens the branded review.

  3. 03

    They approve or request changes on that version. History stays on the deliverable so you never guess which round was signed off.

  4. 04

    Revoke a link anytime. Approved work can land in Files so delivery and deliverables stay connected.

We run the platform. You run the studio.

Create an account, invite your team and clients, and you’re live, with no DevOps side quest. Updates, uptime, and the portal stay on us so you can stay on the work that pays.

Beta

Request beta access

We will only use this email for beta updates and your invite.