# How to use a Righthand with Dropbox

Prepare a Dropbox delivery index with file identities, paths, revision context, approval evidence, and a checked sharing boundary.

By Righthand Team · 2026-10-09

Source: https://www.righthand.ai/blog/how-to-use-righthand-with-dropbox

## Separate the delivery index from file sharing

Use Righthand with Dropbox to prepare an index of approved files for a delivery handoff. The result should identify the intended assets and missing approval evidence. A folder full of recently modified files does not establish that every file is ready to send to a client.

Dropbox's [getting-started guide](https://www.dropbox.com/developers/reference/getting-started) describes folder listings and metadata. Preserve available file identities and paths. Paths help people navigate, while identity helps reconcile a file that has been renamed or moved within the approved source.

## Define folder and approval scope

Give the account, exact folder, included subfolders, and the approved delivery manifest. For an illustrative design handoff, the manifest might require a logo package, usage guide, and final source file. The owner supplies those requirements and the evidence that marks a version approved.

Check Dropbox's actual tools through [integrations](/integrations). If listings or metadata reads are absent, use an owner-supplied folder inventory or authorize a browser review. If file contents cannot be inspected, the report should stay an inventory rather than claim a complete quality review.

## A complete illustrative request

> At 2 PM America/Los_Angeles on Friday, review the approved client-delivery folder and attached asset manifest. Return a private index with file identity where available, current path, filename, modification or revision information, and matching approval reference. Flag missing assets and ambiguous versions. Do not move, delete, upload, or share files. Send to me for creative-lead review. Reconcile the listed files and subfolder coverage against the manifest and identify inaccessible content.

The example is illustrative. The newest revision can contain unfinished changes. Approval must come from the named source rather than from recency or a filename containing “final.”

## Make the index useful to its reviewer

An example entry might say: “Logo package found in Delivery; two similarly named archives; approval reference identifies only one; creative lead must confirm the intended archive.” Keep both paths and their identities so the reviewer can compare them.

An approved source file and a rendered preview serve different purposes. The index should distinguish them rather than treating a preview as a replacement for the required editable asset. If the export loses revision detail, mark the version check unresolved.

## Reconcile movement and repeat runs

On later reviews, match file identity where available and refresh the path and revision information. A renamed file should not look like a missing asset plus a new duplicate. Finish the supported listing's pagination or state partial coverage.

An unavailable folder can reflect account selection or permission loss. Do not broaden the search into unrelated folders to fill the gap. Sharing a link requires a separate authorized recipient and access setting, then an independent check that the intended file and permission were used.

Set authority through [Righthand connection permissions](https://docs.righthand.ai/guides/add-a-connection). Review [pricing](/pricing) for recurring delivery preparation and keep the creative lead responsible for the final asset selection.