How to use a Righthand with Cloudinary

Quick answer

Use Righthand to prepare a Cloudinary asset-delivery checklist for an approved website change. Match originals, transformations, and intended placements before rollout.

Start with a reviewable deliverable, keeping Cloudinary as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

Evidence and access

Cloudinary documents image transformations and asset-delivery options. See the official Cloudinary reference. Provider capabilities and Righthand's available tools are separate checks.

Request the approved asset inventory with public IDs, versions, transformation references, source files, and intended placements. Verify the required tools and owner-approved scope through Righthand integrations; use the supplied packet when a native read is unavailable.

Define the objects and authority

Include these fields in the working input: public ID, asset version, resource type, transformation, format, dimensions, delivery URL. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

A transformed image can exist without being used by the site. Uploads, overwrites, deletion, and public delivery changes need owner approval.

Illustrative first-run brief

Use the owner-provided Cloudinary snapshot or approved read-only view. Review the supplied ten-asset manifest against required placements. Flag wrong dimensions, uncertain versions, and unmatched delivery links without changing assets. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the asset manager to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

Expected result and verification

A mobile image can use the correct original but the wrong crop. The checklist records the placement-specific review.

Open a delivery URL and compare its version, dimensions, and visible crop with the approved requirement. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.

Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

Common failure and recovery

An unversioned or cached URL can show older content. Confirm asset version and intended delivery behavior before requesting replacement.

If an asset URL serves an unexpected version or transformation, retain the actual reference and ask the media owner which output is authoritative.

FAQ

What should the reviewer verify first?

Verify asset identity, version, transformation, dimensions, and placement. A transformed URL can produce a different artifact from the original file.

How should a repeat run be scoped?

Keep public ID and version with each accepted output. Recheck changed transformation parameters or replacements; a familiar filename does not preserve approval.

For connection and permission details, use Righthand Docs. Review Pricing alongside any separate provider charges before expanding the workflow.