SyncOnAI360

Change History

Know what changed in Salesforce, when, and which way it came in.

A record of every change to every connected org, with changes made through SyncOnAI 360 kept in full and changes made elsewhere caught and flagged.

Track your org freeBook a demo

Deploy receipt

Acme Production

Deployed
Change
Case_Intake_Route: fault path added
Requested
"Add fault handling to the intake Flow"
Checks
5 of 5 passed
Approved by
M. Okafor, admin
Deployed
Today, 14:22 to Acme Production
Previous version recorded

In one paragraph

SyncOnAI 360 Change History records what changed in each connected Salesforce org and when, and whether the change came through SyncOnAI 360 or another route. Changes made through it keep a full before and after with the request, checks and approver; changes made elsewhere are detected on sync and production changes outside the pipeline are flagged by the audit.

Routes told apart: through 360, or elsewhere
2Routes told apart: through 360, or elsewhere
Before and after for every change made through 360
FullBefore and after for every change made through 360
Of Setup Audit Trail read into each audit
30dOf Setup Audit Trail read into each audit
Record per sync, plus one entry per changed component
1Record per sync, plus one entry per changed component

01The problem

Why "who changed that?" is so hard to answer in Salesforce

Salesforce records some changes in the Setup Audit Trail, in terse entries that are hard to search. Deploy tools record their own deploys. Neither tells you the whole story, and neither can say what changed outside the process.

  1. 01

    Fragmented records

    Deploy logs, the Setup Audit Trail and people's memories each hold part of the history.

  2. 02

    Side doors

    A quick fix made directly in production never appears in the release record.

  3. 03

    No before and after

    Knowing that something changed is not the same as knowing what it was before.

  4. 04

    Audits and incidents stall

    Without a clear history, every post-mortem and compliance review starts with archaeology.

02changes

How does SyncOnAI 360 track Salesforce metadata changes?

Each sync records one snapshot of the org plus one entry for each component that genuinely changed, so the history grows with real change rather than with the size of the org. The Changes lens shows what changed and when, and whether it came from SyncOnAI 360 or from somewhere else.

History records that a component changed and when, not a copy of its content. For what the old version looked like, changes made through SyncOnAI 360 keep their full before and after on the proposal and the deploy record. History starts when recording starts; it cannot reconstruct an org's past before it was connected.

  • One snapshot per sync, one row per real change
  • Route of each change shown
  • Full before and after for changes through 360

Command Center

Org portfolio

5

Connected orgs

78

Average health

3

Need attention

  • Global Sales · ProductionProd

    12 open findings · Deploy approved 2h ago

    86

  • Service EMEA · ProductionProd

    31 open findings · Change made outside pipeline

    71

  • Partner Portal · ProductionProd

    18 open findings · Audit finished 20m ago

    79

  • Global Sales · UATSandbox

    14 open findings · Proposal validated

    84

  • Service EMEA · DevSandbox

    36 open findings · Sync running

    68

03outside

How do you catch changes made outside the release process?

Every audit reads the last thirty days of the org's Setup Audit Trail. The change intelligence checks flag production changes made outside the deploy pipeline, validation rules that were recently deactivated, and a single user making an unusually high number of changes.

Because those checks run after every refresh, a side-door change shows up as a finding with its evidence, rather than being discovered when the next deploy overwrites it.

  • Production changes outside the pipeline
  • Recently deactivated validation rules
  • Unusually high change velocity by one user

Org Audit

Acme Production · last run 6 minutes ago

Grade C
high

Flow has no fault path

Case_Intake_Route · Automation & Flows · Effort: hours · $600

<!-- Case_Intake_Route.flow-meta.xml -->
<recordUpdates>
  <name>Assign_Queue</name>
  <!-- no <faultConnector> -->
  <object>Case</object>
</recordUpdates>

04through 360

What is recorded for changes made through SyncOnAI 360?

Every proposal keeps a before and after view of each file, its named pre-flight checks and its blast radius. Every deploy leaves a receipt: what changed, the request that produced it, the checks, who approved it and when, with rollback to the recorded previous version.

Workspace actions, deploys, org refreshes, settings changes and connections, are written to the activity log, so the history covers who did what in the workspace as well as what changed in the org.

  • Before and after per file
  • Receipts with request, checks and approver
  • Workspace activity log

