Practical guide

Cloud source file or signed archive? Keep the direction clear

Last materially reviewed 2026-09-21

Quick answerBeing able to select a cloud file does not prove that completed records synchronize back to it.
What to know

Verify the integration direction

Signaturely’s pricing page lists cloud-storage integrations. A listed integration is a starting point for verification, not proof of every direction or synchronization behavior. Distinguish selecting a source file for preparation from storing the final signed document afterward. These are different operations with different records and permissions. Do not replace a working archive process merely because a familiar storage logo appears in the product description.

What to know

Name the authoritative file

Before sending, establish which source version was approved. After completion, establish which output is the retained signed record. The source and final output may belong in different locations and should not be casually overwritten. An ordinary shared document that continues to change is not a reliable substitute for identifying what was actually issued. Keep the relationship understandable without assuming the storage service provides a signing-specific history.

What to know

Check access requirements and failure behavior

If a connection is used, verify who can access the source and destination and what happens when a transfer fails. Do not grant broader access as an improvised troubleshooting step. A missing final file may mean the process never included a return transfer, not that synchronization is temporarily slow. Inspect the documented supported operation and actual observed result before retrying or adding another automation.

What to know

Keep a modest acceptance record

Use a non-sensitive sample, where authorized, to confirm the exact direction and output location. Record what was observed rather than describing the whole integration as working. If a step is manual, make that responsibility explicit. The audit guide covers the retained evidence, while the manual-versus-API guide explains why a desired automated handoff needs its own supported contract and verification rather than an assumption. Record the exact direction tested, not just the integration name.

Continue when useful

Next: Keep the signed document and its audit trail together

Retain the output and the record that identifies its request; one is not a substitute for the other.

Open Keep the signed document and its audit trail together →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Signaturely product and current plans — Merchant documentation · signaturely.com · Merchant-controlled · checked 2026-09-21
  2. View and download the audit trail — Merchant documentation · help.signaturely.com · Merchant-controlled · checked 2026-09-21