Reviews, files, and versions

How to review internally before sharing with a client

Work with your team without giving clients, guests, or automations access too early.

Reviewed on July 15, 2026

See it in Aproova

Under Advanced settings › Review settings, select “Create as an internal review”. If it is disabled, check the workspace plan.
Open the v2 or v1 selector. On an eligible plan, select “Internal” beside the version; after the change, the action becomes “Release”.

Before you start

  • A Fluxo, Operação, or Custom plan.
  • An Owner, Administrator, or Member role to create the review.
  • To release a version: be an Owner, Administrator, the review creator, or have permission to upload versions in the project.

Step by step

  1. 1Use an internal review when your team still needs to check creative, copy, brand, legal, or production details before involving the client.
  2. 2Open “New review”, upload the file, give it a clear name, and choose the project.
  3. 3Open “Advanced settings”. Under “Review settings”, select “Create as an internal review”.
  4. 4Add the team members who will do the first check. Clients and guests may stay in later stages: they will only get access after release.
  5. 5Review the stages, rules, deadlines, and notifications. A stage named “Internal review” organizes the workflow, but only internal visibility blocks external access.
  6. 6Select “Send for internal review”. Only internal members are notified; public links, guests, external emails, and webhooks remain on hold.
  7. 7Comment, place markers, and submit decisions as usual. If changes are needed, upload another version and select “Internal team only” before saving it.
  8. 8When the work is ready for the client, open version history and select “Release”. The version becomes available to external reviewers and pending notifications are sent.
  9. 9Open the client link or confirm access with an external reviewer before closing the internal stage.

What should happen

Your team works on a private version, and the client receives access, email, and automation events only after an authorized person releases it.

If something doesn't work

  • The option is missing or disabled: confirm that the workspace is on a Fluxo, Operação, or Custom plan.
  • The client cannot open the version: this is expected while it is marked as internal.
  • Naming a stage “Internal review” does not block the client on its own. Also select internal visibility for the version.
  • The “Release” button is missing: confirm that you manage versions for this review or have upload permission in the project.
  • After release, external access, pending emails, and the new-version webhook become active. Check participants and integrations first.