Difora › Guides

Give client changes a clear review step.

An agency can capture its client site in CI, share the baseline and diff with the right team, and decide what to accept before delivery. Start with one real project and an agreed review responsibility.

Set up the first client project Start free

Choose the access boundary first

Difora membership is organization-wide. Projects are not separate client permission boundaries. If clients must not see each other’s projects, use separate organizations and invite only the people who should have access to each one. An organization owner manages members and accepts its Agreements.

The Free allowance is one project and 5,000 submitted snapshots per month for an organization, including unchanged images. Choose a suitable paid plan for a larger shared team or workload; there is no dedicated agency plan or white-label portal promised here. See current plans.

Agree on a small delivery workflow

  1. Choose the pages. Capture important page states with representative test data and stable desktop/mobile names.
  2. Establish the baseline. Review the first complete build with the responsible team member and consciously approve it.
  3. Review a change. The next CI run links to the exact build. Compare baseline, current and diff; discuss questions on the snapshot.
  4. Resolve and repeat. Approve intended changes or fix unexpected ones. An assigned reviewer is advisory; approval restrictions are configured separately by an owner.

Keep capture in the client project

Use a separate project upload token per project and store it in that repository’s CI secrets as DIFORA_TOKEN. After a successful complete capture, the same command works across CI providers: 

npx difora upload ./screenshots

Choose the Playwright capture workflow for site journeys or Storybook for component states. Keep each project’s complete snapshot set together; a missing name may be treated as a removal.

Make handover explicit

Before closing an engagement, agree who owns the organization, who maintains CI and who reviews future changes. Review memberships, rotate shared credentials using project token controls, and confirm that the client can complete a capture and review. Do not assume a reviewer assignment grants or removes access.

Review data-processing boundaries with the client. Optional public PR previews are off by default; enabling them changes the sharing boundary. Difora supplies evidence for your team’s decision, not an automatic client sign-off.

Start free Set up the first client project

Difora is an independent service. Product names identify the tools discussed; no affiliation or endorsement is implied.