Storage and connections
Where archived copies are written, where they are read from, and how a sync mode is decided for each pairing.
Three of the five onboarding decisions describe the same pipeline from two ends. A connection is where data is read from. A storage target is where the archived copy is written. A sync mode is the rule for one pairing of the two.
Storage targets
A storage target is where archived copies are physically written.
There is a hosted default, and you can connect S3-compatible targets of your own. Each target is listed with the kind of storage it is, the region it is pinned to, and how it stores what it receives, for example every version kept, a folder per file.
| Marker | Meaning |
|---|---|
| Default | New archived copies go here unless a sync mode says otherwise. |
| Connected | The target is reachable and accepting writes. |
Each S3-compatible target carries its own region. An organization can hold targets in different regions at the same time, which is how data can be kept where it has to stay.
ERP connections
A connection is one authorized link to one ERP account. An organization can hold several, and each reports when it was last scanned.
The important part is that connections do not all keep history the same way:
| Marker | What it means for history |
|---|---|
| MeshERP keeps versions | Version history is kept on the MeshERP side for this connection. |
| Provider keeps versions | The source provider holds the versions, not the archive. |
| No history kept | No version history is retained for this connection. |
A connection marked No history kept still archives, but there will be no earlier versions to read back for it. Two connections to the same ERP can differ, so check the marker rather than assuming it applies to the whole account.
What any connection can reach is bounded by the ERP identity you authorized. A connector reads the records, files, configuration and source history that identity is allowed to read, and nothing beyond it.
Sync modes
A sync mode is decided per pair: one storage target with one ERP connection. That is why this step carries more decisions than the others. A setup with three targets and three connections has more pairs to answer than a setup with one of each.
Every pair needs an answer. Until all of them are decided, onboarding reports that sync modes are unfinished, even when every other step is complete and the archive is already running.
An undecided pair is a gap in coverage, not a stopped archive. The pairs you answered keep working. Treat the unfinished warning as a coverage checklist rather than an outage.
Changing them later
All three are revisited by reopening onboarding. Finishing the wizard again re-saves the choices, it does not re-archive anything that was already captured.