SyncOnAI360

Client Portal

Show clients the state of their Salesforce org, on your terms.

Read-only views of health and audit results, shared through links that expire and can be withdrawn whenever you choose, with no account needed to view.

Client portal

Share a read-only view

Read-only health summary

Acme Production · Grade B · 82

synconai360.com/share/org/7f3a...

Expires in 14 days. Viewed 3 times.

In one paragraph

The SyncOnAI 360 Client Portal shares read-only views of a Salesforce org with clients and stakeholders: health summaries, health reports and audits. Each view is shared through a link that expires and can be withdrawn at any time, the record that it existed is kept, and viewers need no account and cannot change anything.

Views to share: health summary, health report, audit
3Views to share: health summary, health report, audit
Accounts needed to view
0Accounts needed to view
Link withdrawable at any time
AnyLink withdrawable at any time
Only: viewers can change nothing
ReadOnly: viewers can change nothing

01The problem

Why client reporting on Salesforce work is so clumsy

Consultancies and platform teams report progress through PDFs and slide decks. They take time to make, go out of date immediately and can never be taken back.

  1. 01

    Reports that never die

    A PDF sent last quarter is still circulating, describing an org that has changed.

  2. 02

    Accounts for everyone

    Giving a stakeholder access to a tool means a seat, a login and a permission review.

  3. 03

    Effort over substance

    Hours go into formatting a report rather than into the work it describes.

  4. 04

    Claims without evidence

    Slides say the org is healthier; nothing lets the client see for themselves.

02share

What can be shared with a client?

Share a read-only health summary of an org from the client portal, a full health report from the org's health page, or an audit with its findings. Each is a link that opens in the browser without an account.

The views are read-only by design: a client sees the grade, the scores and the findings, and cannot change the org, the workspace or the report.

  • Health summaries, health reports and audits
  • No account needed
  • Read-only by design

Client portal

Share a read-only view

Read-only health summary

Acme Production · Grade B · 82

synconai360.com/share/org/7f3a...

Expires in 14 days. Viewed 3 times.

03control

How do you control a shared Salesforce report?

Each link expires, and any link can be withdrawn at any time. When a link is withdrawn, the record that it existed is kept, so you always know what was shared and when.

That makes sharing a decision you can reverse: share a report for a steering committee, and withdraw it when the meeting is over.

  • Links expire
  • Withdraw at any time
  • A record of every share

Client portal

Share a read-only view

Read-only health summary

Acme Production · Grade B · 82

synconai360.com/share/org/7f3a...

Expires in 14 days. Viewed 3 times.

04readable

Will clients understand what they see?

The health score maps to a letter grade with a plain sentence, from A, excellent and enterprise ready, to F, critical and needing immediate action. Audit findings are written in plain language with their evidence and an estimated cost to fix.

Clients do not need to read Salesforce metadata to follow the story: what was wrong, what it costs, and what has been fixed.

  • Letter grade with a plain sentence
  • Findings in plain language
  • Costed issues

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

05prove

How does the portal prove delivered work?

When fixes are deployed and the audit runs again, each fixed finding is marked verified fixed, or regressed if it came back, and the grade moves accordingly. Share the updated report and the client sees the evidence directly.

Combined with deploy receipts behind every change and work items linked to deploys, the portal turns reporting into evidence rather than assertion.

  • Verified fixes after re-audit
  • Receipts behind every change
  • Evidence, not slides

Org Audit

Acme Production · last run 6 minutes ago

Grade C
high

SOQL query inside a loop

Drafted a fix for OpportunitySync.cls: one query before the loop, results mapped by Id. Validated against the org. Proposal waiting for approval.

  1. Detected

  2. Fix proposed

  3. Fix deployed

  4. Verified fixed

06cadence

How do teams use shared reports over an engagement?

Share a baseline health report at kickoff, then share the re-audit after each release. Because every fix that is deployed and re-audited is marked verified fixed or regressed, the client sees progress measured against the same checks each time.

Withdraw each link when it has served its purpose. The record of what was shared stays with the workspace, so the history of what a client was shown is never in doubt.

  • A baseline at kickoff
  • A re-audit after each release
  • Withdraw links when done

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

07which

What should you share with a client, and when?

Share the health summary for a quick status, the full health report for a review meeting, and the audit when the conversation is about what to fix and what it costs. Each view answers a different question, so pick the one that matches the meeting.

Keep links short-lived for sensitive reviews and withdraw them when the meeting ends. A fresh link can always be sent for the next review.

  • Summary for status
  • Health report for reviews
  • Audit for scoping

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

08How it works

Sharing with a client

Read-only, temporary, recorded.

  1. 01

    Pick the view

    Health summary, health report or audit.

  2. 02

    Create a link

    A read-only link that expires.

  3. 03

    Send it

    The client opens it without an account.

  4. 04

    Withdraw

    Revoke it whenever you choose; the record is kept.

09Before and after

Client reporting, slides versus portal

Without

With SyncOnAI 360

PDFs that circulate forever

Links that expire and can be withdrawn

Seats and logins for stakeholders

No account needed to view

Hours formatting decks

Reports straight from the org

Claims of progress

Re-audits that verify each fix

11Questions

Frequently asked questions

A way to share read-only views of a Salesforce org's health and audit with clients and stakeholders through links.

No. Shared links open in the browser without an account.

No. Shared views are read-only.

Yes. Withdraw any link at any time; the record that it existed is kept.

Yes. Each portal link expires, and you can withdraw it sooner.

The grade, scores and findings in plain language, with evidence and cost estimates for audits.

No. In-house teams use the same links to report to leadership and partners.

Yes. Every plan includes every feature.

Yes, until it expires or you withdraw it. Withdraw links you no longer need.

Yes, through an engagement's deal room, which shares the proposal and, if you choose, the statement of work.

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.

  • Anthropic
  • OpenAI