# Storage, snapshots and connected destinations

Understand where records and files go, and verify delivery.

Audience: App owners and data managers

Reviewed: 2026-11-05

Canonical path: /docs/storage-and-sync

## Different resources

Records, attachments, exported spreadsheets and connected Lists are different resources. A record save does not prove remote delivery completed. App access does not automatically grant cloud-file access, and file access does not grant app permissions.

## Configure and verify

1. Open Overview or Overview & storage for the app type.
2. Check the connected identity and storage location.
3. Where offered, choose a snapshot destination or connect the intended List and map columns.
4. Use an authorised test record or snapshot.
5. Read the result and open the destination to confirm the expected file or List.

## Snapshot versus maintained copy

A snapshot is a point-in-time copy. A maintained List destination can have different push/update behaviour. Read its configuration before pushing, especially where existing items can be updated or removed.

Do not assume connections are bidirectional, editing a cloud copy updates the app, or a spreadsheet is a complete restorable backup.

## Public forms are different

Form List delivery creates one item per new accepted entry. It does not backfill old responses, update delivered items from edited responses, or attach files directly to List items. Use the form guide for that workflow.

## Connection problems

Check the connection banner, permissions and error. Reconnect the intended account when prompted, then verify before retrying. Ownership changes and revoked provider access can affect delivery. Do not publish tokens or secret-bearing file links in support requests. Calendar connections are not offered in this release.

## Related guides

- [Create and publish a public form](/docs/forms)
- [Records, imports and exports](/docs/records-and-imports)
- [Troubleshoot a problem](/docs/troubleshooting)