Deploy receipt

Acme Production

Deployed
Change
Case_Intake_Route: fault path added
Requested
"Add fault handling to the intake Flow"
Checks
5 of 5 passed
Approved by
M. Okafor, admin
Deployed
Today, 14:22 to Acme Production
Previous version recorded

05compare

Can you compare Salesforce orgs or points in time?

Yes. Compare metadata between two orgs, such as a sandbox and production before a release, or between snapshots of the same org, to see exactly which components differ.

Review history keeps every health review, so scores and findings can be compared over time and the effect of a cleanup or a release can be shown rather than asserted.

  • Compare between orgs
  • Compare between snapshots
  • Health reviews kept for trend

Acme Production

Org health · synced 4 minutes ago

82

Health · B

Health

82

Confidence

74

Coverage

91

Apex coverage 78%, from the org's last test run

  • 3 Flows on Case run on the same trigger
  • 11 Apex classes below 75% coverage
  • Managed package source hidden by Salesforce: 2 packages

06review

How does change history support an audit or a client review?

When an auditor or a client asks what changed during a period, the Changes lens, the deploy receipts and the activity log answer together: what moved in the org, which changes came through an approved proposal, and who did what in the workspace.

Changes that arrived some other way are visible as such, and the change intelligence checks raise them as findings, so gaps in the process are visible as well as the work.

  • Org changes, receipts and activity together
  • Side-door changes raised as findings

Acme Production

Org health · synced 4 minutes ago

82

Health · B

Health

82

Confidence

74

Coverage

91

Apex coverage 78%, from the org's last test run

  • 3 Flows on Case run on the same trigger
  • 11 Apex classes below 75% coverage
  • Managed package source hidden by Salesforce: 2 packages

07How it works

How change history builds up

Recording starts at connection and grows with real change.

  1. 01

    Connect

    Recording starts with the first sync.

  2. 02

    Sync

    Each sync records the components that genuinely changed.

  3. 03

    Audit

    Changes outside the pipeline are flagged from the Setup Audit Trail.

  4. 04

    Deploy

    Changes through 360 keep full before and after on their receipts.

08Before and after

Change history, with and without SyncOnAI 360

Without

With SyncOnAI 360

Terse Setup Audit Trail entries

Changes per component with their route

Side-door changes go unnoticed

Production changes outside the pipeline flagged

No before and after

Full before and after for changes through 360

Health trend by memory

Every review kept for comparison

Post-mortems start with archaeology

Receipts and history ready to read

09Who uses it

Who uses change history

Salesforce adminsSee what changed in each org since the last release, and whether it came through SyncOnAI 360 or straight in Setup, without reading the Setup Audit Trail line by line.
Release and delivery leadsCompare a sandbox with production before a release to see which components differ, and catch side-door production changes before the next deploy overwrites them.
Compliance and platform ownersAnswer who changed what, when and with whose approval from receipts and the activity log, and see changes made outside the release process as findings with their evidence.ConsultanciesShow a client what moved between two reviews, scores and findings side by side, so the effect of the work is demonstrated rather than claimed.

10Questions

Frequently asked questions

Each sync compares the org's components and records those that genuinely changed. Changes made through SyncOnAI 360 are recorded at deploy time with full detail.

For changes made through SyncOnAI 360, yes: proposals and deploy receipts keep the before and after. For changes made elsewhere, history records when a component changed, not its old content.

Yes. Each audit reads the last thirty days, and change intelligence checks flag production changes made outside the pipeline.

No. History starts when recording starts.

Yes. Metadata can be compared between orgs or between snapshots of the same org.

No. Retention is enforced, and old history is pruned on a schedule.

Yes. Every plan includes every feature.

Members of the workspace. Health reports and audits can also be shared as read-only links.

11Keep exploring

Related

Deploy and ApprovalsChecks, approval, receipts, rollbackOrg Audit55 checks, priced findings, a letter gradeSafe ChangeValidate, approve, deploy, roll backOrg IntelligenceUnderstand every org down to its sourceEnterprise Salesforce teamsGovern every org and every change at scalePricingEvery feature on every plan

Start in 5 minutes. No card required.

Connect your Salesforce org. Run your first health scan. Ask your first question. See what you've been missing.

Start free, connect my orgBook a demo with SyncOnAI
  • Anthropic
  • OpenAI