Choose who issued records

A source is the system or account that issued incoming IDs. It can deliver records through integrations, APIs, uploads and email. A connection describes how data arrives; it does not determine what the records mean.

Choose a source

Connections, attributed email, API clients and uploads from a source page carry their source. Otherwise review the suggested issuer or choose one. The suggestion can come from retained evidence or your previous choice; a familiar layout never assigns it. Your own records and a new name open the ordinary source editor. Once chosen, the source stays on that arrival and its reprocessing.

You may leave a one-off import Unassigned. The shared layout still supplies field meanings and duplicate checks still run, but sender order numbers and references are not remembered or used to link. It cannot import automatically.

IDs are scoped to their source and logical record type. Record 1001 from Alder Supply and 1001 from Cedar Supply are distinct until explicitly linked to the same business record. Similar names never merge sources or establish identity.

Changing a draft’s source clears dependent choices and needs a fresh review. Once the arrival has approved records or confirmed completeness, use a new arrival for a different source. The original evidence remains retained.

Manage sources

Open Configure → Sources for every file feed, connected account, email sender and API source. Search or filter by kind, Needs attention and active or archived status. Rows show their record types, last arrival, recent activity and future-arrival policy.

Each source has four tabs:

• Activity shows each arrival’s sender, record types, outcome and records created, updated, unchanged, set aside or failed. Error counts cover the entire history; View affected arrivals shows every arrival with that problem. Open an arrival to inspect its original and resulting records. Retry repeats eligible failed work. Process again starts a new version from the saved original for review; reading a document again asks for record types and may use model credits. Upload data uses this source.
• Mappings shows its remembered layouts, field choices, value maps and versions. Overrides are marked. Change an override or reset a field to the shared layout. Editing creates a new version; earlier versions and decisions remain available.
• Records shows how its IDs and names link to your records. Link and unlink choices use the same matching review as Inbox.
• Settings holds its name, connection, Tags/Project for all its imports, processing policy and archive action.

The layouts view shows shared meanings and the sources using them. A change for everyone previews the sources it affects. Changes for one source leave the others alone; changes for just one import are not remembered.

Approving a source’s effective choices defaults to automatic after validation. Choose Review each time to require confirmation. Replacement versions keep that policy. Retiring choices or archiving preserves records, links and history. Merge sources previews the mappings, links and history before you approve combining duplicate sources.

Automatic processing requires an approved policy and trusted attribution. An unattributed email does not gain a source from similar columns. Nested email parts retain the envelope’s explicitly assigned source. Provider connection setup may establish verified attribution for its account.

Creating a source does not create a customer or vendor in Contacts.